Using Windows Server 2008 as the print server platform is a very good choice because it provides powerful print management capabilities to meet our various printing needs. However, because it is powerful, complex, and a system platform that is not so familiar to most administrators, it is cumbersome to troubleshoot printing failures. Many managers seem to be helpless and don't know where to start. This article will combine your own practice and draw on the experience of peers and netizens to summarize the printing troubleshooting ideas and steps under Windows Server 2008, and hope to help everyone.
From the user's point of view, printing failures are nothing more than "everyone can't print", "some users can't print", "only one user can't print". The author below uses this as a clue to analyze the reasons for printing errors and talk about the corresponding troubleshooting ideas and steps.
1. Everyone can't print
In this case, we can basically conclude that the problem with the printer itself is not a network problem. The troubleshooting ideas suggested by the author are:
(1). Regular inspection. We can check the printer in person. For Windows Server 2008, you can check the status of the printer through the printer's status page (enter the printer's IP address in the browser). If there are no problems, you should check the print server's event log and find printer-related error and warning messages from the log to determine the error.
(2). Check the print queue. Check if the printer is paused in the Print Service Manager, or if there is a document error. If this is the case, right-click on the documents and select the Cancel command to remove them. (Fig. 1)
(3). Check the 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 be because the IP address changes and the print port points to the wrong IP address. In this regard, we also need to check the status of the subnet where the printer is located.
(4). Check the network. We can ping the printer's IP address with a ping command on a host. If the IP address of the printer cannot be pinged from any host, this indicates that the printer may be down or the network is disconnected. In addition, there may be a problem with the printer's network card failure or the switch or router connected to the printer.
Previous 12 3 4 5 6 Next Read more
I believe many people will be attracted by the powerful security features of Windows Server 2008 sys
In a LAN working environment, it is quite common for a network to fail. Finding faults and resolving
Windows Server 2008 disks are divided into MBR and GPT partitions. This article only discusses MBR
Using Windows Server 2008 as the print server platform is a very good choice because it provides pow
Win2008 how to install iis Windows2008 installation iis method graphic tutorial
Understand the common skills of windows2008
Windows 2008 install raid driver
Windows Server 2008 shared resource access shortcut
Optimize Windows Server 2008 to improve Internet efficiency
Windows XP environment changes Boot.ini file
Windows 2008 R2 remote desktop authorization configuration graphic tutorial
How to migrate Windows 2003 to Windows 2008
Windows server 2008 IE enhanced security configuration shutdown method
Windows Server 2008 R2 Managed Service Account (MSA) Features
Microsoft announced Windows Server 2008 R2 final release date
NT Server Frequently Asked Questions Jinghua
Microsoft launches new website Want to accelerate the adoption of Windows 10 speed
Wonderful: system startup speed question and answer highlights
Baidu cloud housekeeper use skills
Common problems with Win7 watching videos
Win8.1 picture password creation method