Windows Server 2008 is incorrectly queued as a print server

Using Windows Server 2008 as a print server platform is a great choice, because it provides powerful print management capabilities to meet our various printing needs. However, because of its power, complexity, and is a system platform that is not so familiar to most administrators, it is troublesome to make a row when encountering a print failure. A lot of managers seem helpless, do not know where to start. This article will combine their own practice and learn from the experience of peers and netizens, on the Windows Server 2008 print debugging ideas and steps to a summary, I hope to help.

From the user's point of view, there are three situations where the print failure is not "everyone can print", "Some users cannot print", and "only one user cannot print." The following author on this as a clue to analyze the causes of printing errors, and to talk about the corresponding wrong way of thinking and steps.

1, everyone can not print

In this case, we can basically determine that the problem is not the printer itself is a network problem. The author suggested that the wrong way of thinking is:

(1). Routine inspection. We can check in front of the printer, for Windows Server 2008来 that the printer's status can be viewed through the printer's status page (the IP address of the printer in the browser). If there is no problem, then you should check the print server's event log and find the printer-related error alert and warning information from the log to make a mistake.

(2). Check the print queue. Check to see if the printer is paused in Print Service Manager, or if there is a document error. If so, right-click the document and select Cancel to remove it. (Figure 1)

(3). Check printer configuration information. If someone maliciously sets the printer to dynamically obtain an IP address, or does not set a reservation for the printer. In this case, if the printer is turned off and restarted, it may change after its IP address, and the print port points to the wrong IP address. In this respect, we also need to check the subnet status of the printer.

(4). Check the network. We can ping the printer's IP address on a single host, and if you cannot ping the printer's IP address from any host, this indicates that the printer may be turned off or the network will be disconnected. In addition, there may be a problem with the NIC of the printer or the switch or router that is connected to the printer.

(5). Retrieves changes to the printer configuration. You can ask or recall when the printer was last printed correctly, and whether the printer's configuration has changed. If the printer has never worked properly, it indicates a problem with the initial configuration. If the configuration of your printer changes, you may recommend that you revert to a previous configuration. If you suspect a print device, we can try uninstalling and reloading the printer driver.

(6). Detect disk space. This is often overlooked and it is necessary to check the free space on the disk where the spool folder is located, because it can also cause a printing failure. If the partition's free space is low or there is no free space, the print server will not be able to create the spool file, so the document will not print. In addition, we should also check the Print folder permission settings, if there is a problem with permissions settings, background printing can not be done. (Figure 2)