One inkjet printer breaking stops all from working
We have a Windows Server 2003 print server. It doesn't do anything else, it just acts as a print server, and is a virtual machine with 1GB of RAM and 60GB of disk space. It mostly trundles along just fine.
We have a bunch of mostly second-hand HP Business Inkjet 1100 printers connected to that print server with the standard HP JetDirect 200m print server that plugs in the slot provided on the printer. We also have a few new networked HP Business Inkjet 1200 machines (bought before I realised the 1100s could be got for way cheaper second hand...).
The problem would seem to be that when one printer gets itself jammed up, or runs out of paper, and gets a backlog of a few jobs, the whole lot of 1100 / 1200 printers stops printing. Other printers on the server carry on working just fine. It's as if the 1100 / 1200 printers are all using one driver or print queue, so when one breaks they all break. Is this correct? Is this something inherant in how Windows Server 2003 handles print jobs, or is it something to do with how HP have written the driver? Is there some way I can stop this happening, a setting that I can turn on so that each printer has its own seperate whatever-it-is that it needs? I can always assign the server another gigabyte or two of RAM, or a bit more disk space, if that's going to be neccesary.