At work, I have a little desktop USB Canon inkjet printer connected to my laptop, which I primarily use to print quick items like an agenda for a meeting I'm in. For big print jobs, I have a Windows print queue definition that points to the network HP laserjet printer in our office.
One day when printing to the local printer, Windows warned me that one of my color ink cartridges was running low. Ever the lazy person, I just clicked the "print in greyscale" box whenever I printed to the local printer.
Eventually, my black ink cartridge ran empty. About to go on vacation for the holidays, I didn't order a replacement, and just printed everything to the laser printer.
When I got back to the office, I figured there wasn't a point in keeping the local inkjet printer powered on if I wasn't going to print to it, so I turned it off. The next morning, I wasn't able to print to our network printer. That meant I couldn't print anything! Every time I tried to print, Windows said the printer was "offline". Ouch!
If you can see the problem, you are smarter than I am.
Through many iterations of experiments, I've determined the following:
- If the local printer is off when I boot Windows, the network printer appears to be "offline".
- If the local printer is on when I boot Windows, I can print to the network printer.
Why does Windows seem to care about the local printer, when trying to print to the network printer? Linux doesn't care about these things. These printers are defined on different queues - or at least, Linux puts different printers on different queues. I assume Windows does that. Does Windows do some kind of weird print-fu where the local printer matters, even when printing to a network printer?
I guess I'll have to unplug the USB cable to the local printer until I get a new ink cartridge ...