• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 221
  • Last Modified:

Printer problem - Solaris2.6

Due to a server crash, I had to rebuild a new NIS and print server on Solaris 2.6
I Reinstalled NIS and Print Server with same spooler names.
Problem:
lpstat on client shows printer accepting jobs. but when I submit a job, it doesnot print, but stays in queue. When printed from print server, it prints.
0
bhagawatula
Asked:
bhagawatula
  • 2
  • 2
1 Solution
 
dsernaCommented:
Here are a few things to try:

Verify the tcp listeners are running:
   # pmadm -l -p tcp

   PMTAG          PMTYPE         SVCTAG         FLGS ID
   <PMSPECIFIC>
   tcp            listen         0              -    root
   \x00020ACE000000000000000000000000 - c - /usr/lib/saf/nlps_server #
   tcp            listen         lp             -    root     - - p -
   /var/spool/lp/fifos/listenS5 #
   tcp            listen         lpd            -    root
   \x00020203000000000000000000000000 - p -
   /var/spool/lp/fifos/listenBSD #

   If these services are not running set up a LOCAL printer on the
   printserver with Admintool.

   Command line to setup the listeners:

    # sacadm -a -p tcp -t listen       -c "/usr/lib/saf/listen tcp" -v
`nlsadmin
    -V` -n 9999

    #  pmadm -a -p tcp -s lp -i root -m `nlsadmin -o      
/var/spool/lp/fifos/
    listenS5` -v `nlsadmin -V`

    # pmadm -a -p tcp -s lpd -i root -m `nlsadmin -o  \
      /var/spool/lp/fifos/listenBSD -A    
'\x00020203000000000000000000000000'
    ` -v `nlsadmin -V`

    # pmadm -a -p tcp -s 0 -i root -m `nlsadmin -c      
/usr/lib/saf/nlps_serve
    r -A      '\x00020ACE000000000000000000000000'` -v `nlsadmin -V`


    Also make sure that there is a process (lpNet or in.lpd) running which
    listens on tcp port 515:

    #  netstat -a | grep printer
      *.printer            *.*                0      0     0      0 LISTEN






0
 
dsernaCommented:
Sorry the above post meant to go in as a "proposed answer". It sounds like the problem is that the print server is not listening for network print requests. Try the following:


:

Verify the tcp listeners are running:
   # pmadm -l -p tcp

   PMTAG          PMTYPE         SVCTAG         FLGS ID
   <PMSPECIFIC>
   tcp            listen         0              -    root
   \x00020ACE000000000000000000000000 - c - /usr/lib/saf/nlps_server #
   tcp            listen         lp             -    root     - - p -
   /var/spool/lp/fifos/listenS5 #
   tcp            listen         lpd            -    root
   \x00020203000000000000000000000000 - p -
   /var/spool/lp/fifos/listenBSD #

   If these services are not running set up a LOCAL printer on the
   printserver with Admintool.

   Command line to setup the listeners:

    # sacadm -a -p tcp -t listen       -c "/usr/lib/saf/listen tcp" -v
`nlsadmin
    -V` -n 9999

    #  pmadm -a -p tcp -s lp -i root -m `nlsadmin -o        
/var/spool/lp/fifos/
    listenS5` -v `nlsadmin -V`

    # pmadm -a -p tcp -s lpd -i root -m `nlsadmin -o  \
      /var/spool/lp/fifos/listenBSD -A      
'\x00020203000000000000000000000000'
    ` -v `nlsadmin -V`

    # pmadm -a -p tcp -s 0 -i root -m `nlsadmin -c      
/usr/lib/saf/nlps_serve
    r -A      '\x00020ACE000000000000000000000000'` -v `nlsadmin -V`


    Also make sure that there is a process (lpNet or in.lpd) running which
    listens on tcp port 515:

    #  netstat -a | grep printer
      *.printer            *.*                0      0     0      0 LISTEN

0
 
bhagawatulaAuthor Commented:
Trying it now, will update posting as soon as I get a result
--Thanks
0
 
bhagawatulaAuthor Commented:
Thank you,
Adding a local printer solved the problem.
0

Featured Post

Upgrade your Question Security!

Add Premium security features to your question to ensure its privacy or anonymity. Learn more about your ability to control Question Security today.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now