Web server access failure troubleshooting skills

Many companies have set up Web servers, but if you set up a good Web server without access testing, you may not be able to achieve the purpose of successfully publishing information; this is not the case, a Web server access failure failure recommended in this article is more common. Now, we will summarize its elimination process, and hope that we can respond quickly when we encounter the same type of failure again in the future!

In order to let the staff of the unit know the spirit of the superior and the unit notification and other information in time, the unit The 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 will also use the Web server and the LAN. Ordinary workstations are connected to the same switch at the same time, and they 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.

But it’s not a long time, when LAN users are experiencing Web access, they have encountered an inexplicable failure phenomenon: no matter which type of system comes with IE browser access unit posted to the web server notification When the information is used, 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 side at all, and the network administrator finds the web server when carefully checking the related settings. The system allows any user to perform anonymous login access. What is the reason for the system to force the user to log in? It is even more incredible that even if the network administrator correctly enters a valid user account to log in to the web server, even enter the super system corresponding to the system. User accounts can't log in successfully into the web server. What is going on? Is there a problem with the network line? Or is the working status of the web server abnormal? There are other unknown problems...

Test line connectivity

In order to judge whether the line connectivity is normal, the network The administrator first logs in to the switch background management system, and switches the system into the global configuration state. In this state, the "disdia" string command is executed. From the subsequent switch diagnosis result information, the network administrator sees each switch. The working status of the switch port is in the "UP" state, which indicates that the working state of the switch port is normal.

After the network administrator randomly tested the connectivity of the Internet cables of several common workstations, the cable was also connected. When the Ping command was used to test the IP address of the Web server, the other party's address was found. Can also be normally pinged, which shows that the connectivity of the LAN network line is normal; since the network line is unblocked, then the client system should be normal to access the Web server in the default state, now the access is not normal, most problems Appears on the "server" of the web server.

Re-checking the authentication settings

Since the login dialog appears on the system screen, the web server must have the authentication function enabled at a certain location; for this reason, the network administrator decides The authentication-related settings in the web server are rechecked. Log in to the web server system with system administrator privileges, open the system's Start menu, click the Settings and Control Panel commands, and double-click the Administrative Tools icon from the pop-up system control panel window. From the IIS console interface, select the host name of the target web server, and right-click the host name, then click the "Properties" command in the shortcut menu to enter the properties dialog box of the target Web site; click on the properties dialog box In the "Directory Security" tab, find the "Authentication and Access Control" location, click the "Edit" button at the corresponding location, and from the settings window that pops up, the network administrator first selects "Integrated Windows Authentication". , "Anonymous access" and other options, found that still can not successfully log in to the Web server, and then canceled the selected state of these settings, but no matter how you set up, 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, very Obviously the failure of the web server access failure is independent of the authentication settings.

Try to adjust the authorization mode

Because the input of 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 be problematic, so immediately go online Search for relevant information, and if the online authorization mode is improper, it can also cause the failure to access the Web server. When you see such a prompt, the network administrator does not do it, and then opens the "Start" menu of the Web server system, expands the "Settings" and "Control Panel" windows one by one, and double-clicks the "Authorization" function icon in the window. Open 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". Obviously, such a setting is likely to cause Enter the failure of any account to successfully access the web server; for this reason, the network administrator tries to adjust the authorization mode of the target web server to the "per device or user" option, and then select "per device or per customer authorization box" I agree with the "option, I thought it would solve the problem by restarting the Web server system. In fact, the adjustment of the server authorization mode did not play any role at all.

Address conflict implicated access

After trying to adjust various possible settings, a user in the LAN suddenly calls the network administrator to say that they are using a new printer. After setting it to the network printing state, it does not take long 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 it out, the network administrator immediately went to the network printer site and logged into the network printer. When viewing the relevant network setting parameters, the print log page actually prompts that there is an IP address conflict. When further checking the conflicted IP address, the network administrator suddenly becomes dumbfounded. The conflicted IP address is actually the local area network. The address used by the web server host, it is no wonder that LAN users cannot successfully access the unit's web 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 network printer automatically The running web service does not allow 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 fault, 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 unit. The web server host system, this time no longer disappoints the network administrator. When the client system re-attempts to access the unit'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.