Results 1 to 14 of 14
  1. #1
    Super Moderator BATcher's Avatar
    Join Date
    Feb 2008
    Location
    A cultural area in SW England
    Posts
    3,414
    Thanks
    33
    Thanked 195 Times in 175 Posts

    WS2008R2 server: Network printers show as offline on Win7 clients

    I'm bashing my head against a brick wall on this one, and wonder whether anyone has come across the problem, and preferably a fix!

    I have a WS2008R2 server with two networked printers defined on it, and about 25 Windows 7 Pro PCs, all in a workgroup.

    Every so often both printers will show as offline on one or more of the Win7 clients, but the printers aren't really offline.

    I've applied the SNMP Legacy fix (yes, I know it shows for WS2003) to all the clients, and then (more logically, perhaps) to the server, but this hasn't fixed the problem.

    I've read through the arguments in this thread, and it appears to me that the SNMP settings for both printers should be the same when accessed via a browser looking at a printer's IP address, and the printer port definition on the server. I can't check this at present!

    Any thoughts welcome...
    BATcher

    Time prevents everything happening all at once...

  2. #2
    WS Lounge VIP
    Join Date
    Dec 2009
    Location
    Earth
    Posts
    8,188
    Thanks
    47
    Thanked 983 Times in 913 Posts
    You should not be using the printer's IP address to connect to a printer defined on a server - I assume this is what you have done.
    You connect to the printer by selecting it in Explorer after browsing to the server, or typing "\\servername\printername" in a Command Prompt - there are other ways but we'll stick to those two for now.

    cheers, Paul

  3. #3
    Super Moderator BATcher's Avatar
    Join Date
    Feb 2008
    Location
    A cultural area in SW England
    Posts
    3,414
    Thanks
    33
    Thanked 195 Times in 175 Posts
    No, sorry - I meant that I used the printer's IP address in a browser to get to the administrator functions so I could see what was set in SNMP...
    BATcher

    Time prevents everything happening all at once...

  4. #4
    WS Lounge VIP
    Join Date
    Dec 2009
    Location
    Earth
    Posts
    8,188
    Thanks
    47
    Thanked 983 Times in 913 Posts
    What has SNMP got to do with offline notification?
    Are you using an external SNMP monitor?

    cheers, Paul

  5. #5
    Super Moderator BATcher's Avatar
    Join Date
    Feb 2008
    Location
    A cultural area in SW England
    Posts
    3,414
    Thanks
    33
    Thanked 195 Times in 175 Posts
    No - I know nothing whatever about SNMP, apart from what I read in the first link in my original post!
    BATcher

    Time prevents everything happening all at once...

  6. #6
    WS Lounge VIP
    Join Date
    Dec 2009
    Location
    Earth
    Posts
    8,188
    Thanks
    47
    Thanked 983 Times in 913 Posts
    I now see where you are going - note to self, read more carefully.

    The printer is "controlled" by the server and the clients use that as the source of printer status.
    Is the printer shown offline on the server?
    Are the clients connecting to the printer on the server or direct? Check the port.
    Are the permissions on the server queue correct? Everyone should have print rights.
    Are there any problems in Event Manager > security?

    cheers, Paul

  7. #7
    jwoods
    Guest
    Quote Originally Posted by BATcher View Post
    I've applied the SNMP Legacy fix (yes, I know it shows for WS2003) to all the clients, and then (more logically, perhaps) to the server, but this hasn't fixed the problem.

    Any thoughts welcome...
    There is also a hotfix available for Windows Server 2008 R2...

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

  8. #8
    Super Moderator BATcher's Avatar
    Join Date
    Feb 2008
    Location
    A cultural area in SW England
    Posts
    3,414
    Thanks
    33
    Thanked 195 Times in 175 Posts
    Thanks, jwoods - I nearly applied that one yesterday, but noticed that my server's level of Win32spl.dll was about a year newer than those in the "all supported x64-based versions of Windows 7 and of Windows Server 2008 R2" list.

    Paul T:

    The printer is "controlled" by the server and the clients use that as the source of printer status.
    Yes, both printers are defined/installed on the server, and I did Add Printer on each Win7 Client.
    BTW one is a hefty Kyocera photocopier/scanner/printer, the other is a smaller HP multifunction box. Not that that makes any difference!
    Both seem to support SNMP v1 (at least), and have 'public' as the 'community'.

    Is the printer shown offline on the server?
    No, only on the occasional Win7 client, just after they've printed to one of the two printers.
    Both printers show offline on the failing Win7 client when you then look.

    Are the clients connecting to the printer on the server or direct? Check the port.
    See first answer! Not sure what I need to check on the port - I've (now) turned off SNMP on the port of each printer.

    Are the permissions on the server queue correct? Everyone should have print rights.

    Since most of the time everything works, that one is a non-starter!

    Are there any problems in Event Manager > security?
    You have more faith in Event Manager than I have!
    The difficulty is associating the time one is told about a problem with when the problem actually started.

    The important thing I note is that, although they have been working for about a year without incident (I understand), the problems started once more Win 7 clients were introduced to replace XP clients. I started a couple of months ago with about half-XP, half-Win7, and now have 24 of the 26 PCs being Win7.
    BATcher

    Time prevents everything happening all at once...

  9. #9
    WS Lounge VIP
    Join Date
    Dec 2009
    Location
    Earth
    Posts
    8,188
    Thanks
    47
    Thanked 983 Times in 913 Posts
    the problems started once more Win 7 clients were introduced to replace XP clients
    Hence my question about how they were installed. Installation should be done by selecting from the server in Explorer or \\server\printerqueue.
    If you double click on the printer on the PC to view the queue you should see its address in the title, which should be \\server\printerqueue.
    [Edit] And the printers should have been installed on the server as local printers with the port set to the printer IP or DNS name.

    cheers, Paul

  10. #10
    Super Moderator BATcher's Avatar
    Join Date
    Feb 2008
    Location
    A cultural area in SW England
    Posts
    3,414
    Thanks
    33
    Thanked 195 Times in 175 Posts
    You have specified precisely what was done!
    BATcher

    Time prevents everything happening all at once...

  11. #11
    WS Lounge VIP
    Join Date
    Dec 2009
    Location
    Earth
    Posts
    8,188
    Thanks
    47
    Thanked 983 Times in 913 Posts
    How about this MS article / hot fix?
    https://support.microsoft.com/en-us/kb/2713128

    cheers, Paul

  12. #12
    jwoods
    Guest
    Quote Originally Posted by Paul T View Post
    How about this MS article / hot fix?
    https://support.microsoft.com/en-us/kb/2713128

    cheers, Paul
    That's the hotfix posted in post #7.

  13. #13
    New Lounger
    Join Date
    Apr 2010
    Location
    New Jersey
    Posts
    3
    Thanks
    0
    Thanked 0 Times in 0 Posts
    I have had this problem where there is a WSD port on the server. Did not seem to be a problem before Windows 7.

  14. #14
    Super Moderator BATcher's Avatar
    Join Date
    Feb 2008
    Location
    A cultural area in SW England
    Posts
    3,414
    Thanks
    33
    Thanked 195 Times in 175 Posts
    No, don't have a WSD port!

    It 'seems' that turning off SNMP has fixed the problem.
    I hope!
    BATcher

    Time prevents everything happening all at once...

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •