printer issue

[Ravinder Singh Gill]

1 out of 3 printers were working fine (printer1). The other 2 (printer2 and printer3) were printing normal prints fine but another format of printing (some 2d labels) were not printing correctly. I then had the cables swapped between printer1 and printer2 to see if this would resolve the problem. I then also swapped the IP addresses (having cabled them back correctly) however neither of these fixed the issue. Now that the IP addresses are as they should be (as they were originally) printer1 has completely stopped working. I sent a print job to it from the unix command prompt however can not see this print job when I execute the following:

lp -dprinter1 /tmp/testprint

also I can not see it in SAM (Printers & Plotters, LP Spooler, Print Requests).

The print job has not printed either.

Can anybody advise?

[Luk Vandenbussche]

Does the job comes in your queue

disable printer1
lp -dprinter1 /tmp/testprint
lpstat -t

enable printer1
lpstat -t

[Ravinder Singh Gill]

i just resubmitted the job without making any changes and when I did a

lpstat -dprinter1

straight away after submitting the print job, it was in the queue....and a few seconds later it was no longer there (I may have taken too long to check it previously). This would suggest to me that it printed. however when I contacted the people at the site with the printer, they said nothing was printed. Any suggestions?

[Luk Vandenbussche]

Hi,

Double check your interface scripts and IP adresses

/etc/lp/interface/printer1

Do you see some activity (leds) on the printer when you send a job.

Perhaps you might miss a linefeed

[Ravinder Singh Gill]

i sent some more test prints to each of the printers and the guys are telling me that even printer1 has started printing. not sure what just happened as I did not make any changes.

[Bill Hassell]

It is difficult to advise a strategy without knowing how the printers are connected. HP-UX has two methods: remote printers which are accessed through a server or a non-HP network adapter, and printers that use HP's JetDirect interface cards. In the case of remote printing, there isn't a lot you can do at the HP-UX side if the job completes--the server did something with the file and you'll have to figure out what is wrong with the server.

For JetDirect, the fastest solution is to first query the printers with hpnpadmin -v. hpnpadmin is in the /opt/hpnpl/bin directory and will verify conectivity. If there are problems reported with hpnpadmin, contact your networking administrator with the results. If hpnpadmin -v looks normal, use removequeue (same directory) and addqueue to reinstall the printer.

[Ravinder Singh Gill]

thanks