Troubleshooting of Web servers is no longer difficult

Many organizations have set up Web servers to promote and promote themselves. However, if the deployed Web servers do not pass access tests, they may not be able to smoothly publish information. The Web server troubleshooting method recommended below is more common. Now we will summarize it and hope that you can quickly respond to the same type of faults in the future!

Access environment for Web Server troubleshooting

In order to allow the employees of the organization to understand the instruction spirit of the superior and the organization's notice and other information in a timely manner, the Organization's leadership decided to build a Web server in the LAN to ensure that 26 normal workstations in the LAN can smoothly access the Web. The Network Administrator immediately selected a computer with excellent hardware performance, installed Windows Server 2003, and set up a Web Server. To ensure Web access speed, the Network Administrator connects the Web server and the common workstation in the LAN to the same vswitch at the same time and ensures that they are directly in the same working subnet. In normal times, some wks have Windows XP and some have Windows Vista, but no matter what operating system is installed, they can quickly access all kinds of information published to the Web server.

Fault Identification for Web Servers

However, this is not a long time. LAN users encounter an inexplicable fault during Web access: no matter which type of system is used, the Web server system forcibly requires the user name and password to be entered for identity authentication when the browser access organization is used to publish the notification information to the Web server. In fact, the Network Administrator has not configured Authentication Settings on the Web server. When you carefully check the settings, the network administrator finds that the Web server system allows anonymous login access by any user, why does the system force a user to log on? Even though the network administrator correctly enters a valid user account for logging on to the Web server, or even enters a Super User Account of the corresponding system, the administrator cannot log on to the Web server, what is this? Is there a problem with the network line? Or is the Web Server Abnormal? There are other unknown problems ......

Analysis and Solution of Web Server troubleshooting

Web Server troubleshooting analysis 1. Test Line connectivity

To determine whether the connection is normal, the network administrator first logs on to the vswitch background management system, switches the system to the global configuration status, and then runs the "dis dia" string command in this status, from the vswitch diagnostic result information returned later, the network administrator can see that each switch port of the vswitch is in the "UP" status, which indicates that the switch port is working normally.

Then, the network administrator randomly tests the connectivity of the Internet cables of several normal workstations and finds that the cables are connected. When Ping command is used to test the IP address of the Web server, if the peer address can be pinged properly, the connectivity of the LAN network is normal, by default, the client system can access the Web server normally. Currently, access is not normal, and most problems occur on the Web server ".

Web Server troubleshooting analysis 2. Re-check the Authentication Settings

Since the logon dialog box appears on the System screen, it indicates that the Web server must have enabled the authentication function somewhere. Therefore, the Network Administrator decides to re-check the authentication-related settings on the Web server. Log on to the Web server system as a system administrator, open the "Start" menu of the system, and click "Settings" and "Control Panel" commands in turn, double-click the "Administrative Tools" icon in the displayed system control panel, expand the IIS console interface, select the host name of the target Web server, and right-click the host name, click the "properties" command in the shortcut menu to go to The Properties dialog box of the target Web site. Click 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 in the settings window that appears, the Network Administrator selects "Integrated Windows Authentication", "Anonymous Access", and other options, finds that the Web server still cannot be successfully logged on, and then cancels the selected status of these settings, however, no matter how configured, the above fault still exists.

Later, the network administrator finds the Home Directory of the Web server, opens the attribute setting window of the corresponding home directory, and enters the "Security" tab page of the window. The result shows that the directory allows access by any user, obviously, the failure of access to the Web server is irrelevant to the Authentication Settings.

Web Server troubleshooting analysis 3. Try to adjust the authorization Mode

Since no account can be entered to successfully access the organization information published to the Web server, the network administrator began to suspect that the Web server's authorization mode may be faulty, so he immediately searched the internet for relevant information, A prompt on the Internet that the authorization mode is inappropriate can also lead to failure in accessing the Web server. When this prompt is displayed, the network administrator immediately opens the "Start" menu of the Web server system and expands the "Settings" and "Control Panel" windows one by one, double-click the "Authorization" icon in the window to open the authorization mode Setting dialog box. The network administrator can see that the target Web server system uses the "per server" Authorization mode by default, at the same time, it is found that the number of user connections is set to "10". Obviously, this setting may cause failure in accessing the Web server without entering any account. Therefore, the Network Administrator tries to adjust the authorization mode of the target Web server to the "per device or user" option, and then selects the "I agree" option in each device or each customer authorization box, the original thought that restarting the Web server system could solve the problem, but in fact the adjustment of the server authorization mode did not play any role at all.

Web Server troubleshooting 4. address conflict-related access

When trying to adjust various possible settings, a user in the LAN suddenly calls the network administrator and says that the new printer is set to the network printing status, it does not take long to print properly. Hearing such a fault description, the network administrator immediately flashed a thought. Does the Network Printer affect the working status of the Web server? With a try, the network administrator immediately came to the network printer site, logged on to the network printer Management page, and displayed the IP address conflict on the print log page when checking the relevant network settings parameters; when you further check the conflicted IP address, the network administrator suddenly becomes dumb. The conflicted IP address is actually the address used by the Web server host in the LAN, it is no wonder that LAN users cannot successfully access the Web server of the Organization.

Originally, in order to facilitate user management and maintenance, a Web Service is also enabled by default. Print users can log on to the Web management interface to remotely modify various print parameters, only Web services that run automatically by network printers do not allow anonymous access. When the IP address of the Network Printer grabs the host address of the Web server of the organization and the online user accesses the Web server of the organization again in the future, the Web Management page of the Network Printer may be accessed, this page does not allow anonymous access, so the Authentication Window will pop up on the system screen. At this time, no matter whether the network administrator enters any user account in the target Web server, of course, the login operation cannot be completed successfully, unless the user account used to log on to the network printer is the same as the user account used to log on to the target Web server.

After finding the specific cause of failure, the network administrator adjusted the IP address used by the network printer in the LAN to ensure that the IP address used by the Web server host was not illegally used, then, the Web server host system of the Organization was restarted. This time, the network administrator was not disappointed. When the client system attempted to access the Web server of the organization again, various types of information could be normally accessed, so far, the failure of Web server access has been completely solved.

Conclusion

From the above troubleshooting process, the cause of the above fault is actually a small change in the network environment, and this change occasionally affects the working status of other devices in the LAN. If we notice these minor changes before resolving the fault, we may be able to think and associate them accordingly, so that the network fault can be solved without detours.

1. Fun Web Server skill big search
2. Troubleshooting Changyou web Server
3. 8 common Web Server Security Vulnerabilities