Try this: On the properties of each printer (on the server), select the "port" tab, local the correct port, click on "configure" and uncheck "SNMP enabled". Once you click "ok" the printer's status will be instantly turned back to normal. Quoted from: http://episteme.arstechnica.com/eve/forums/a/tpc/f/12009443/m/752004225831
Had this problem after I upgraded our servers to SP2. HTH, Robert On Wed, Mar 5, 2008 at 8:03 PM, Walt Hundleby < [EMAIL PROTECTED]> wrote: > Hi All > I had to rebuild our Print Server because the system partition was created > too small and kept running out of space. > Original Printer Server was W2K3, Enterprise Ed. with SP2 > New Print Server is W2K3 R2, Ent. Ed. with SP2 > I used Microsoft's Print Migrator to recreate the queues, renamed the old > print server and then renamed the new print server to the original print > server's name to save on profile changes. > > Since then 2 or our ~35 networked printers have given a lot of grief, an > HP LJ 2100 and an HP LJ 4000. I went searching for new drivers but there > were none. I reloaded the drivers just in case. The 2100 prints a few jobs > and then goes offline. To get it going again you have to pull the plug and > then cycle the on/off. Both HP and Microsoft drivers have been tried. The > 4000 - with the HP driver the printer receives the job but does not print > it, with the Microsoft driver it does print everything but way slower than > before. > > And on top of that I have the Print Spooler service just stop on several > PCs and Terminal Servers with no error message. So far there has been only > one occurance per PC or Terminal Server of the computers that have > experienced the problem. > > Any ideas on solutions would be appreciated...Thanks...Walt > ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ > ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~ > ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
