Printer is connected to Dell Windoes and it works. From my Debian, CUPS can detect it, can spool, and it prints (but not when command is sent.) It prints whenever completely unpredictable. Maybe a while later, maybe 2 days later.....

I suggest you check the CUPS configuration file and see if anything strange is going on. Also, how do you configure CUPS? Perhaps there is a rogue script that's meant to help by providing a "friendlier" way to configure but is doing more harm than good.

You need to find out what is causing the job cue to be held up. I have often seen a WinDuhs print server go into hibernation and screw up the print services when it wakes up (but in this case all computers are affected, not only Linux). See if the WinDuhs print manager shows a printer queue, which indicates that it is receiving data but not printing (in which case this is a WinDuhs problem) or if your Linux print queue is filling up with jobs (in which case it's most likely a Linux printing problem).

kaz2100

09-22-2008 08:38 PM

Hya,

CUPS config file is as provided by Debian. I did not touch anything until yesterday. I changed LogLevel.

Depending on (I guess) the number of active computers connected onto the network, available printers vary. The one which choked is gone now, moreover, /var/spool/cups is clean. Nothing is printed!

Checking every individual computer may solve this situation, but not easy as everybody has own computers.