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

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

   For instructions, see "To check the basic functions of the LP print service: ".

2. Make sure that the print server is accessible.

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

      print_client# ping print_server

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

3. Make sure that the lpd daemon on the print server is running.

   1. On the print server, verify the lpd daemon is running.

      $ ps -ax | grep lpd 126 ? IW 0:00 /usr/lib/lpd 200 p1 S 0:00 grep lpd $

      If the lpd daemon is running, a line is displayed, as shown in the above example. If it is not running, no process information is shown.

   2. If lpd is not running on the print server, become superuser on the print server, and restart it.

      # /usr/lib/lpd &

4. Make sure that the remote lpd daemon is configured properly.

   1. On the print server, become superuser, and invoke the lpc command.

      # /usr/etc/lpc lpc>

   2. Get LP status information.

      lpc> status luna: queuing is enabled printing is enabled no entries no daemon present lpc>

      Status information is displayed. In the above example, the daemon is not running and needs to be restarted.

   3. If no daemon is present, restart the daemon.

      lpc> restart luna

      The daemon is restarted.

   4. Verify that the lpd daemon has started.

      lpc> status

   5. Quit the lpc command.

      lpc> quit

      The shell prompt is redisplayed.

5. Make sure that the print client has access to the print server.

   1. Check if there is an /etc/hosts.lpd file on the 4.1 print server.

      On a 4.1 print server, if this file exists, it is used to determine whether an incoming print request can be accepted. If the file does not exist, all print client systems have access, so skip steps b and c.

   2. If the file exists, see if the print client is listed in the file.

      Requests from client systems not listed in the file are not transferred to the print server.

   3. If the client is not listed, add the print client to the file.

      ---

      Note -

      If you get this far without pinpointing the problem, the SunOS 4.1 system is probably set up and working properly.

      ---

6. Make sure that the connection to the remote lpd print daemon from the print client is made correctly.

   1. On the print client, become superuser, and verify the lpsched daemon is running.

      # ps -ef | grep lp root 154 1 80 Jan 07 ? 0:02 /usr/lib/lpsched

      The lpsched daemon should be running, as shown in the above example.

   2. Stop the LP print service.

      # lpshut

      The LP print service is stopped.

   3. Restart the LP print service.

      # /usr/lib/lp/lpsched

      The LP print service is restarted.

7. Make sure that the remote print server is identified correctly as a SunOS 4.1 system.