Kyocera Printers - Delayed Printing

[enjay]

Our Kyocera printers (I think just the networked ones) have started taking several minutes from the user clicking print to the page actually coming out. I haven't specifically changed anything other than running some MS monthly updates.

 

Has anyone else seen this, or does anyone have any suggestions as to cause or solution?

[SHimmer45]

which drivers are you using as i had a similar problem when using the KX drivers (on 2008R2)

switching to the Uni drivers/KPDL sorted the spooling time issues.

[enjay]

We are using the KX drivers on 2008R2. I'll try one on the KPDL drivers instead. Odd that this problem has only recently started occurring though...

[enjay]

Problem. The universal KPDL drivers don't allow duplex printing though...

[SHimmer45]

just installed version 2.41 (digitally signed) of the classic plugin unversal driver which they list ask KPDL/PCL and that has the option for double sided.

should be under the layout page under preferences, by default its set to none.

[SHimmer45]

meh it doesnt with the classic i was reading the wrong version

[enjay]

So, which version should I be using? Also, all the others I tried were all mono, not colour.

 

It is definitely something driver-related though, as it printed immediately when I had it on the PCL drivers.

[SHimmer45]

well if the KX driver isnt working and the PCL works for you id go for that.

there does appear to be issues with the KX drivers on 2008r2, i was using an older KX driver which i then updated at the time which didnt resolve the issue.

 

depending on how you roll out your drivers you should be able to install the working driver on the server and then install the KX one on the client, we are however using local port printing which can be less flexible in your ability to roll out and manage it. (only an issue if you need to change something which we dont do often)

[enjay]

I updated the KX drivers, and after a bit of a bedding in period, everything seems okay.

 

I hadn't realised when doing this that I would update all the printers of the same model at once - makes sense afterwards but at the time, I was thinking the drivers were specific to each print queue. This meant my "testing" wasn't quite as invisible to the users as I'd hoped!

[penfold]

I've had trouble with Kyocera KX drivers killing the print spooler on clients. I've had to move over to Universal drivers for now.

[enjay]

Uni drivers are too basic though - mono and no duplex.

[SHimmer45]

the pooling of the drivers is good which means you only need to change one part, not ideal for testing mind

[DavidTomic]

I've come across the same problem, and I honestly never figured out what was actually causing it.

 

In the end I actually just setup a new print server and migrated everything onto that (same printers, same drivers, etc), and it's been working fine ever since.

 

Go figure ...

[penfold]

Uni drivers are too basic though - mono and no duplex.

 

I know it's a bit late but I'm using the Kyocera Classic Universaldriver 2.81 and it allows printing on both sides. I can't comment on the colour though as we don't have any colour printers with the problem.

 

Have you had any more problems?

[Singist]

This has been happening to just a few random laptops using the KX driver from a 2008r2 server. I noticed that any image/photos being sent to the printer were being changed to bitmaps from jpegs therefore increasing the size of the print massively and taking an age. Didn't realise it might be a driver issue as it's completely random. I'll have a look at updating them.

[enjay]

I updated the drivers, which sorted the delayed printing issue but caused a far bigger problem in that computers could no longer connect at all!

 

If you do decide to update the drivers, then I would encourage you to delete the print queues, delete the existing drivers from the server, and then recreate everything, rather than just add new drivers over the top.

[penfold]

I updated the drivers, which sorted the delayed printing issue but caused a far bigger problem in that computers could no longer connect at all!

 

If you do decide to update the drivers, then I would encourage you to delete the print queues, delete the existing drivers from the server, and then recreate everything, rather than just add new drivers over the top.

 

At the moment it seems to be ok, but I am expecting some people to come complaining as I've watched a few of the jobs and they seem to take too long to print but these print jobs are 50MB+ which I'm not sure is accurate or is because of a dodgy driver.