You might try tearing down the printers and rebuilding from scratch. Not much of a solution, but it's the only thing I can think of besides the new drivers.
On Wed, Mar 5, 2008 at 5: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> ~
