Printer que won't clear.

[crzycooter]

I'm running windows98 SE on a network. I send print jobs through a print server to a printer that is on the network. I setup a continuous ping so I could monitor replies from the printer. I printed a test page and saw that immediately after the print job made it to the printer's memory, the windows 98 machine lost ip connection to the printer. This causes the print job to hang in the print que on the pc. You can't purge it. Print jobs from then on just keep stacking up on top of that one and nothing more can get printed. The pc has to be rebooted to clear the print que. Any help out there on this one? erick@cmoremedical.com

http://www.cmoremedical.com

 

[clivo]

The print jobs piling up is a usual but abnormal occurence in Windows, not just 98SE.

I'm not convinced that IP connection was lost. What printer is used, is it attached to a print server or station or is it stand alone? What are your spool settings and are you using EMF or RAW?



Clive
clive@digitalsky.co.za

 

[crzycooter]

It's printing RAW, although I have tried EMF as well. The printer is set up on the network(LPR port) with its own ip address. I'm convinced that it is losing ip connection since pinging that ip address will come back with no reply. erick@cmoremedical.com

http://www.cmoremedical.com

 

[Sugarman]

I have a similar problem on a Win 2000 Professional machine.
The print jobs get stuck in the que.
But the Print que just keeps on getting more and more jobs which actually don't exist.
Restarting does not help.
Reinstalling the printer or restarting the spooler neither.
Though, after restarting the spooler, any print job is shown as 3 local downlevel documents, but still no printing occurs. Any help will be greatly appreciated.

Another bit of a brain-teaser:
After a few reinstallations of the printer and spooler, the printer did print a test page, but as soon as i shared it or tried to print through DOS, the problem reoccured.