A print job problem.

[Fragon]

I have a network printer(HP Lj5SiMX) which connect to my HP-UX system and Windows2000 system.
I issued a print job (named jobux)from HP-UX which will print about 1000 papers.
During the printing,another user issue a windows2000 based print job (EXCEL report,named jobwin) to this printer.
Normally,"jobwin" won't be printed until "jobux" is finished. But now "jobwin" print first and "jobux" stopped. After "jobwin" is finished,"jobux" start to print from the beginning again.(Print the whole job again) Thus I wasted so many papers.
Would anyone tell me how to prevent this occurs?
Thanks a lot.

[Rajeev Shukla · Accepted solution]

could you tell how you have configured your network printer on HPUX. Are you using jetdirect utility or doing a remote print on IP.

Thanks
Rajeev

[Fragon]

I use Jetdirect in HP-UX. In Windows2000 use TCP/IP port.
This problem not occur always,only sometime happened.
But when it occur,users will complain.

[Rajeev Shukla]

I guess you might change the settings on the windows. Coz TCP/IP printing just fires prints to the IP and doesn't wait in any queue. Which might be making unix print to wait in queue and finish windows print first. And the printing from begenning of the page is the feature with the unix queue. So try changing the windows end of settings and see how it goes.

Rajeev

[Bill Hassell]

JetDirect cards keep track of jobs and won't start another until one is finished. It sounds like the firmware in the JetDirect card needs updating. You can download the firmware and updating tool from http://h20000.www2.hp.com/bizsupport/TechSupport/DriverDownload.jsp?prodNum=JDDW2K&prodName=hp+jetdirect+download+manager+Windows&locale=en_US&taskId=135&prodSeriesId=27355&prodTypeId=18972

[Jin Zhou]

You'll always have this kind of problem unless you use a centralized spooler for all your print jobs, regardless of Unix or Windows. Because each computer has no knowledge of other computers' print job and simply open port TCP port 9000, reset the printer, and dump data into the printer engine.

To solve this problem, you can either use Samba or CUPS to "export" printers to Windows client. So the lpsched, or lpd, or cupsd (depending on which one you use) will handle Windows printing request just like handling Unix printing request.

PS.
Having said above, actually you may also solve this problem by using Windows "lpr", but in this case you need to use lpr on your HPUX as well. By default, HPUX use SYSV lpsched, not lpr/lpd.