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 TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Laserjet 4000 print jobs from 1 program hang in print spooler?!?

Status
Not open for further replies.

scriggs

IS-IT--Management
Jun 1, 2004
286
GB
I have a network with 1 LJ4000, 8 LJ4+ and 3 LJ2300. All connected by various jetdirect boxes to a Windows 2003 Server.

Last week I ran Windows Server 2003 SP1, Exchange Server 2003 SP2 and installed an upgrade to Computer Associates eTrust Antivirus v7.1.

Since then I have a problem with the LJ4000 only. When one specific program prints particular reports the first page prints, then no more. The printer does not display an error, but the jobs sit in the print queue and cannot be deleted. I need to restart the print spooler. All other jobs print fine - word, excel, internet, etc.

I have tried updating the drivers for the printer and installing PCL5 and PCL6 versions but no change. I have tried disabling the antivirus software in case it was interfering but no change.

Any ideas what I can look for, test, change?
 
I know how to fix this problem on a Netware server, but I'm not familiar with W2K3's print system... Maybe if I describe it generally you can apply it to W2K3.

The job comes from the client and is placed in a spool on the server. Then some form of handler (Netware calls these "Gateways") fetches it from the spool and feeds it to the printer. On Netware I can choose from several different Gateway providers; Novell, HP, Xerox, Kyocera, etc.

What I do when I see your problem is to assign the printer to different Gateways until I find one that behaves correctly. HP's gateway for Netware is notoriously out of date and usually the OS provided gateway handles the jobs better. Since you have just applied SP1, you may be experiencing a similar issue.
 
I have now figured out a solution thanks to much googling and thought I would share with the group.

The fault lies with the HP Standard TCP/IP Port, don't know why. Setting up a new port as a Microsoft Standard TCP/IP Port makes the problem go away.
 
Sounds like the MS Port has the same functionality as the Netware Gateway.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top