HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Printer issue
Operating System - HP-UX
1832529
Members
7496
Online
110043
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
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
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
02-06-2006 05:45 AM
02-06-2006 05:45 AM
Printer issue
Hi
I have a weird printer setup. The physical HP printer is located in Dallas and has an IP address. The HPUX 11.0 system managing the print queues is located in Atlanta, GA. The TCP/IP port for these printqueus is located on a Windows 2003 box in California. There is a firewall between Atlanta and California but ports are wide open. I tested by pinging from the HPUX machine to the Windows 2003 box.
Now I have an existing printque called prndal1 on the HPUX box that points to the Windows 2003 box & works fine. Using SAM, I added 2 other printqueue (s) called prndal2, prndal3 exactly similar to prndal1 (remote printer). It asked me for the printer name (prndal2), remote system name (IP address of Windows 2003 server) and remote printer name (prndal2). Stopped lpsched and re-started for grins. However when I print from the HPUX machine (lp -dprndal2 test.txt) and check status using lpstat -p, it does not work. Can someone help here. Where does HPUX store printer configuration. Thx
Ragu
I have a weird printer setup. The physical HP printer is located in Dallas and has an IP address. The HPUX 11.0 system managing the print queues is located in Atlanta, GA. The TCP/IP port for these printqueus is located on a Windows 2003 box in California. There is a firewall between Atlanta and California but ports are wide open. I tested by pinging from the HPUX machine to the Windows 2003 box.
Now I have an existing printque called prndal1 on the HPUX box that points to the Windows 2003 box & works fine. Using SAM, I added 2 other printqueue (s) called prndal2, prndal3 exactly similar to prndal1 (remote printer). It asked me for the printer name (prndal2), remote system name (IP address of Windows 2003 server) and remote printer name (prndal2). Stopped lpsched and re-started for grins. However when I print from the HPUX machine (lp -dprndal2 test.txt) and check status using lpstat -p, it does not work. Can someone help here. Where does HPUX store printer configuration. Thx
Ragu
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-06-2006 06:07 AM
02-06-2006 06:07 AM
Re: Printer issue
Try adding from the command line instead:
lpadmin -v/dev/null -mrmodel -pprndal2 -ormwindowsserver.yourdomain.com -orpprndal2
Don't use ip address - use DNS - that way if they change the ip address - you don't have to re-create the queue...
As far as where things are:
/etc/lp
/var/spool/lp
/var/sam/lp
/var/adm/lp
Check for errors in /var/adm/lp/log
Run the scheduler with -v:
lpsched -v
Compare the interface scripts in /etc/lp with prndal1
Rgds...Geoff
lpadmin -v/dev/null -mrmodel -pprndal2 -ormwindowsserver.yourdomain.com -orpprndal2
Don't use ip address - use DNS - that way if they change the ip address - you don't have to re-create the queue...
As far as where things are:
/etc/lp
/var/spool/lp
/var/sam/lp
/var/adm/lp
Check for errors in /var/adm/lp/log
Run the scheduler with -v:
lpsched -v
Compare the interface scripts in /etc/lp with prndal1
Rgds...Geoff
Proverbs 3:5,6 Trust in the Lord with all your heart and lean not on your own understanding; in all your ways acknowledge him, and he will make all your paths straight.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-08-2006 11:26 AM
02-08-2006 11:26 AM
Re: Printer issue
Thx, Geoff for your reply. I removed it from SAM and did it by command line. I presume no model info is required. I still cannot print. /var/adm/lp/log shows the name of the printjob.
Here is what I need. Help me "duplicate the existing printque prndal1 to prndal2. I need to change the IP, but everything else should be status quo. SAM does not have an option to edit or copy an existing printque. I looked at /etc/lp/interface and did a diff of prndal1 and prndal2, but it did not return anything. Where is the IP info stored. Thx
Ragu
Here is what I need. Help me "duplicate the existing printque prndal1 to prndal2. I need to change the IP, but everything else should be status quo. SAM does not have an option to edit or copy an existing printque. I looked at /etc/lp/interface and did a diff of prndal1 and prndal2, but it did not return anything. Where is the IP info stored. Thx
Ragu
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
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP