- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- lpstat: connection to "printer" down
Operating System - HP-UX
1823065
Members
3050
Online
109645
Solutions
Forums
Categories
Company
Local Language
юдл
back
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
Forums
Discussions
юдл
back
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
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
тАО06-30-2004 09:21 AM
тАО06-30-2004 09:21 AM
lpstat: connection to "printer" down
The scenario ...
*** From HP5470 "oki320val" printer, IP=192.168.40.49
(1). #lpstat -t
scheduler is running
...
device for oki320val: /dev/null
remote to: oki320valnf2 on 192.168.nn.mm
...
connection to 192.168.nn.mm is down
regalhp: waiting for 192.168.nn.mm to come up
...
(2). #ping oki320val or 192.168.nn.mm (OK)
(3). #telnet oki320val (OK, can login)
(4). From our "Data" server - I happen to use HP Jetadmin, at first it cannot find 192.168.nn.mm, then I make it find it and it does.
Can print a test page from the printer while on "data server" - so all that access is OK now.
(5). EVENTUALLY, the "connection" resolves itself - maybe 2 - 3 hours later and the stuff in queue prints and all is well
***********************************************
# lpstat -t | grep oki320val | more
device for oki320val: /dev/null
remote to: oki320valnf2 on 192.168.nn.mm
oki320val accepting requests since Jun 29 17:32
printer oki320val is idle. enabled since Jun 29 17:32
printer oki320val is idle. enabled since Nov 19 13:55
printer queue for oki320val
regalhp: oki320val: ready and waiting
printer queue for oki320val
regalhp: oki320val: ready and waiting
#
Is the fact that there are 2 oki320val printers listed my problem? Any special place I should go to correct this situation so I only have "1" oki320val?
***********************************************
(6). How can I resolve the "connection down problem" ? I would think there is a way to "force" the issue as far as the HP5470 goes
Thanks for any and all help! Sorry so wordy!
Anne
*** From HP5470 "oki320val" printer, IP=192.168.40.49
(1). #lpstat -t
scheduler is running
...
device for oki320val: /dev/null
remote to: oki320valnf2 on 192.168.nn.mm
...
connection to 192.168.nn.mm is down
regalhp: waiting for 192.168.nn.mm to come up
...
(2). #ping oki320val or 192.168.nn.mm (OK)
(3). #telnet oki320val (OK, can login)
(4). From our "Data" server - I happen to use HP Jetadmin, at first it cannot find 192.168.nn.mm, then I make it find it and it does.
Can print a test page from the printer while on "data server" - so all that access is OK now.
(5). EVENTUALLY, the "connection" resolves itself - maybe 2 - 3 hours later and the stuff in queue prints and all is well
***********************************************
# lpstat -t | grep oki320val | more
device for oki320val: /dev/null
remote to: oki320valnf2 on 192.168.nn.mm
oki320val accepting requests since Jun 29 17:32
printer oki320val is idle. enabled since Jun 29 17:32
printer oki320val is idle. enabled since Nov 19 13:55
printer queue for oki320val
regalhp: oki320val: ready and waiting
printer queue for oki320val
regalhp: oki320val: ready and waiting
#
Is the fact that there are 2 oki320val printers listed my problem? Any special place I should go to correct this situation so I only have "1" oki320val?
***********************************************
(6). How can I resolve the "connection down problem" ? I would think there is a way to "force" the issue as far as the HP5470 goes
Thanks for any and all help! Sorry so wordy!
Anne
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-30-2004 02:42 PM
тАО06-30-2004 02:42 PM
Re: lpstat: connection to "printer" down
Don't use JetDirect software (jetadmin which has been obsolete since 1999, and hppi) for a non-HP LAN connection. Normally, no vendor supports the HP proprietary JetDirect protocol on port 9100 but a few vendors appear to have started to try.
Start by deleting both printers using lpadmin -x. Then use SAM to add the OKI printers as 'remote' printers. You must have the OKI's 'internal' printer name (like on any lpr printer server).
There's no way to 'force' the printer to work with incompatible software. Set up the OKI printers as plain lpr printers.
Bill Hassell, sysadmin
Start by deleting both printers using lpadmin -x. Then use SAM to add the OKI printers as 'remote' printers. You must have the OKI's 'internal' printer name (like on any lpr printer server).
There's no way to 'force' the printer to work with incompatible software. Set up the OKI printers as plain lpr printers.
Bill Hassell, sysadmin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-30-2004 03:02 PM
тАО06-30-2004 03:02 PM
Re: lpstat: connection to "printer" down
if the printer is a lpd printer running on an aix node you will need to have your hostname mentioned in /etc/hosts.lpd file for printing onto that printer
Wild guess.
Kaps
Wild guess.
Kaps
Nothing is impossible
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-30-2004 04:01 PM
тАО06-30-2004 04:01 PM
Re: lpstat: connection to "printer" down
If your system in HP-UX 11.x, please make sure that your lpspool subsystem cumulative patch is updated:
(1) PHCO_30431 s700_800 11.11 lpspool subsystem cumulative patch
(2) PHCO_31016 s700_800 11.00 lpspool subsystem cumulative patch
which one of the symptom reported is:
rlpdaemon(1m) doesn't accept hostname starting with digits.
(1) PHCO_30431 s700_800 11.11 lpspool subsystem cumulative patch
(2) PHCO_31016 s700_800 11.00 lpspool subsystem cumulative patch
which one of the symptom reported is:
rlpdaemon(1m) doesn't accept hostname starting with digits.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP