Operating System - HP-UX
1827382 Members
4105 Online
109963 Solutions
New Discussion

Re: Print request is in lpstat -t but not actually not printing on the printer

 
deepu
Occasional Contributor

Print request is in lpstat -t but not actually not printing on the printer

I have defined a new printer in the server. The printer name is appearing in lpstat -t and also enabled.
When giving any request it is constantly appearing in lpstat -u but no output on the printer. Like following :
70_3-9635 root priority 0 Oct 1 12:16 on 70_3
hosts 719 bytes

Pls suggest what is the problem ?
4 REPLIES 4
Bhuvaneswari Selvaraj
Valued Contributor

Re: Print request is in lpstat -t but not actually not printing on the printer

Hi,
Try checking whether the sceduler is running or not, by using the command lpsched. If it is not running, bring it up by using the same command lpsched.

If it is still not working, try to ping the printer.

If that also does not help, bring up SAM and see whether the printer is a real printer or is it a dummy printer.
john korterman
Honored Contributor

Re: Print request is in lpstat -t but not actually not printing on the printer

Hi,
check that you can connect to the printer on port 515, e.g.:
# telnet 70_3 515

if you do not get a prompt, it is a network problem.

regards,
John K.
it would be nice if you always got a second chance
deepu
Occasional Contributor

Re: Print request is in lpstat -t but not actually not printing on the printer

Hi,
Not all requests are printing. Every two requests of the same file is printing. Means if I give one file for printing the first request is not printing and also not coming into spooler. But same file is printing on the second request. The request id is skipping to next.
The printer is a network printer.

Pls suggest.
If I do telnet 70_3 515 then it is saying :
# telnet 70_3 515
70_3: Unknown host
john korterman
Honored Contributor

Re: Print request is in lpstat -t but not actually not printing on the printer

Hi again,
sorry I misunderstood: I tought that nothing was printed out and that 70_3 was the printer in question. It appears not to be the case.

regards,
John K.
it would be nice if you always got a second chance