To check printing from a SunOS 4.1 client to a SunOS 5.x print server:

1. Check the basic functions of the LP print service on the print server, if you have not done so already.

   For instructions, see "To check the basic functions of the LP print service: ". Make sure that the printer works locally before trying to figure out why nothing prints when a request is made from a print client.

   ---

   Note -

   You should be logged in as superuser or lp on the system specified in the following steps.

   ---

2. Make sure that the print client is accessible.

   1. On the SunOS 5.x print server, send an "are you there?" request to the print client.

      print_server# ping print_client print_client is alive

      If you receive the message print_client not available, you may have a network problem.

3. On the print client, verify the printer is set up correctly.

   # lpr -P luna /etc/fstab lpr: cannot access luna #

   This command shows whether the print client is working. The above example shows that the print client is not working correctly.

4. Make sure that the lpd daemon is running on the print client.

   1. Verify the lpd daemon is running.

      # ps -ax | grep lpd 118 ? IW 0:02 /usr/lib/lpd #

      This command shows if the lpd daemon is running on the print client. The above example shows that the daemon is running.

   2. On the print client, start the lpd daemon.

      # /usr/lib/lpd &

5. On the print client, make sure that there is a printcap entry identifying the printer.

   1. Verify the printer is known.

      # lpr -P mercury /etc/fstab lpr: mercury: unknown printer #

      The above example shows that the /etc/printcap file does not have an entry for the specified printer.

   2. If there is no entry, edit the /etc/printcap file and add the following information:

      printer-name|print-server:\ :lp=:rm=print-server:rp=printer-name:br#9600:rw:\ :lf=/var/spool/lpd/printer-name/log:\ :sd=/var/spool/lpd/printer-name:

      The following example shows an entry for printer luna connected to print server neptune.

      luna|neptune:\ :lp=:rm=neptune:rp=luna:br#9600:rw:\ :lf=/var/spool/lpd/luna/log:\ :sd=/var/spool/lpd/luna:

   3. Create a spooling directory (/var/spool/lpd/printer-name) for the printer.

6. Make sure that the print client lpd is not in a wait state by forcing a retry.

   If the print server is up and responding, the print client lpd may be in a wait state before attempting a retry.

   1. As superuser on the print client, invoke the lpc command.

      The lpc> prompt is displayed.

   2. Restart the printer.

   3. Quit the lpc command.

      The shell prompt is redisplayed.

      # lpc lpc> restart luna luna: no daemon to abort luna: daemon started # quit $

7. Check the connection to the print server.

   1. On the print client, become superuser, and check the printer log file.

      # more /var/spool/lpd/luna/log

      Frequently, no information is displayed.

   2. Also check the printer status log.

      # more /var/spool/lpd/luna/status waiting for luna to come up #

   3. If the connection is all right, on the print server, verify the print server is setup correctly.

      # lpstat -t scheduler is running system default destination: luna device for luna: /dev/term/a luna accepting requests since May 20 17:45 1997 printer luna now printing luna-314. enabled since May 20 17:45 1997. available. luna-129 root 488 May 20 17:47 #

      The above example shows a print server that is up and running.

      If the print server is not running, go back to Step 1 before continuing.