We've started having a rather severe problem since we migrated to
Server 2003 a month ago. If the printer itself is offline, the print
server will fail to notice this and the print queue will hang when the
first print job is sent to it. The only way to clear this is to attempt
to delete the job, then restart the spooler on the print server. Either
alone doesn't work.
All printers use static IP addresses. The client is a 2003 terminal
server. The client and server are on the same side of the
firewall/router, and have no a/v running on them. DNS is working, as is
WINS, and the printers are all published to AD. Whether any of those
components is missing something I can't be sure. (The print server is
also the DNS/WINS/DC.)
I'm not sure if this is a symptom, but when the spooler restarts, the
server reports the printers ready immediately, while the client takes
several minutes to come back to readiness.
We also recently made a full firewall and vpn reconfiguration on the
network, however, printing was continuing to work fine on the 2000
server whether the printers were on or off - that would be detected
properly.
|
Similar Threads
Linear Mode
