none
Printers offline in windows 2008 R2 RRS feed

  • Question

  • Hi

    When I look into Print Management, I have some printers offline. I can print direct to the IP-address, and can acces the web-console of the printer. When I reboot the spooler it's ready and goes immediately offline again.

    any suggestions 

     

     

    mercredi 10 novembre 2010 09:17

Réponses

  • Something is interfering with the SNMP response from the printer.  On the ports tab of the affected printers, Configure the port and uncheck SNMP until you figure out what the issue is.  Setup a TEST printer using a port with SNMP enabled so you can work on the issue and still have an working queue for others to use.

    I'd also verify that the firmware on the network cards of the printers are the same version.


    Alan Morris Windows Printing Team

    jeudi 11 novembre 2010 14:42
    Auteur de réponse
  • This can also occur if the port configuration is not correct for SNMP Community name.  If you change this to a value other than PUBLIC on the device, then you will also need to update the information in port configuration.


    Alan Morris Windows Printing Team

    Hi all,

    After having some issues with offline printers, the conclusion was very simple. Just be sure that you have the exact same SNMP configuration on the printer device, matching what you have on the port used on the print server. If you don't have the option "Use Printer Offline" active, or if the printer isn't REALLY offline, this should clear out any problems.

    Hope it helps!


    Tiago Viana, MCITP:SA

    • Proposé comme réponse jonjon14all vendredi 20 juillet 2012 22:44
    • Non proposé comme réponse jonjon14all jeudi 2 août 2012 20:05
    • Proposé comme réponse sullijwiii jeudi 22 novembre 2012 16:23
    • Marqué comme réponse Alan MorrisEditor jeudi 22 novembre 2012 20:31
    mercredi 18 juillet 2012 14:27
  • This can also occur if the port configuration is not correct for SNMP Community name.  If you change this to a value other than PUBLIC on the device, then you will also need to update the information in port configuration.


    Alan Morris Windows Printing Team
    lundi 8 août 2011 22:05
    Auteur de réponse

Toutes les réponses

  • Sounds like it could be a driver problem. Try checking the OEM web site for the latest drivers.

    --------

    Regards,
    Hank Arnold
    Microsoft MVP
    Windows Server - Directory Services
    http://it.toolbox.com/blogs/personal-pc-assistant/

    On 11/10/2010 4:17 AM, Patrick Verbakel wrote:

    Hi

    When I look into Print Management, I have some printers offline. I can print direct to the IP-address, and can acces the web-console of the printer. When I reboot the spooler it's ready and goes immediately offline again.

    any suggestions




    Regards, Hank Arnold (MVP - DS)
    mercredi 10 novembre 2010 09:28
  • Hi

    I have downloaded the latest driver and have this issue for serveral printers. Some printers are "ready" other "offline", for same brand/type and same driver  

     

    mercredi 10 novembre 2010 10:04
  • Hi,

    Thanks for the post.

    You said that some printers are "ready" other "offline", for same brand/type and same driver. Now I am wondering if there is any registry difference between the good one and the bad one. You could check it from the following path in registry:

    Key:   HKEY_CURRENT_CONFIG\System\CurrentControlSet\Control\Print\Printers\<print queue name>

    In addition, are these printers (good ones and bad ones) locally attached to the same machine?

    Please also right-click the problematic print queue in Printers, and then clear the Use Printer Offline setting. This resets the registry key to the correct value.

    Hope this helps.

    Miles

     


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    jeudi 11 novembre 2010 02:57
    Modérateur
  • Hi

    registry looks the same

    all printers connect to one printerserver

    Use printer offline was not marked

     

    regards,

     

    • Proposé comme réponse eschencedq lundi 23 juillet 2012 13:48
    jeudi 11 novembre 2010 08:28
  • Something is interfering with the SNMP response from the printer.  On the ports tab of the affected printers, Configure the port and uncheck SNMP until you figure out what the issue is.  Setup a TEST printer using a port with SNMP enabled so you can work on the issue and still have an working queue for others to use.

    I'd also verify that the firmware on the network cards of the printers are the same version.


    Alan Morris Windows Printing Team

    jeudi 11 novembre 2010 14:42
    Auteur de réponse
  • I disabled snmp on the port and status changed to "ready"

    will look into firmware

    jeudi 11 novembre 2010 14:51
  • Hi there,

     

    I have this exact symptom on a Windows 2008 Standard Server. This solution\workaround worked like a charm.

    But I'm still trying to identify the cause of the problem. Has anyone reached a conclusion?

     

    Best Regards,

    Tiago Viana

     

     

     

    mercredi 9 mars 2011 09:54
  • Greetings,

    Has anyone found a resolution for this issue. I am having the same issue as well.

     

    Please advise.

     

    Thanks,

     

    wm

    jeudi 26 mai 2011 22:07
  • I don't know much about SNMP but I think it's a security configuration mismatch between the printer and the driver. The SNMP client in the driver has community name set to "public" which is a default read-only name or something. When I logged in to my printer's firmware through the web interface, I looked at the SNMP config page and SNMP was setup to read-write access with a blank community name. I set the printer community name to public and since then I haven't had the offline status problems but I can't prove this is what fixed it.

    The printer I was having problems with is a HP LaserJet 9050n, latest firmware and universal print driver on a 2008 R2 server.

    jeudi 28 juillet 2011 12:49
  • Thank you Alan Morris.  Turning off SNMP on the printer did the trick.
    jeudi 4 août 2011 18:46
  • Although not for 2008, the same workaround is mentioned here :

    http://support.microsoft.com/kb/946198


    Please remember to click “Mark as Answer” on the post that helps you.
    dimanche 7 août 2011 01:09
  • This can also occur if the port configuration is not correct for SNMP Community name.  If you change this to a value other than PUBLIC on the device, then you will also need to update the information in port configuration.


    Alan Morris Windows Printing Team
    lundi 8 août 2011 22:05
    Auteur de réponse
  • Although not for 2008, the same workaround is mentioned here :

    http://support.microsoft.com/kb/946198


    Please remember to click “Mark as Answer” on the post that helps you.


    The issue above looks to be a defect/bug in the tcpmib.dll.  It is the 2007 version that was affected and resolved by the hotfix delivered by KB946198. 

    There was a registry/GPO component to enable the hotfix in 2003: DWORD: SNMPLegacy at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print with a value set to 1.  This is documented in the KB.  It was also suggested to me that since this hotfix was delivered for Server 2003 that it should have been ported to Server 2008 R2 and simply adding the very same component (SNMPLegacy) to the 2008 box should alleviate the behaviour.  Tried that.  Same issue.

    So it's either not a bug in the tcpmib.dll or the hotfix was NOT ported to Server 2008.  I'll tend to lean to the latter.

    vendredi 14 octobre 2011 20:14
  • Hi Dustin,

    in fact it is not a bug in tcpmib.dll . It's a design change. Customers with large print server farms and thousands of print queues complained that they don't know if printers are attached behind the old print queues in his environment because all print queues were online.

    As a result a design change has been done. If the printer does not respond or does not respond in a spesific period of time it will be set to offline by the spooler service.

    The admins will then know if the print queues are still used or if a printer is attached behind that. The problem was that a lot of printers were not snmp compliant and also does not repond within the required time to the print server.

    The spooler set it to offline and clients were not able to print. Therefore MS introduced SNMPLegacy (Old behaviour). Even if the printer does not respond to the snmp command it will remain online.

    Regards,

    Cengiz Kuskaya




    vendredi 14 octobre 2011 22:28
  • The SNMPLegacy registry key was never implemented in any OS other than 2003 SP2.
    Alan Morris Windows Printing Team
    samedi 15 octobre 2011 07:23
    Auteur de réponse
  • Yes.  I believe that was confirmed.  Thanks Cengiz for your feedback.

    For the purposes of workaround the key for the SNMP Status is located at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors\Standard TCP/IP Port\Ports\<IP Address/Port Name>\SNMP Enabled.  Set it to 0.

    GPO Ready?

    D.

    mercredi 19 octobre 2011 20:41
  • Hello Alan,

    no, thats not correct. There is something wrong with the SNMP response interpretation  in Windows Server 2008 R2. Windows Server 2003 reads the SNMP value correct as "Error", Windows Server 2008 R2 thinks, it is "Offline". So observed at several printer models (but not all).

    regards,

    Herbert Abels
    Germany

    mercredi 18 juillet 2012 07:45
  • Hello Hank,

    sorry, but this is not possible.

    We are talking about SNMP, not about the driver. Either the message will be sent out incorrectly or is misinterpreted by the operating system.

    regards,

    Herbert Abels
    Germany

    mercredi 18 juillet 2012 07:50
  • Hello Patrick,

    this works, but does not solve the problem. When disconnecting the warning lamp, it will not light precisely, of course.

    But theSNMP communicationis needed formanythings.For example,the devicesoptions are recognizedand reportedwith SNMP. And there are some warning messages that are very very important for central monitoring (like ther correct "Offline").

    Regards,

    Herbert Abels
    Germany

    mercredi 18 juillet 2012 07:59
  • Hello Alan,

    what does that mean?

    The problem is that there may be many reasons for a printer not to respond to an SNMP command. For example, the warning "toner low" or "paper tray empty" with some printers. I think the reason lies in the order of SNMP queries and the positions in the MIB, perhaps relating with a timeout.

    Regards,

    Herbert.Abels
    Germany

    mercredi 18 juillet 2012 11:21
  • This can also occur if the port configuration is not correct for SNMP Community name.  If you change this to a value other than PUBLIC on the device, then you will also need to update the information in port configuration.


    Alan Morris Windows Printing Team

    Hi all,

    After having some issues with offline printers, the conclusion was very simple. Just be sure that you have the exact same SNMP configuration on the printer device, matching what you have on the port used on the print server. If you don't have the option "Use Printer Offline" active, or if the printer isn't REALLY offline, this should clear out any problems.

    Hope it helps!


    Tiago Viana, MCITP:SA

    • Proposé comme réponse jonjon14all vendredi 20 juillet 2012 22:44
    • Non proposé comme réponse jonjon14all jeudi 2 août 2012 20:05
    • Proposé comme réponse sullijwiii jeudi 22 novembre 2012 16:23
    • Marqué comme réponse Alan MorrisEditor jeudi 22 novembre 2012 20:31
    mercredi 18 juillet 2012 14:27
  • Alan and Tiago, your answers proved true in my case - HP 2320 and 400 printers offline in Server 2008. I found the SNMP did not match in both the browser view and the port setting in Printer and Device Win7. They are working great now. All I have to do is change the settings on about 25 printers. Thank you very much :)
    jeudi 22 novembre 2012 16:29
  • Yes its the wrong SNMP settings that caused the printer to go offline. Thanks for this post!

    jeudi 8 octobre 2015 09:08
  • Great tip!!!
    jeudi 16 novembre 2017 18:45
  • Thanks Alan. Still useful today.
    jeudi 22 mars 2018 05:59
  • Hi all,

    Just had this issue on a Server 2012 print server with an Oki C711.  After verifying the SNMP community string, I found that the OFFLINE condition of my queue changed to ONLINE when I changed the SNMP index in the queue's port setting from 0 to 1.  It was still printing OK in the OFFLINE condition.

    mardi 8 octobre 2019 13:46
  • thanks for the additional information

    Alan Morris formerly with Windows Printing Team

    mercredi 9 octobre 2019 04:58
    Auteur de réponse