When nothing prints, there are three general areas to check:
The printer hardware
The network
The LP print service
If you get a banner page, but nothing else, this is a special case of incorrect output. See "Troubleshooting Incorrect Output".
The hardware is the first area to check. As obvious as it sounds, you should make sure that the printer is plugged in and turned on. In addition, you should refer to the manufacturer's documentation for information about hardware settings. Some computers use hardware switches that change the characteristics of a printer port.
The printer hardware includes the printer, the cable that connects it to the computer, and the ports into which the cable plugs at each end. As a general approach, you should work your way from the printer to the computer. Check the printer. Check where the cable connects to the printer. Check the cable. Check where the cable connects to the computer.
Problems are more common with remote print requests--those going from a print client to a print server. You should make sure that network access between the print server and print clients is enabled.
If the network is running the Network Information Service Plus (NIS+), see the NIS+ and FNS Administration Guide in the Solaris 2.6 System Administrator AnswerBook for instructions to enable access between systems. If the network is not running the Network Information Service (NIS) or NIS+, before you set up print servers and print clients, include the Internet address and system name for each client system in the /etc/hosts file on the print server. Also, the Internet address and system name for the print server must be included in the /etc/hosts file of each print client system.
For printing to work, the LP scheduler must be running on both the print server and print client. If it is not running, you need to start it using the /usr/lib/lp/lpsched command. If you have trouble starting the scheduler, see "How to Restart the Print Scheduler".
In addition to the scheduler running, a printer must be enabled and accepting requests before it will produce any output. If the LP print service is not accepting requests for a printer, the submitted print requests are rejected. Usually, in that instance, the user receives a warning message after submitting a print request. If the LP print service is not enabled for a printer, print requests remain queued on the system until the printer is enabled.
In general, you should analyze a printing problem as follows:
Follow the path of the print request step-by-step.
Examine the status of the LP print service at each step.
Is the configuration correct?
Is the printer accepting requests?
Is the printer enabled to process requests?
If the request is hanging on transmission, set up lpr.debug in syslog.conf to display the flow.
If the request is hanging locally, examine the lpsched log (/var/lp/logs/lpsched).
If the request is hanging locally, have notification of the printer device errors (faults) mailed to you, and re-enable the printer.
The procedures found in "Troubleshooting Printing Problems" use this strategy to help you troubleshoot various problems with the LP print service.
If basic troubleshooting of the LP print service does not solve the problem, you need to follow the troubleshooting steps for the specific client/server case that applies:
SunOS 5.x print client using a SunOS 5.x print server (for instructions, see "To check printing from a SunOS 5.x client to a SunOS 5.x print server:")
SunOS 5.x print client using a SunOS 4.1 print server (for instructions, see "To check printing from a SunOS 5.x client to a SunOS 4.1 print server:")
SunOS 4.1 print client using a SunOS 5.x print server (for instructions, see "To check printing from a SunOS 4.1 client to a SunOS 5.x print server: ")