Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Configuring HP LaserJet 9050dn network printer with Sun Solaris 10 box

Status
Not open for further replies.

techincaladmin

Technical User
Jul 5, 2009
26
QA
Hi there,

I have a Sun Solaris(SPARC) box running solaris 10, i m trying to configure Hp LaserJet 9050dn printer with ref to Sun DOC

Solaris 10 TBD??

HP Jetadmin for Solaris[TM] Operating Environment.. not available for download(Solaris 10)

Kindly suggest me some appropriate method to follow...
 
Is it a network printer, or directly connected to your Solaris system? If it's directly connected, using what kind of cables?

What method(s) have you tried so far, and where do you get stuck? (I don't have access to that URL).

Annihilannic.
 
thanks Annihilannic for replying..

Status is we have network printer under our Domain, i have gathered the path through windows domain added host as under
\\ITSCLSPRN1.xx.xxx.xx\MITSB00FP09BL for the specified printer.

Now i need to get network access for my Solaris 10 box so that it can print through domain added printer.

 
The simplest way to do it would be to install the Microsoft "Print Services for Unix" (also known as "TCP/IP Print Services" on some versions of Windows) on the print server, if you have admin rights, or if the Windows admins are friendly. :) This will make the Windows print server behave like a standard Unix LPD print server, listening on port 515.

Then you can configure a local print queue using the following:

Code:
lpadmin -p mitsb00fp09bl -s ITSCLSPRN1.xx.xxx.xx!MITSB00FP09BL

Annihilannic.
 
bash-3.00# lpadmin -p mitsb00fp09bl -s ITSCLSPRN1.xx.xxx.xx!MITSB00FP09BL
bash: !MITSB00FP09BL: event not found

 
Bash evilness. Either escape the ! or use a real shell. :)

Code:
lpadmin -p mitsb00fp09bl -s ITSCLSPRN1.xx.xxx.xx\!MITSB00FP09BL

Annihilannic.
 
# lpadmin -p mitsb00fp09bl -s ITSCLSPRN1.qu.edu.qa\!MITSB00FP09BL
lpadmin: Unknown option 's'!
 
That's odd. Perhaps your system has CUPS installed instead of the standard BSD style printer client. Do you get similar output to these commands?

Code:
$ pkginfo SUNWpcu
system      SUNWpcu Solaris Print - Client, (usr)
$ which lpadmin
/usr/sbin/lpadmin
$ grep /usr/sbin/lpadmin /var/sadm/install/contents
/usr/sbin/lpadmin f none 0555 root lp 8953 42052 1106350196 SUNWpcu
$ ps -ef | grep [c]ups
$

Annihilannic.
 
#pkginfo SUNWpcu
system SUNWpcu Solaris Print - Client, (usr)

# which lpadmin
/usr/sbin/lpadmin

#grep /usr/sbin/lpadmin /var/sadm/install/contents
/usr/sbin/lpadmin f none 0555 root lp 8953 42052 1106350196 SUNWpcu

#ps -ef | grep [c]ups
root 16979 1 0 13:08:17 ? 0:06 /opt/sfw/cups/sbin/cupsd
 
#lpstat -t
scheduler is not running
no system default destination
system for mitsb00fp09bl: ITSCLSPRN1.xx.xxx.xx (as lpd://ITSCLSPRN1.xx.xxx.xx/printers/MITSB00FP09BL#Solaris)
mitsb00fp09bl accepting requests since Wed Sep 16 09:24:22 2009
Failed to get printer info for mitsb00fp09bl: not-found
Failed to get job list: bad-argument

I have tried this command on another solaris box.. :(
 
#lpstat -t
scheduler is running
no system default destination
system for mitsb00fp09bl: ITSCLSPRN1.qu.edu.qa (as printer IP_10.10.90.17)
mitsb00fp09bl accepting requests since Sep 16 09:55 2009
printer mitsb00fp09bl faulted printing mitsb00fp09bl-0. enabled since Sep 16 09:55 2009. available.
server ITSCLSPRN1.qu.edu.qa not responding

This is another identical server... :(
 
I'm a little confused because you seem to have CUPS installed and running, however the "lp" utilities are the standard Unix ones. Do you know whether your site uses CUPS or standard "lp"?

Is the printer working on the second server? The print queue appears to have been configured on that one to send directly to the printer's IP address (however the fact that the last job was "faulted" is not encouraging).

On the first server you will need to start the LP scheduler by running lpsched, then maybe lpstat -t will respond correctly with the print queue status.

Annihilannic.
 
Annihilannic, you are rite CUPs are being installed on first server just to configure the said printer. Unfortunately it is not working after many attempts.

Printer is not working on any of server.

One more thing, i was trying to see the printer through MY Neighbour Network, samba is not showing me contents for PrintServer after entering into printserver domain.

I am fed up now after performing ton of attempts.
 
Hmm... what is the output of these commands:

Code:
sum /usr/sbin/lpadmin
ls -l /usr/sbin/lpadmin

I'm trying to figure out whether it has been replaced by CUPS.

Did you install Print Services for Unix on the Windows print server like I suggested? If so, try removing the existing print queue and re-adding it using the command I suggested:

Code:
lpadmin -x mitsb00fp09bl
lpadmin -p mitsb00fp09bl -s ITSCLSPRN1.xx.xxx.xx\!MITSB00FP09BL

Annihilannic.
 
bash-3.00# sum /usr/sbin/lpadmin
47678 45 /usr/sbin/lpadmin

bash-3.00# ls -l /usr/sbin/lpadmin
lrwxrwxrwx 1 root root 26 Sep 14 10:57 /usr/sbin/lpadmin -> /opt/sfw/cups/sbin/lpadmin

bash-3.00# lpadmin -x mitsb00fp09bl
lpadmin: delete-printer failed: server-error-operation-not-supported

bash-3.00# lpstat -t
scheduler is running
no system default destination
lpstat: get-classes failed: server-error-service-unavailable
lpstat: get-printers failed: server-error-service-unavailable
lpstat: get-printers failed: server-error-service-unavailable
lpstat: get-printers failed: server-error-service-unavailable
lpstat: get-jobs failed: server-error-service-unavailable

bash-3.00# lpstat -a
lpstat: get-printers failed: server-error-service-unavailable

bash-3.00# lpadmin -p mitsb00fp09bl -s ITSCLSPRN1.xx.xxx.xx\!MITSB00FP09BL
lpadmin: Unknown option 's'!
bash-3.00#
 
This is what i am getting from second identical server against same commands.

bash-3.00# sum /usr/sbin/lpadmin
42052 18 /usr/sbin/lpadmin

bash-3.00# ls -l /usr/sbin/lpadmin
-r-xr-xr-x 1 root lp 8953 Jan 22 2005 /usr/sbin/lpadmin

bash-3.00# lpadmin -x mitsb00fp09bl
mitsb00fp09bl: unknown printer

bash-3.00# lpadmin -p mitsb00fp09bl -s ITSCLSPRN1.xx.xxx.xx\!MITSB00FP09BL

bash-3.00# lpstat -t
scheduler is not running
system default destination: mitsb00fp09bl
system for _default: ITSCLSPRN1.xx.xxx.xx (as printer MITSB00FP09BL)
system for mitsb00fp09bl: ITSCLSPRN1.xx.xxx.xx (as printer MITSB00FP09BL)
_default accepting requests since Sep 18 12:45 2009
mitsb00fp09bl accepting requests since Sep 18 12:45 2009
printer _default faulted printing _default-0. enabled since Sep 18 12:45 2009. available.
server ITSCLSPRN1.xx.xxx.xx not responding
printer mitsb00fp09bl faulted printing mitsb00fp09bl-0. enabled since Sep 18 12:45 2009. available.
server ITSCLSPRN1.xx.xxx.xx not responding
bash-3.00#
 

This is what i am getting against second identical server.
I added SFWcprnt.pkg & SFWcups.pkg packages on first server only.

bash-3.00# sum /usr/sbin/lpadmin
42052 18 /usr/sbin/lpadmin

bash-3.00# ls -l /usr/sbin/lpadmin
-r-xr-xr-x 1 root lp 8953 Jan 22 2005 /usr/sbin/lpadmin

bash-3.00# lpadmin -x mitsb00fp09bl
mitsb00fp09bl: unknown printer

bash-3.00# lpadmin -p mitsb00fp09bl -s ITSCLSPRN1.xx.xxx.xx\!MITSB00FP09BL

bash-3.00# lpstat -t
scheduler is not running
system default destination: mitsb00fp09bl
system for _default: ITSCLSPRN1.xx.xxx.xx (as printer MITSB00FP09BL)
system for mitsb00fp09bl: ITSCLSPRN1.xx.xxx.xx (as printer MITSB00FP09BL)
_default accepting requests since Sep 18 12:45 2009
mitsb00fp09bl accepting requests since Sep 18 12:45 2009
printer _default faulted printing _default-0. enabled since Sep 18 12:45 2009. available.
server ITSCLSPRN1.xx.xxx.xx not responding
printer mitsb00fp09bl faulted printing mitsb00fp09bl-0. enabled since Sep 18 12:45 2009. available.
server ITSCLSPRN1.xx.xxx.xx not responding
bash-3.00#
 
Okay, let's ignore the first server with CUPS on it for now.

On the second server, have you run lpsched to start the scheduler?

Have you installed Print Services for Unix on ITSCLSPRN1?

Annihilannic.
 
ya.. I hav startd daemon through svcs for print server n ipp, it has started the scheduler on second server.. Unix print services hav been installed on print server!
 
Okay... can you ping the print server?

Code:
ping ITSCLSPRN1.xx.xxx.xx

Can you connect to the Unix LPD port on the print server?

Code:
telnet ITSCLSPRN1.xx.xxx.xx 515

If it does connect successfully, you can hit Ctrl-] to get the telnet> prompt, and then type close.

If both of those are working, then it must be a name mismatch; are you sure the print queue on the Windows server is called exactly "MITSB00FP09BL"?

Annihilannic.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top