Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Puzzling printer problem - help!

Status
Not open for further replies.

albracco

IS-IT--Management
Jun 10, 2004
62
US
Background:
SCO 5.0.7, 2 identical servers. 6 HP laserjet network printers. A few months ago, the main server seemed to be having various problems - (SSH wouldn't work, couldn't install any patches with Software Manager, etc.). Admin decided to restore the root filesystem from the second server (where there were no apparent problems) and then re-name the server, change IP, re-license SCO, etc. This seemed to work swimmingly. They could then install patches, got SSH working, etc.

Problem:
However, a new problem cropped up. For one of the printers (an HP laserjet 9000), whenever 2 or more large files are printed, the last job is not released from the spooler, although all the jobs do print. The spooler believes the last job is still printing and will stay that way and not print anything else until that job is cancelled. It only
happens when printing files larger than 75,000 bytes, and only when 2 or more are sent in succession. And it only happens with that printer. Printer prints fine from Windows.


Futile attempts to fix:
I've tried everything I can think of. Re-configured the printer, tried various interface scripts, checked permissions on lp and related files/directories. I've tried restoring printing-related files from a backup when it was working. I tried completely removing network
printing and re-installing and setting up the printers again from scratch. Same problem. I've tried setting the printer tcp/ip user & idle timeout settings to the highest allowable number.

Looking for new ideas...

TIA
 
In your /etc/printcap file make sure there is no "ex" directive and that there is an "mx#0
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top