- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- lp problems
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
04-08-2002 02:56 AM
04-08-2002 02:56 AM
I have tried stopping/starting the spooler etc. and am getting nowhere fast!
Thanks for any help...
J
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2002 03:00 AM
04-08-2002 03:00 AM
Re: lp problems
seems to be a name resolution problem, did you check your /etc/hosts file? Try to send the printjob to IP- adress first to confirm it.
Allways stay on the bright side of life!
Peter
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2002 03:14 AM
04-08-2002 03:14 AM
Re: lp problems

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2002 03:18 AM
04-08-2002 03:18 AM
Re: lp problems
Then..
resinstall printer by using 'jetadmin' and nothing else...
Regards,
Ceesjan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2002 03:22 AM
04-08-2002 03:22 AM
Re: lp problems
This is definately a lookup problem.
If you use DNS the /etc/resolv.conf file must
have permissions of at least 444 .
ping will work ok as will nslookup, but
bad permissions will make Jetadmin fail with hpnpf not being able to resolve the hostname of the printer.
CHECK permissions on these:
/tmp : 777
/etc/hosts : 444
/etc/resolv.conf (if it exists) : 444
Steve Steel
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2002 03:26 AM
04-08-2002 03:26 AM
Re: lp problems
What is the result of the command "nslookup ehqprt006".
If it doesn't return the correct IP address of the printer (what I think will be the problem), you need to check your /etc/hosts or DNS server (or NIS server).
Is the printername absolutely correct ?
What is it's IP address, can you ping it ? Can you do a reverse lookup (nslookup
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2002 05:24 AM
04-08-2002 05:24 AM
SolutionOnce the address has been reinstated, if ping still does not work, the printer may not have the correct gateway (router) in the configuration. All network devices need a minimum of 3 values: IP-address, subnet mask and gateway.
Once ping to IP-address responds, now check the hostname with nslookup. If there is no such device, then the IP-to-name connection in /eetc/hosts or DNS has been broken. For /etc/hosts, just edit the file. However, if you have a file called /etc/resolv.conf, then what nslookup says it used to first determine the address, as in:
# nslookup bambam
Using /etc/hosts on: rebel
looking up FILES
Trying DNS
Name: bambam.atl.hp.com
Address: 156.94.386.491
In this case, the hostname lookup was directed to look in /etc/hosts (FILES) and not finding the name there, tried DNS and resolved the name. The order was dictated by /etc/nsswitch.conf (which you may not have, but should create if you have /etc/resolv.conf). To avoid DNS updating problems, always put printer names and IP's into /etc/hosts and specify:
hosts: files[NOTFOUND=continue UNAVAIL=continue] dns [NOTFOUND=return UNAVAIL=continue TRYAGAIN=return]
in /etc/nsswitch.conf. This will provide a more reliable (and faster)way to resolve important hostnames and IP addresses.
Note also that HP's JetDirect software does not need a hostname, as it can use the IPP address. To fix you printer, use removequeue to remove the printer, verify it is working:
/opt/hpnp/bin/hpnpadmin -v IP-address
If you get back a bunch of stats, all is well. Then add the printer back with addqueue as in:
addqueue -h 156.345.678.90 -q my_local_print_queue
Bill Hassell, sysadmin