Hanging Print Jobs

[s5fs]

I'm running NT4 sp6a as a print server for about 12 printers. The problem is when a print job get stuck (ie, the printer runs out of paper) all queued print jobs hang until I fix the printer, even jobs scheduled to other printers.
I basically have two questions:
1) How can I fix this problem in NT4
2) Does Win2k offer more robust print server capabilities?
This has been an ongoing problem and I'd like to get it fixed before I go insane
Thanks,
- Adam

 

[AMCSE]

I can't answer your NT 4.0 print question however, I can talk a little about 2000 print services. We run 6 separate 2000 servers as file and print servers. On one server we have 108 printers installed. It is extremely easy to install and administer those printers. If you go the 2000 route I have one caution. Make sure you download the latest drivers from the manufacturer. We had trouble in the beginning with drivers that are supplied with the 2000 Server CD. Good Luck.

 

[Zelandakh]

It doesn't all hang on mine. How are you configuring the printers? What does event log say?

 

[s5fs]

Zelandakh, here is an example: lets say I have a printer named HP5 that a user has sent a large document (30pgs) to. It runs out of paper in the middle of the print job, and I get a message in the event log saying "Printer on host 192.168.1.x is rejecting our request..", but thats the only message. Unfortunately when this happens, occasionally the server will stop servicing the other printers as well, and they will hang in a "spooling" state, and will not print until HP5 ceases to have an error condition (ie, I put paper in the tray). Any ideas?
- A

 

[zoeythecat]

What type/model of printer are we talking about (the model of the printer that is causing all the other printers to wait)?

What ports are you using?

Check the properties of each printer (check the Scheduling tab) and let us know what settings you have defined here. Compare these to how the other settings are.