Jump to content

Recommended Posts

Posted

For a long time we have had a follow me Print solution in school. Summer 2015 we started a new contract and got new printers in the building. We have 2 queues, a Mono & Colour. Since installation we've had a really strange problem in that sporadically users will find that they cannot send a job to one of the printers. Usually, it will take a long time to try and connect to the printer in question and Word or other Office app will eventually time out and give an error like this:

 

Windows Cannot Print.png

 

There's no real evidence of something wrong in the Event Viewer apart from the failure notice above. Both printers are on different virtual ports and in every case the opposing Printer will still work without issue. The problem appears to affect all other programs on the system. The problem can usually be rectified by logging out and back in again which isn't always ideal we just need it to work consistently.

 

I've also installed the following patches:

https://support.microsoft.com/en-us/kb/2647753

https://support.microsoft.com/en-us/kb/2713128

 

The last patch should go on over night but i'm not hopeful for a fix. Drivers are all up to date and things are working as they should be most of the time. But still this comes round and affects people everyday and its very annoying. I'm thinking it could have something to do with profiles but i'm at a loss to go about testing and replicating the problem. PLEASE HELP! :)

Posted
I've been on to them a few times now and in all honesty the support is a bit sketchy on this one. I will go back to them but i'd love something else to try in the meantime.
Posted (edited)

How is your Papercut Set up are the printers connected to a Windows server running papercut?

Just another point, when you say it works if they logg out and back in,

Just check the Papercut Client is running on the PC.

Should appear in the top right corder papercut.png

Edited by robsonma
Posted
Thanks for the reply @robsonma. Yes we are running Papercut and the printers are connected to a Windows Server. All seems to be setup correctly. We do have the Papercut Client running and have had Papercut look at this too. They have indicated though and I fully agree that the job is failing before Papercut even knows about the problem.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...