Remote printing between 10.20 and HPUX 11

[Omer Mukthar]

I am facing a problem with remote printing, I have a HPUX 11 server which can remote print to another HPUX 11 server. From 10.20 to 11 no problem in remote printing.
But from HPUX 11 to 10.20, when I print it gives waiting for printserver to come up. Have any one faced this problem and any solutions?

[John Poff]

Hi,

Do you have a line in your /etc/inetd.conf config file for the 'rlpdaemon'? If so, check your /var/adm/inetd.sec file, which is where other systems are allowed or denied the ability to print to your 10.20 system.

JP

[Omer Mukthar]

Hi John,

the /etc/services
/etc/inetd.conf
/var/adm/inetd.sec

All these files are O.K and still I face the problem. From another 10.20 server I am able to remotely print on through the same server. Is there any other clue? How to assign points? as I am new user

[John Poff]

What command are you using on your 11.00 box to do the print command, and what error message is it giving you? Are you getting the error message on your 10.20 box or your 11.00 box?

It looks like you figured out the points. Welcome to the forum!

JP

[Michael Steele_2]

Here is the remote printer configuration procedure from HP, I've tested it on both versions of HP-UX; 10.20 and 11.00.

From client:

a) ps -ef | grep rlp
b) rlpdaemon running?
c) kill PID rlpdaemon
d) vi /etc/inetd.conf
e) printer stream tcp nowait root /usr/lib/rlpdaemon rlpdaemon -i -l (* THIS SYNTAX IS CORRECT*)
f) inetd -c

From both server and client:

a) vi /etc/hosts
b) add client/server ip
c) ping client/server ip
d) verify printer works for local print jobs on server

From server:

a) lpstat -t (* printer exists *)
b) /usr/lib/lpadmin -x printer (* NOW DELETE *)
c) /usr/lib/lpshut (* stop lpsched *)
d) /usr/lbin/lpadmin -p local_printer_name -mrmode1 -v/dev/null -ocmrcmode1 -osmrsmode1 -orm -orp
e) /usr/bin/enable local_printer_name
f) /usr/bin/accept local_printer_name
g) /usr/lib/lpsched

[Omer Mukthar]

I am using the lp -d "printer name" filename.

The problem is job never is routed to the remote 10.20 server. The job stays at the 11 server itself. In solairs I use snoop command to see what really happens on the target...Dont we have a equivalent command in HP?

jobs printed
From 10.20 to 10.20 no problem
From 11 to 11 no problem
From 10.20 to 11 no problem

Job is not routed when print job is fired from hpux 11 to 10.20...

Any further clues?

[John Poff]

Hi again,

Can your 11.0 box resolve the hostname and IP address of the 10.20 box? I've also seen similar problems when a box has had an IP address change. On your 11.0 box, try deleting the print queue that points to the remote printer and then recreating it.

JP

[Omer Mukthar]

John,

The hosts file has the remote server name and name resolution is not the problem. Could it be a downward compatibility problem?

[John Poff]

Omer,

I wouldn't think it would be a compatibility problem. All the printing software is pretty ancient so I would think the different flavors of HP-UX wouldn't matter. It might be a patch problem. Do you have all the latest lp patches on the boxes? What kind of printer are your printing to on the 10.20 box?

I have some 10.20 boxes. I can try setting up a print queue from an 11.0 box here and see if it goes to one of them.

JP

[Omer Mukthar]

Hi John,
thanks a lot....

10.20 server has a alis line printers connected to the serial ports. I am able to print very fine from other HPUX 10.20 servers.

Can you simulate the same and see if you also face the same problem?

Patch wise I have the latest installed on both.

[Michael Steele_2]

OK, Lets check for jetadmin, if you're still having problems, and run the diagnostics utility.

jetadmin
diagnostics #2
examin spooler operations #2
enter name of printer
yes to everything
view /tmp/hpnpflog file

[Omer Mukthar]

Hi Fredrick,

I am not using Jetdirect card. The printer is connected to seril port of a HPUX 10.20 server. Another HPUX 11 server configured as a remote printer pointing to this printer is not spooling the job to the HPUX10.20 server.

[Michael Steele_2]

You know, its very possible for jobs to get hung up for one particular printer while success occurr elsewhere. So from the two servers unable to print, clear them out. Here is the way to do this:

a)cd /var/spool/lp
b)ls FIF, SCHEDLOCK (* Present?*)
c)lpstat -r (* running? *)
d)lpshut
e)rm FIFO, SCHEDLOCK, outputq, *lock.
f)>outputq
g)>log
h)ps -ef | grep -i lp
i)kill any jobs found in h)
i)lpsched -v
j)more log file
k)lp -d printer

[Michael Steele_2]

Are you using any kind of serial to network interface device like a switch box? Something that may have an ip address and connection for the last 2 feet but be serially connnected to the server?

[Omer Mukthar]

Hi Friends,

I found the problem,

The target host which I am remote printing to should have the source hostname's IP Address on its /etc/hosts entry.

Good exercise.....Thanks a lot every one....

[Omer Mukthar]

Thanks a lot John for specifying that its not compatibility problem....