Please help. New MFD copier will not connect to any clients.

[TwistedHelixis]

Hi,

 

This primary school has just had a new MFD copier, its a Kyocera TASKalfa 6054ci.

 

Myself and the engineer connected it to the network with static IP, Installed the drivers onto the print server and set it to shared via AD.

 

Test print from server was fine.

 

When I try to add the printer from a client by pushing it from GPO the client just hangs. So I deleted the GPO for now.

 

If I open printer options on client, then click 'add printer' and click on the printer, it returns the following error. Printer error #740

 

Searched online and tried lots of different options. The following did work but is not practical.

In CMD prompt type this = rundll32 printui.dll,PrintUIEntry /il

This then opens a different printer GUI with all the printers listed, clicking on the printer then installed the drivers.

 

Obviously the above is not a workable option for the staff and the copier engineer will not help as it is printing from our printer server.

 

The copier company are coming to remove the old copier in a day or two, and this is the schools only printer, so I need to get this fixed asap.

 

EDIT - I am logged onto the client computer as local admin.

 

Any ideas?

Edited December 7, 2022 by TwistedHelixis

[Michael]

If it's the same error I'm thinking of, it means Windows isn't up-to-date and needs a newer patch. Anything from 2022 should do the trick.

[Michael]

A quick Google - it means insufficient permissions. Have a look here for guidance.

[JOrdan01070]

Hi it sounds like the printer driver permissions error did the engineer install type 3 or 4 drivers on the server.

[TwistedHelixis]

If it's the same error I'm thinking of, it means Windows isn't up-to-date and needs a newer patch. Anything from 2022 should do the trick.

 

Hi, even get this issue on our Windows 12 with Nov updates, so its not this.

 

A quick Google - it means insufficient permissions. Have a look here for guidance.

I do now remember having to do this at another school. Ill give this a go later, Thanks

 

Hi it sounds like the printer driver permissions error did the engineer install type 3 or 4 drivers on the server.

Ill check later. I take it type 4 is better?

[Michael]

Type 4 are typically more basic in functionality (compared to Type 3), but also Papercut (and possibly other print management solutions) have limitations with Type 4.

[PrimaryNetMan]

If you plan to make any use any features such as Kyocera custom boxes etc the you'll need to use their Type-3 KX drivers. Also check the Engineers have used the most up-to-date drivers

[TwistedHelixis]

I am no longer at the school but just had a call from the copier engineer to say he returned to the school as he had an idea. He has set the name and IP of the new copier to the one used on the old copier (similar or same drivers) and everyone is now printing through the new copier.

 

While this is not a fix, it does give me time to test out the ideas posted above.

[Koldov]

Had a similar thing with a recent MFD exchange/deployment...

 

Business Manager had arranged it all, for over half-term when I wasn't in!

 

I was seriously expecting carnage on the first day back (and told the Business Manager so whilst berating him for arranging it when I was on holiday... How are the drivers going to get installed? Who is going to change all the GPOs for deployment?), but when I walked in everyone was happily printing away (didn't I look a fool)!

 

Turns out the engineer just pulled all the information from the old one and copied it to the new one (including machine name, I.P., Job Accounting numbers... everything), it was even using the same drivers as it wasn't much of a step up in terms of model from a Kyocera TASKalfa 5052ci to a Kyocera TASKalfa 5054ci (I think the drivers are pretty universal anyway, although I had installed named ones and not Universal, they cover a lot of models in the .inf)... and I haven't bothered to change them as everyone seems OK!

Edited December 7, 2022 by Koldov

[MatthewL]

When I was installing copiers and replacing like for like I wouldn't bother updating drivers, they worked with old ones and in fact we still use an older driver for our new machines. Put the same IP on and you can be up and running in a few minutes.

 

With all the issues recently type 3 drivers don't seem to deploy and then you loose functions as type 4 is your universal one.