Printing - Any known issues with printservers and IP addressing?
Posted on 2004-04-19
I'm not a UNIX admin but I suffer at the hands of one. I'm a LAN Admin with a MS domain. I have IP printers, Ricoh and HP's with Jetdirects or Ricoh NICs. Printing is done from the NT Server spooler for MS Office apps, and the HP-UX server for Unix printing. Both print to the same IP address, but they have different NOS printer names.
Here's my problem:
When I poweroff, disconnect a print server from a printer, replace it with a different print server (same IP address & name), MS Printing resumes like nothing ever happened. UPUX print queue fills up but printing stops. Several powerdowns, restarts, and going back to the original printserver doesn't kickstart UNIX printing. My UNIX admin doesn't know why it happens and offers no solutions except I shouldn't mess with changing things. I'm battling an issue I don't have rights or the training to solve (the Unix server) and an admin with a bad attitude. In addition he blames the Ricoh printers - even though I've proven it happens to HP printers as well. I'd like to:
1. FIX THE ISSUE!!!
2. Know why Unix printing is so sensitive and unforgiving to printserver changes.
3. Upgrade printservers & printers without having to call my UNIX admin for attitude? Is there a timeout on Unix spoolers? A safe waiting period? Should I shut down the printer & printserver for 5 min, 1 hr, 2 hrs? before adding a new printserver?