We had all our printers managed by Windows Server 2008 R2 and was working fine for as long as I can remember. Then all of a sudden (I had installed some skydive sync tool which might have caused the problem) certain printers would appear offline to both the server and the user. We could still ping the printers (they all have static ip addresses) but not print to them. This was a good opportunity to migrate the printers to a new server running Windows Server 2012 R2. The move over was fine and users could happily print. Fast forward 3 months. Just come in this morning and about 20 of the classroom printers now appear offline on our web management window and getting helpdesk tickets about 'not being able to print'.
The temporary solution to this is to turn it off and on again but am keen to find out why it's started to do this again.
Printers are a nightmare... can you reach the webadmin pages when they are "offline"? if so check out the printer status it sometimes gives clues. if you can't wake it up and then check on the web admin for any dodgy sleep settings.
also could be something is interfering with the SNMP response from the printer. On the ports tab of the affected printers, Configure the port and uncheck SNMP and test. if you re-enable it ensure the port setup is exactly match that on the printer.
Last edited by ardvark; 2nd April 2014 at 09:50 AM.
Reason: xtra info
I'm thinking it has something to do with Pcounter since it's occurred on two different servers on two different versions of Windows OS. But, let's try to isolate the problem first before coming to any conclusions:
1. Are you able to do a test print from the Print Server when this occurs? If no, then the problem may be with the printers.
2. Have you tried printing directly from a client to a printer, bypassing the server? If you can't, the problem may be the print driver or the printers. Has the print driver been updated recently?
3. What happens when you restart the Print Server service rather than restarting the server? If this fixes it then you have a problem with the print service and may have some conflicts with other software.
4. What happens if you simply restart the Pcounter services on the server when this problem occurs? Does it fix it? If it does, then Pcounter is the culprit.
You have to think about the chain of events when a print job goes out. The client calls the print driver to send the print request, Pcounter acts as a middle-man from the client to the printer and either lets the print job through to the print server or rejects it. The print server sends the job to the printer. The problem could be anywhere along the chain.