Web server troubleshooting access environment In order to enable the staff to keep abreast of the spirit of the superior instructions and unit notifications and other information, the unit leader decided to set up a Web server in the LAN to ensure that 26 ordinary workstations in the LAN can successfully access the Web. Upon receiving the leadership request, the network administrator immediately selected a computer with a fairly good hardware performance, installed the Windows Server 2003 system, and set up a Web server in it; in order to ensure the speed of Web access, the network administrator would also use the Web server and the LAN. The normal workstations are connected to the same switch at the same time and are guaranteed to be in the same working subnet. In normal times, some Windows XP systems are installed on some common workstations, and some Windows Vista systems are installed. However, regardless of the operating system installed, they can quickly access various types of information posted to the Web server. The failure phenomenon of Web server troubleshooting is not good for a long time. When LAN users perform Web access, they encounter an inexplicable failure phenomenon: no matter which type of system comes with the IE browser access unit posted to the Web server. When the information is notified, the web server system forcibly requires the input of the user name and password information for identity verification; in fact, the network administrator does not perform the authentication setting on the web server at all, and the network administrator finds the web when the related settings are carefully checked. The server system allows any user to perform anonymous login access. What is the reason for the system to force the user to log in? What is even more incredible is that even if the network administrator correctly enters a valid user account for logging in to the web server, or even enters the super user account of the corresponding system, it cannot successfully log in to the web server. What is going on? Is it a problem with the network line? Or is the working state of the web server abnormal? There are still other unknown problems …… Web server troubleshooting analysis 1. Test line connectivity In order to judge whether the line connectivity is normal, the network administrator first logs into the switch background management system, and switches the system into the global Configure the status. In this state, execute the “disdia” string command. From the subsequent switch diagnosis result information, the network administrator sees that the working status of each switch port of the switch is in the “UP” state, which indicates the switch port. The working status is normal. After that, the network administrator randomly tested the connectivity of the Internet cables of several common workstations and found that the cables were connected. When the IP address of the Web server was tested using the ping command, the IP address of the Web server was found to be pinged. This shows that the connectivity of the LAN network line is normal; since the network line is unblocked, then the client system should access the Web server in the default state should be normal, and now the access is not normal, most of the problems appear in the Web server “ On the body”. 2, re-check the authentication settings Since the login dialog box appears on the system screen, it means that the Web server must have the authentication function enabled at a certain location; for this reason, the network administrator decides to perform authentication-related settings on the Web server. check again. Log in to the web server system with system administrator privileges, open the system's “Start” menu, and then click the “Settings” and “Control Panel” command to double-click from the pop-up system control panel window. ; management tool & rdquo; icon, then expand the IIS console interface, select the host name of the target web server, and right-click the host name, then click the "properties" button in the shortcut menu to enter the properties of the target Web site Dialog; click on the "Directory Security" tab in the Properties dialog box, find the "Authentication and Access Control" location, click the "Edit" button at the corresponding location, and then pop up from it. In the settings window, the network administrator first selected the option "Integrated Windows Authentication", "Anonymous Access", and found that the web server could not be successfully logged in, and then the selected status of these setting options was canceled, but no matter how Set, the above symptoms still exist. Later, the network administrator finds the home directory of the web server, opens the property setting window of the corresponding home directory, enters the "Security" tab page of the window, and sees that the directory allows any user to access, obviously the web server accesses. A failed failure, regardless of the authentication settings. 3, try to adjust the authorization mode. Since entering any account can not successfully access the information published to the Web server, the network administrator began to suspect that the authorization mode of the Web server may have problems, so immediately search the Internet for relevant information, and the network prompts the authorization mode is improper. It can also cause a failure to access the web server. When you see such a prompt, the network administrator does not do it, and then opens the web server system's “Start” menu, and expands the “Settings” and “Control Panel” window by double-clicking the window. The "Authorization" function icon opens the authorization mode setting dialog box. The network administrator sees that the target web server system uses the "per server" authorization mode by default, and finds that the number of user connections is set to <10&rdquo ;, obviously, such a setting is likely to cause the failure of any account to access the Web server successfully; for this reason, the network administrator tries to adjust the authorization mode of the target Web server to "Every device or user" option Then select the "I agree" option in the per-device or per-customer authorization box. I thought that restarting the Web server system would solve the problem. In fact, the adjustment of the server authorization mode did not play any role at all. 4. Address conflict implicated access In the case of trying to adjust various possible settings, there is no result. A user in the LAN suddenly calls the network administrator to say that one of their newly used printers is set to the network printing state. How long does it take to print normally? When I heard such a fault description, the network administrator immediately flashed a thought in mind, did the network printer affect the working state of the Web server? With the mentality of trying, the network administrator immediately went to the network printer site, logged into the network printer management page, and when viewing the relevant network setting parameters, the print log page actually prompts that there is an IP address conflict phenomenon; further check for conflicts. When the IP address, the network administrator suddenly dumbfounded, the conflicting IP address is actually the address used by the Web server host in the unit LAN, which is also the pressure of the clock and the sun is not smashed & Psi; server. Originally, in order to facilitate user management and maintenance, the network printer is also enabled to run a web service in the default state. The print user can log in to the web management interface to remotely modify various print parameters, but the web service automatically run by the network printer is not allowed. Make anonymous access. When the IP address of the network printer robs the host address of the unit web server, when the Internet user accesses the unit's web server again in the future, the web management page of the network printer may be accessed, and the page does not allow the user to perform anonymous access. Then, the authentication window will pop up on the system screen. At this time, the network administrator can not successfully complete the login operation regardless of any user account in the target web server, unless the user account of the login network printer and the login target web server are logged in. The user accounts are the same. After finding the specific cause of the failure, the network administrator adjusted the IP address used by the network printer in the unit LAN to ensure that the IP address used by the web server host was not illegally robbed, and then restarted the web server host system of the unit. Once again, the network administrator was disappointed. When the client system re-attempts to access the organization's web server, it can normally access various types of information, and the failure of the web server access failure is completely solved. From the above troubleshooting process, the cause of the above failure is actually a small change in the network environment, and this change occasionally affects the working state of other devices in the LAN. If we notice these small changes before we solve the problem, we may be able to carry out targeted thinking and association, so that the network failure will naturally not be detoured.