Windows Forum

Ask something
Discussion Locked

Network printing slowdown W2K client

0 helpful
7 replies

by bobrace

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I had a client running on our network using Win98 and printing to a HP1600c on our network. I have upgraded that user with a new PC running Windows 2000 and reconfigured the client to print to the 1600c. Now when he prints, it takes forever to print any document with the smallest graphic on it. As soon as you click on print, the light starts to flash on the printer, but it just sits there for the longest time. Text Only docs seem to print OK. I have the printer set to "spool jobs so that ..." and also set to "print after the first page is spooled." What am I missing?

7 replies

by wilmos

For remote print queues (queues sent to another physical location), we've installed local print queues (in the office) for immediate relief. Also, we've seen issues with WinNt Print Servers operating with W2K clients. Often times we'll notice that the Nt print server will install a NT driver on the W2K client (not good). Using an updated driver has solved some of these issues. Unfortunately, we still have a LOT of locations with this problem. Any other possible resolutions that you've found on your end? -Will Moss (wilmos@safeco.com)

by joseph moore

There is a Windows Update patch for Win2K clients to print to HP printers. Sounds like you need this patch.
Go to the Windows Update site, run the update scan, and in the Windows 2000 section of the found updates is where this HP printing patch is.It is NOT a critical update, so it won't be in that section.

hope this helps

by beyond

I had a similar problem with a networked HP printer and resolved the issue with a printer driver. The latest HP printer driver did not work. I had to use the version prior to the latest driver to resolve this issue. There are five W2K Pro systems that print to this printer and only one system was experiencing this problems. All of the other systems were able to send print jobs to this printer without any problems. I deemed it to be software compatibility issue with the latest HP driver, but I never did search out the true culprit that created this issue. The older driver resolved the issue and I left well enough alone!

This discussion is closed to new replies.