topic Re: remote printer in Operating System - HP-UX

remote printer

Sean Lavery — Fri, 17 Oct 2003 13:40:14 GMT

i have canon imagerunner 8500 copier that is hooked up to our network and i am trying to set it up as a printer on our HPUX (vers. 11 B)box.. I have an entry in the /etc/hosts file for it and I am using SAM .. i put in the printer name, the ipaddress as the remote system name, and "lp" as the remote printer name (as I was told by a local canon rep).. I cant get anything to print.. Should this be setup as a BSD System?? I know now that the lpstat command causes the connection to go down and I get the "waiting for xx.xx.xx.xx to come up" message.. Any thoughts? Insight would be greatly appreciated!
Thanx
Sean

Re: remote printer

RAC_1 — Fri, 17 Oct 2003 13:55:45 GMT

Try adding like follows.

lpshut

lpadmin -pPrinter_name -v/dev/null -ob3 -mrmodel -ocmrcmodel -osmrsmodel -ormsys2 -orplp

Where -mrmodel is the script(rmodel) that will be used as interface script. You may the script for your printer on internet or from vendor.

-ob3 - is bsd style printer.
-orplp - remotye print queue
-ormsys2 -- remote system sys2(/etc/hosts entry of printer)

lpsched -v

Try printing.

Re: remote printer

RAC_1 — Fri, 17 Oct 2003 13:59:37 GMT

Check this thread. May be helpful.
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=198122

Also missed few steps in my response.

enable and accept commnds for printer and then lpsched -v

Re: remote printer

Michael Steele_2 — Fri, 17 Oct 2003 14:00:58 GMT

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

Re: remote printer

Sean Lavery — Fri, 17 Oct 2003 14:03:35 GMT

the only thing is i dont know how to test on the local print server because it is built into the canon copier.. i cant telnet into it or anything..

Re: remote printer

Sean Lavery — Fri, 17 Oct 2003 14:18:36 GMT

also, any of you guys know why an lpstat -d kills the connection???

Re: remote printer

RAC_1 — Fri, 17 Oct 2003 14:23:34 GMT

You printer is network printer and should be added as remote printer as I mentioned above.

You can check by putting different interface scripts.

lpstat -d prints default printer.

Re: remote printer

Michael Steele_2 — Fri, 17 Oct 2003 14:24:35 GMT

Local printer.

Try something like this then:

remsh host cat /etc/passwd > /dev/printer

Re: remote printer

Michael Steele_2 — Fri, 17 Oct 2003 14:25:46 GMT

Disregard the last message:

Re: remote printer

Sean Lavery — Fri, 17 Oct 2003 14:32:34 GMT

i should have specified .. when i type lpstat -d it kills the connection.. i have been attempting to install it as a remote printer

Re: remote printer

RAC_1 — Fri, 17 Oct 2003 14:35:52 GMT

lpadmin -d printer name will set default printer.

lpstat -d prints defaulkt printer.

What do you mean by cloeses the connection?

Re: remote printer

Sean Lavery — Fri, 17 Oct 2003 14:49:04 GMT

when every i do a lpstat CIR8500, i imediately get the following:
/ (root) $lpstat CIR8500
CIR8500-0 root priority 0 Oct 17 15:46 on CIR8500
(standard input) 2585 bytes
CIR8500-1 root priority 0 Oct 17 15:46
(standard input) 346 bytes
connection to 192.99.99.10 is down

cbwux: waiting for 192.99.99.10 to come up

Then for a short period of time I cant even print to the copier from windows (almost like the network connection to the printer is dead)

Re: remote printer

RAC_1 — Fri, 17 Oct 2003 14:54:13 GMT

This could be a network problem.

You can check it with a contineous ping to printer ip address.

lpstat should not cause problem unless the there is a problem with printer.

Re: remote printer

Keith Bevan_1 — Sat, 18 Oct 2003 03:27:34 GMT

Sean,

'waiting for xx.xx.xx.xx to come up' and a failed telnet to the ip suggests a config or connectivity issue'

Try :-

ping 192.99.99.10

If this is a remote printer then I am assuming the printer has an address/gateway set in the config of the copiers internal network card.

Providing ping is not turned off on your comms (ie router config) you should get a reply from this ip address.

If this fails then its either :-

cabling/connectivity issue - check cabling
config issue at the printer end - check ip config on copier

If it works and you get a reply try pinging the lookup/alias name next to the ip address in the /etc/hosts table.

Again this should work if the /etc/hosts table is set correct.

Let me know your results.

Keith

Re: remote printer

Sean Lavery — Mon, 20 Oct 2003 10:39:11 GMT

the IP ping worked...
/adv/data/COOPER (seanl) $ping 192.99.99.10
PING 192.99.99.10: 64 byte packets
64 bytes from 192.99.99.10: icmp_seq=0. time=11. ms
64 bytes from 192.99.99.10: icmp_seq=1. time=1. ms
64 bytes from 192.99.99.10: icmp_seq=2. time=1. ms
64 bytes from 192.99.99.10: icmp_seq=3. time=1. ms

----192.99.99.10 PING Statistics----
4 packets transmitted, 4 packets received, 0% packet loss
round-trip (ms) min/avg/max = 1/3/11
as did the name ping...
/adv/data/COOPER (seanl) $ping CIR8500
PING CIR8500: 64 byte packets
64 bytes from 192.99.99.10: icmp_seq=0. time=1. ms
64 bytes from 192.99.99.10: icmp_seq=1. time=1. ms
64 bytes from 192.99.99.10: icmp_seq=2. time=1. ms
64 bytes from 192.99.99.10: icmp_seq=3. time=1. ms
64 bytes from 192.99.99.10: icmp_seq=4. time=1. ms

----CIR8500 PING Statistics----
5 packets transmitted, 5 packets received, 0% packet loss
round-trip (ms) min/avg/max = 1/1/1

Re: remote printer

john korterman — Mon, 20 Oct 2003 11:01:34 GMT

Hi Sean,
the lp daemon on the unix server should be able to contact the printer on port 515. This is probably not ok at the moment. Try this command for testing this:
# telnet 515

if you get something like "connection refused" or if the command hangs, there is a network problem concerning port 515. If the connection is ok, you will get a prompt.

hope it helps,
John K.

Re: remote printer

Sean Lavery — Mon, 20 Oct 2003 11:16:35 GMT

ok.. that didnt work
/adv/seanl (seanl) $telnet 192.99.99.10 515
Trying...
telnet: Unable to connect to remote host: Connection refused

I also found a menu on the copier that lets me ping an ip.. and i can ping all addresses here except for the server I'm trying to print from, but I can still ping from the server to the printer

Re: remote printer

john korterman — Tue, 21 Oct 2003 02:32:41 GMT

Hi again Sean,
the problem is that the lp daemon cannot contact the printserver via port 515. If you are not the networking guy yourself, then ask them to take care that this port is open from the unix machine to the printserver.

regards,
John K.

Re: remote printer

Sean Lavery — Tue, 21 Oct 2003 12:20:27 GMT

so am I opening the port on the copier or the Unix system??? Speaking w/ our local canon rep, he didnt have a clue about opening port 515 on the copier, although he did say i should be using port 9100 for raw printing.. I think I can probably find instructions on this site for opening the port on the unix side if need be (I am the everything guy at my company...)

Re: remote printer

john korterman — Wed, 22 Oct 2003 02:33:41 GMT

Hi Sean,
I do not think that you need to worry about opening a port on the unix machine itself. lp print wil normally use the service defined in /etc/services on the there defined port, normally 515. Try grepping for lp in /etc/services, e.g.:
# grep 515 /etc/services
you will normally see something like this:
printer 515/tcp spooler # remote print spooling

which means that a tcp spooling session (used for lp print) between the unix server and an lp printer will be established in such a way that the unix server aims at port 515 of the printer. However, the print will not leave the unix machine on port 515 - any free port above 1024 will be automatically selected in a tcp session between the unix machine and the printer, assumed that a session can be established (not the case at your site at the moment).
It is important to know if the receiver listens on the port you aim at, but it is difficult to pinpoint. As your supplier says that the printer uses port 9100, you can try to send a network package to the printer on that port; the telnet trick again:

# telnet 192.99.99.10 9100

If there is network connection to the printer on port 9100, and if the printer actually listens on that port, you will get a prompt. This would mean that you have to make the unix machine aim at that port in a printer session. If you, which I expect, get the "connection refused" it means that either the printer does not listen on that port, or the network in between the unix machine and the printer does not allow you to contact the printer on port 9100, i.e. tricky to figure out which is the problem.
However, normal behaviour would be for the printer to listen on port 515; perhaps it does. My guess is that something in your network prevents you from contacting the printer on port 515, but it is only a guess, and I hope that the more networking oriented guys of the forum can help you here.

Hope it helps,
John K.