Spooler halting on 2003 Cluster

[Guest]

We have a 2003 Cluster consisting of two active active nodes. About every
two weeks one of the nodes stops printing, typing in \\networkname to see the
shares/printers for a particular cluster group doesn't return a response
until the spooler is killed. Sometimes we have to hard power the server to
get it to go down/release resources to the other node.
System uptime doesn't seem to be a factor either, as we have cycled both
servers preventatively and then the next night it happened again. We are
only using WHQL signed drivers, mainly from Canon and HP, and using the
native ones when available. How can I log when a new job begins to come
through to see what job/queue/pc is causing this? Windows right now only
logs to the system log when a job finishes or fails, not when its coming in.
The last job to begin to come in before halting would be the culprit right?

 

[Hans Vredevoort]

Contact Microsoft PSS. There is an unannounced improved
Windwos 2003 printspooler available if you ask MS. You
are by no means the only one experiencing problems with
Windows 2003 printservers.

Regards,

Hans Vredevoort
The Netherlands

 

[Cal Staples]

We will be upgrading to Win 2003 next year. What other problems ,if any,
have been seen? What procedures etc. should I employ to avoid problems?
Any help/references will be appreciated. We currently are running clustered
W2K servers with just under 1300 queues.

Thanks,

Cal