Troubleshooting of Web server access failure (1)

Many companies have set up Web servers. However, if the deployed Web servers do not pass access tests, they may not be able to smoothly publish information, the following is a common failure in Web server access. We will summarize the troubleshooting process and hope that you can quickly cope with the same type of failure again in the future!

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 the WindowsServer2003 system, and set up a Web server. To ensure the 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, Windows XP is installed on some workstations, and Windows Vista is installed on some workstations. However, no matter what operating system is installed, they can quickly access all kinds of information published to the Web server.

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 ......

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 "disdia" string command, 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 ".