The goal in troubleshooting printing problems, as in troubleshooting any type of problems, is first to isolate and identify the problem and then to determine a course of action to fix it. This section helps you diagnose the printer problems, locate the printing subsystem where the error is occurring, and give you some specific tips for solving the problems. The most likely printing problem you'll encounter is a user who can't print, so we present the troubleshooting procedures with this task as the focus.
This section is somewhat condensed, with all client troubleshooting steps presented together and all server steps presented together. In reality, you would often perform basic troubleshooting on the client before you move on to verifying that the print server is working, and you would move on to the most advanced troubleshooting tasks only after you ascertain for sure where the problem is.
Because no set technique exists to identify where a problem lies, the real difficulty in troubleshooting is determining the cause of the problem. To be able to do this, you must understand the various components involved in printing. A little intuition doesn't hurt, either. (For background about the printing process, you might want to reread the Understanding the Printing Process section before you continue.)
Printing problems usually fall into the following categories:
Try to determine which category the problem is in before getting into details. A process of elimination usually works. Try printing from a couple of client machines. If only one doesn't work, you've narrowed the problem down to that client machine; if all clients fail, try printing from the print server. If this succeeds, you know that the problem lies either in the print server configuration or in network connectivity. Keep trying alternatives until you've isolated the problem as precisely as possible, and then start applying the most common fixes until you solve the problem.
If you've already partially isolated the problem, jump straight to the heading in this section that applies and continue. If you can't solve the problem by following the guidelines provided here, you should at least be able to isolate the problem to a greater degree.
More Info
If you can't resolve the problems by using the information provided here, check out the Microsoft Knowledge Base. Go to http://support.microsoft.com, and click the Search link.Attempting to print from the client machine allows you to see any error messages generated while printing. These messages often uncover the cause of the problem or at least indicate some possibilities.
If the document prints properly, you probably have a user error, in which case you might need to educate the users as to the proper printing procedure. Otherwise, you might have a problem with a particular program, or the printer driver might be improperly configured for the users.
Many administrators use this step later in their troubleshooting process to minimize the number of times they need to visit client systems. To understand whether the problem affects only the client or clients reporting the problem or whether it's more generalized, they start by checking the print server or printing from another client computer such as the one they're currently using.
When a document prints but appears garbled or has some other defect, a compatibility problem exists between the client, the printer driver, and the printer. Make sure that the client is using the proper client printer driver and that the server is also using the proper printer driver.
You might want to try installing a duplicate logical printer to test whether the printer driver is corrupt. If this isn't the problem, try changing the spool settings on the client driver (or, if multiple clients experience the same problem, the server's printer driver). Specifically try changing the following options in the Advanced tab of the printer's Properties dialog box. (See the section entitled Changing Spool Settings, earlier in this chapter, for a more detailed procedure.)
If the document doesn't print properly, error messages frequently appear that might help you identify the problem. Here are some solutions to try:
Some applications experience problems when printing in Windows 2000. Some of the issues you might encounter are listed here:
More Info
More Info For other issues, consult the Printers.txt file on the installation CD for the client operating system if the system is Windows 2000, Windows NT 4, or Windows 95/98. You might also want to check the Microsoft Knowledge Base at http://support.microsoft.com.Administrators often check the print server status before actually going to the client machine because they can do it remotely. Here are some matters to check:
To prevent documents with certain languages from printing slowly, install on the print servers the fonts for all languages that the clients will use to print. To do this, copy the fonts to the %SystemRoot%\Fonts folder on the print server and open the Fonts folder (or reboot the server).
Attempting to print from another client machine helps determine whether the problem lies on the server or on the original client machine. Print a test document from the client system, and then use these guidelines to address the results of the print attempt.
If you've ruled out the clients and the server as the source of the problem but you still can't print any documents on the printer, you need to take a close look at the printer. Pause the print queue, and then go check the actual printer. Are any errors reported on the printer? If you find any paper jams or if the printer is low on toner or needs servicing, the printer usually reports an error message. Make sure that the ready or online light is illuminated and that the printer cable is securely attached, or that the network cable is properly plugged in and the light next to the network port is illuminated (if available).
If you still can't print to the printer, attempt to print a test page directly from the printer. Most printers support this capability. If this works, try configuring a different print server with the printer. If you can print from a different print server, you have a problem with the original print server. If this doesn't work, try pinging the printer to see if you can communicate with it.
If you can't delete documents in the print queue or if documents don't print, the print spooler might be stalled. This also affects any fax services the server is running. To restart the Print Spooler service, follow these steps:
Figure 8-23. The General tab of the Print Spooler Properties dialog box.
Restarting the service is usually a good option—it saves time. Automatic rebooting of the computer is a last option because of other processes that might be interrupted or stopped by a reboot.
Printer location tracking can have its own set of problems, although these are usually related to the way the printers and network are set up. The rest of this section discusses some common problems that you might encounter when using printer location tracking and suggests some courses of action.
This problem usually occurs when a printer isn't named according to the printer location name conventions the company decided to implement. When printer location tracking is enabled, clients by default can locate only printers with location attributes that match the naming convention. To fix the problem, enter the correct location name in the missing printer's Location field.
If the company changes its organizational structure or if you find that the current location-naming scheme needs to be changed, use the following procedure. (Windows 2000 doesn't ship with any tools for bulk editing of objects in Active Directory.)
Use Active Directory Sites and Services to update the sites and subnet names. Enter the new location names in the Location field of each printer that is affected by the location name restructuring. You can also do this with an Active Directory Services Interface (ADSI) script.