- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- remote printer
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-17-2003 06:40 AM
10-17-2003 06:40 AM
remote printer
Thanx
Sean
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-17-2003 06:55 AM
10-17-2003 06:55 AM
Re: remote printer
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-17-2003 06:59 AM
10-17-2003 06:59 AM
Re: remote printer
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-17-2003 07:00 AM
10-17-2003 07:00 AM
Re: remote printer
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
e) /usr/bin/enable local_printer_name
f) /usr/bin/accept local_printer_name
g) /usr/lib/lpsched
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-17-2003 07:03 AM
10-17-2003 07:03 AM
Re: remote printer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-17-2003 07:18 AM
10-17-2003 07:18 AM
Re: remote printer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-17-2003 07:23 AM
10-17-2003 07:23 AM
Re: remote printer
You can check by putting different interface scripts.
lpstat -d prints default printer.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-17-2003 07:24 AM
10-17-2003 07:24 AM
Re: remote printer
Try something like this then:
remsh host cat /etc/passwd > /dev/printer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-17-2003 07:25 AM
10-17-2003 07:25 AM
Re: remote printer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-17-2003 07:32 AM
10-17-2003 07:32 AM
Re: remote printer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-17-2003 07:35 AM
10-17-2003 07:35 AM
Re: remote printer
lpstat -d prints defaulkt printer.
What do you mean by cloeses the connection?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-17-2003 07:49 AM
10-17-2003 07:49 AM
Re: remote printer
/ (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)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-17-2003 07:54 AM
10-17-2003 07:54 AM
Re: remote printer
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-17-2003 08:27 PM
10-17-2003 08:27 PM
Re: remote printer
'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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-20-2003 03:39 AM
10-20-2003 03:39 AM
Re: remote printer
/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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-20-2003 04:01 AM
10-20-2003 04:01 AM
Re: remote printer
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
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-20-2003 04:16 AM
10-20-2003 04:16 AM
Re: remote printer
/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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-20-2003 07:32 PM
10-20-2003 07:32 PM
Re: remote printer
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-21-2003 05:20 AM
10-21-2003 05:20 AM
Re: remote printer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-21-2003 07:33 PM
10-21-2003 07:33 PM
Re: remote printer
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-22-2003 07:57 PM
10-22-2003 07:57 PM
Re: remote printer
As I understand it, port 515 is the remote print spooling port, and is used, say, when a workstation passes a print job to a server for printing. Once the server has the job, it then needs to print it, and does this (for a network attached printer) using e.g. HP JetDirect's hpnpf, which attaches by default to port 9100 of the network printer.
In summary:
port 515 = computer-to-computer transfer
port 9100 = computer-to-printer transfer
Some printers support telnet, http, snmp protocols, e.g. for configuration, but I really would expect those to use the ports at the normal addresses (23, 80, 161) rather than 515 or 9100.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-22-2003 08:45 PM
10-22-2003 08:45 PM
Re: remote printer
you cannot be referring to me, as I am not an expert! Still, I suggest to execute the command:
# telnet 192.99.99.10 9100
because it will try to establish a tcp session between the unixserver on which it is executed and 192.99.99.10
I cannot control the port that the unixserver will use, but I aim at port 9100 on 192.99.99.10
and the telnet protocol is only for getting some packages sent across the network. It is a simple connection check, nothing more than that.
regards,
John K.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-22-2003 11:43 PM
10-22-2003 11:43 PM
Re: remote printer
to test connection to a printer you also can use 'hpnpf' (see man hpnpf).
hpnpf -x "printer-ip" file
to send a file to printer.
Add option -R for only one try to connect and option -l filename for a logfile.
Send us the logfile.
Regards
Volkmar
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-22-2003 11:58 PM
10-22-2003 11:58 PM
Re: remote printer
I've a simmilar problem, so for my experience you should be able to 'telnet "printer_ip"' (without port).
For me it works at HP printer (where I've no problems) and Kyocera printer (where I can't print).
Using hpnpf I get 'Connection refused' from Kyocera (no problems with HP) - at that point I'm working now :-)
Good luck
Volkmar
And yes, the default port is 9100 (preset in hpnpf) - maybe you also can test -p 9101.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-23-2003 12:45 AM
10-23-2003 12:45 AM
Re: remote printer
hpnpf -x 192.99.99.10 -R -l /adv/seanl/canonlogfile testprintfile
heres the log file..
08:42:45 hpnpf[2057]
OpenLog: logging started (/adv/seanl/canonlogfile)
08:42:48 hpnpf[2057] Process: entered
08:42:48 hpnpf[2057] OpenSocket: entered
08:42:48 hpnpf[2057] OpenSocket: using 16K send buffer
08:42:48 hpnpf[2057] MakeConnection: 192.99.99.10, port 9100
08:42:48 hpnpf[2057] Error (connect): Connection refused