Response Policy for server access failure

This is not the case when everyone wants to surf the Internet! It is believed that most people may have encountered an error message indicating that the Web server cannot be accessed. In addition to the hardware devices connected to the network, this error may also be caused by many factors. To eliminate such a fault, you must first start from the bottom layer of network communication, that is, you must first check and confirm whether the "Physical Layer" of the network is faulty. When you confirm that the hardware device connected to the network is not faulty, troubleshooting for faults that cannot be accessed by the Web server is just starting.

　　1. network connection, enabled or not

If the Windows 2000 Server System on the Web server does not enable the network connection function of the local computer, no other client can be connected to the Web server, in this way, the Web server is prone to failures. Therefore, checking whether the network connection function on the server is enabled is one of the important steps to troubleshoot the fault.

When checking whether the network connection function of the server is enabled, you can click the "Start" menu on the system desktop, and then click the "set"/"network and dial-up connection" command in sequence, on the open network connection list page, check whether there is a "Local Connection" icon (1 );

Figure 1

If this icon is displayed, you must double-click it. In the subsequent Local Connection Properties dialog box, check whether the connection status is "connected ", if its status is "disabled", it indicates that the network connection function on the server has not been enabled. At this time, you must right-click the "local connection" icon, run the "enable" command from the shortcut menu to restart the network connection function on the server.

TIPS: if the "local connection" icon is not displayed on the network connection list page, you can click "start"/"run" commands in sequence, in the open system running dialog box, enter the service policy editing command "Services. msc, click OK to open the System Service List window, double-click the "Network Connections" project, and in the service attribute settings window shown in 2, check whether the "Network Connections" service has been started. If not, click the "Start" button and select "automatic" from the "Start type" drop-down list ", click the "application" and "OK" buttons. Then, you can view the "local connection" icon in the network connection List window.

Figure 2

　　2. Whether to disable the IIS Process

As you know, When manually checking for network viruses, you may accidentally close some useful processes. If you accidentally close the IIS process, the Web server on the server cannot be automatically started. When any visitor accesses the Web server, the server cannot be accessed. To eliminate such a fault, you must start the IIS process in time. To check whether the IIS process is disabled, follow these steps:

Indicates that the IIS Process on the current server is accidentally disabled;

In this case, you can click "start", "program", "Management Tools", and "Internet Service Management" commands. In the IIS Console window that appears, right-click the name of the target Web server and run the "Start" command from the shortcut menu to restart the IIS process.

　　3. Route faults and clever Query

If you confirm that the Web server is normal, but the client still cannot access the Web server, then you need to check whether the route information of the network connection is normal. As you know, any workstation that communicates through the TCP/IP network protocol can automatically create a route table information. Based on the route table information, the workstation can easily find the target server, and establish an access connection with the server. Considering the route table information of the local client, the system automatically changes after each restart. Therefore, if you cannot connect to a Web server, you can check whether the local route table information contains the "Default Gateway" information that can access the Web server. If not, you can add it to the local route table information to ensure that the workstation can access the Web server smoothly. To view the local route table information, follow these steps:

Click the start/Run Command, in the open system run dialog box, enter the cmd string command, and click OK to switch the system status to the MS-DOS environment;

Run the "Route PRINT" command in the doscommand line. Then you will see the Route table information in the local workstation on the page 3. If you find that there is no routing information to the "Default Gateway", you can use the Route ADD command to ADD a record to the default gateway, and then the workstation will be able to automatically connect to the default gateway.

Figure 3

In addition, you can also use the built-in Tracert command in Windows to find out whether each router and gateway between the local computer and the Web server work normally, if one of the routers or gateways fails, the Web server access error may occur. When you check Which router or gateway has an error, you can run the "run" command in the system Start Menu. In the displayed dialog box, enter the cmd string command, click OK, switch the system status to the MS-DOS environment, and then execute the Tracert command in the doscommand line, the test results may not take long. If the results contain "<210.73.140.1> reports: Destination net unreachable. ", it indicates that the vro with the IP address" 210.73.140.1 "in the current network cannot be connected successfully, causing the local workstation to be unable to find the Web server.

4. Is the domain name resolved correctly?

If you can use the Ping command to Ping the IP address of the Web server, but you cannot access the content on the server through the Web site, it indicates that the name resolution in your workstation is faulty. To solve such a fault, follow these steps:

First, check whether the local Hosts file contains invalid items for the corresponding Web server. If yes, the local workstation may fail to establish a connection with the Web Server due to domain name resolution errors. When checking the Hosts file information, you can first open the system resource manager window, go to the "% SystemRoot % System32DriversEtc" folder window (% SystemRoot % indicates the specific path of the Windows system) and find the Hosts text file;

Right-click the file, select the "open mode" option from the shortcut menu, and select the "Notepad" program from the lower menu to open the Hosts text file. Next, check whether the text file contains the Address Record of the Web server. If such a record exists, check whether the IP address of the corresponding Web server URL is correct, if it is incorrect, you must modify it correctly and save the file again. In this way, the Hosts file will be able to accurately resolve the Web server URL to the corresponding IP address in the future, so that the local workstation can smoothly access the server.

If your computer uses DNS as the domain name resolution method, you also need to check whether the DNS configuration of the Local Computer is correct, or check whether the DNS server in the local network is faulty. When checking that the DNS configuration is correct, you can first switch the system to MS-DOS working mode and then execute the "Ipconfig/all" command in the doscommand line, on the subsequent result page, check whether the IP address of the local DNS server is set correctly. If the IP address is incorrect, you must open the network attribute settings window to reset the IP address of the DNS server.

　　5. Whether the Web permission is enabled

Sometimes we can establish a connection with the Web server, but we cannot open the webpage content on the server. What is the problem? In this case, it can be basically determined that the network connection between the client and the server is normal. As for the phenomenon that the webpage content cannot be opened, most of the reasons are that the permissions of the Web server are not properly set. At this point, you can follow the steps below to check whether the Web permissions of the server are correctly set:

Right-click my computer on the system desktop, and run the "manage" command from the shortcut menu. In the displayed Computer Management window, expand the "service and application"/"Internet Information Service Manager" options in sequence, as shown in figure 4;

Figure 4

Then, right-click the specified Web server site and execute the "properties" command from the shortcut menu that is opened later. In the subsequent Web site property Setting dialog box, click the "Directory Security" tab and click the "edit" button in the "Anonymous Access and authentication control" settings on the corresponding tab;

Next, in the pop-up "authentication method" Setting dialog box, check whether the "Anonymous Access" function is enabled. If this function is not correctly enabled, may affect access to content on the Web server;

In addition, return to the Web server site attribute Setting dialog box, click the "home directory" tab to see if the "Read File" and "directory browsing" permissions are activated on the corresponding tab page, if you do not activate the service, you must select all of them, so that you may be able to smoothly access the Web server content.

　　6. Target address, restricted by no

If the workstation with the specified IP Address can normally access the content of other Web servers and cannot access the content of the specified server, you must check the server, whether to filter the IP address of the specified workstation, so that the workstation has no right to access the content on the server. When checking whether the server filters the IP address of the specified workstation, you can follow the steps below:

Click Start, programs, administrative tools, and Internet Service Manager commands. In the displayed Internet service console window, right-click the name of the target web server site and run the "properties" command from the shortcut menu;

On the Web server site attribute setting page that appears, click the "Directory Security" tab, and click the "edit" button in the "IP address and domain name restriction" setting area on the corresponding tab, in the edit settings window that opens later, check whether the IP address of the specified workstation is in the "Access Denied" list box. If the IP address has been denied, you must delete it in time, click "OK", and refresh the IIS service to ensure that the workstation with the specified IP Address can access the Web server smoothly.