- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Setting up non networked printers
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-15-2003 05:19 AM
04-15-2003 05:19 AM
I have a customer who doesnt use networked printers, instead they have printers hanging off of individual PCs'. How can i configure these printers to be usable from HP-UX, are they set up as remote printers? I have tried using SAM but dont understand all the fields it is asking me for for example is it BSD or not ? remote printer name?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2003 05:27 AM
04-15-2003 05:27 AM
Re: Setting up non networked printers
# lpstat -t
scheduler is running
no system default destination
device for support4si: /dev/null
device for scott: /dev/null
remote to: 192.0.1.14 on 192.0.1.14
support4si accepting requests since Jun 25 13:04
scott accepting requests since Apr 15 14:20
printer support4si is idle. enabled since Jun 25 13:04
fence priority : 0
printer scott now sending scott-25 to 192.0.1.14. enabled since Apr 15 14:20
fence priority : 0
scott-25 root priority 0 Apr 15 14:25 on scott
profile 2491 bytes
connection to 192.0.1.14 is down
ssihp13: waiting for 192.0.1.14 to come up
As you can see I get the message that it is waiting for the PCs' IP address to "come up". The PC is up and the printer is online, so I guess I configured it wrong.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2003 05:30 AM
04-15-2003 05:30 AM
SolutionYou need to specify three basic items. The first a name of the queue on your server; the second is an IPaddress or (better) a hostname of the remote printer; and the third is the queue supported by the remote printer.
If you aren't using DNS, define your printer (PC) hostnames in 'etc/hosts'.
The remote print queue is usually something like "text1" or "lpt1_passthru", etc. depending on the remote offering.
The BSD toggle (as I recall) limits the size of the job number generated.
Regards!
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2003 05:33 AM
04-15-2003 05:33 AM
Re: Setting up non networked printers
Remember that the PC hosting the attached printer must run some form of LPD/LPR software(Line Printer Daemon/Line Printer Remote).
Regards!
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2003 05:34 AM
04-15-2003 05:34 AM
Re: Setting up non networked printers
Its that 3rd bit that gets me, what do you mean by
"and the third is the queue supported by the remote printer."
What do you mean by remote offering, should i be looking up on the PC what the printer is called? How do i do that?
Cheers,
Scott.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2003 05:36 AM
04-15-2003 05:36 AM
Re: Setting up non networked printers
ooooohhhhh its sooo much easier on UNIX!!!!!!!!!
S.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2003 05:42 AM
04-15-2003 05:42 AM
Re: Setting up non networked printers
Yes, you must install and configure the LPR/LPD print services in Windows before anything will work. And ALWAYS specify the BSD option. It limits the printer ID number to 3 digits, a requirement for BSD style print servers (and Windows is based on a BSD model).
Bill Hassell, sysadmin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2003 06:04 AM
04-15-2003 06:04 AM
Re: Setting up non networked printers
Thanks for your help,
Scott.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-18-2003 06:04 AM
04-18-2003 06:04 AM
Re: Setting up non networked printers
You can use microsoft client shared printers when you have Samba ( or CIFS 9000) installed on your server.
In that case you do not need any additional LPR/LPD software for your clients. You just have to enable File and Print Sharing on the pc's.
Once samba is installed on your unix you can verify the availibility of a printer share with
#smbclient -L pcname
If there is a printer share it will be displayed.
Next you can add the printer with
#lpadmin -punixprintername -v -i/opt/samba/smbprint
The lp service will call the smbprint script.
This script contains the following line to send the printjob to the windows client
cat $FILE | smbclient $service -P
The smbprint.sysv interface script is located somewhere under the samba directory.
Regards