How to solve the Web server can ping but can not access

Access to the Web server is a lot of LAN users often have to do a "homework", in the process of frequent visits, many friends have accumulated some Web server access experience, These experiences often help them quickly resolve some glitch that is inaccessible. However, the Web server contributed by the following article can not access the fault phenomenon is quite special. If you do not analyze it carefully, it is easy to take a detour when solving the fault simply by experience. In order to help friends to access the Web server efficiently, the author will now This special network access troubleshooting process is restored, I hope everyone can receive inspiration from it!

Can ping but can not access a certain unit LAN is not large, a total of 18 ordinary computers, plus a Web server installed Windows Server 2003 system, all ordinary computers and Web servers are all connected to one The core switch is managed, and the LAN is shared by the broadband router. In normal times, the operating systems installed and installed in 18 ordinary computers are different. There are Windows XP systems installed, Windows Vista systems are installed, and two computers are still used. Windows 98 systems are still used, but these computers can be used normally. Access the web server in the LAN.

However, in the recent period, when a LAN user accesses the content of the Web server through the Internet Explorer, an authentication dialog box appears on the system screen, asking the user to input the appropriate username and password information; in fact, the Web server There is no authentication enabled at all. It usually allows any user on the LAN to log in and access the site content anonymously. So why is this happening now? What is even more strange is that the network administrator can not successfully pass the authentication of the Web server regardless of whether he enters the legitimate user account of the Web server or enters the super administrator account. What is the reason? When the network administrator attempts to use the Ping command to test the connectivity of the LAN target Web server, it is found that the Web server can be pinged normally. This also proves that the physical connection between the LAN common computer and the Web server is normal; In the case of a failure to access the Web server abnormally, it is likely that there is a problem with the Web server itself.

Check Web Site Access Permissions

At first, the network administrator thought that the Web server itself was improperly set up, causing LAN users to not access properly. Considering that the web server suddenly requires authentication, the network administrator judges that this is definitely the access rights of the web server has been accidentally modified, so immediately enter the Windows Server 2003 server system, click “ start & rdquo; /& ldquo; settings & rdquo; /“Control Panel”, double-click the “Administrative Tools” icon in the Control Panel, and then double-click the IIS Control icon to open the IIS console window of the corresponding system, find the site name corresponding to the target Web server, and then use Right-click the target site name and execute the “Properties” command in the right-click menu to open the property setting window of the target site; click the “Directory Security” tab in the settings window, on the corresponding option settings page. “Authentication and Access Control” click on the “Edit” button to open the settings dialog shown in Figure 1. Here, the network administrator selects or deselects “Anonymous Access” and “ld”; Integrated Windows Authentication & rdquo; options, the web server still has to authenticate, this Explain that this symptom is independent of the access settings of the target web server.

Check server connection restrictions

Because you entered a valid user account or even a super administrator account, you cannot log in to the web server correctly. The network administrator is beginning to suspect that the Windows Server 2003 server system may be against the user. At the same time, the number of connections is limited because once the number of web home directory user connections to the web server is limited, the user who quits the login does not access the site content in the web server anyway. With this in mind, the network administrator first opens the resource manager window of the server system, finds the site home directory of the web server, and right-clicks the directory icon to execute the "property" command in the shortcut menu to open the target site. The property setting window of the home directory; click the "share" tab in the settings window, and in the corresponding option setting page, the network administrator finds that the Windows Server 2003 server system limits the number of user accesses of the directory to 5 So, try to change the parameter to 20, and save the setting operation. When you access the web server again, the same failure phenomenon still occurs.

Afterwards, when the network administrator queried the information about the user connection restriction, it was found that if the authorization mode of the Windows Server 2003 server system was set incorrectly, the number of user connections would be limited. After searching for such a result, the network administrator was secretly excited. It seems that the failure phenomenon that the Web server cannot access can be solved immediately; he immediately opens the "Start" menu of the Windows Server 2003 server system, and then clicks on it. “Set ”/“Control Panel” command, and double-click the "Authorization" option. In the following interface, the network administrator finds that the server system selects the "per server" option by default. At the same time, the number of user connections is displayed as “5”, it is obvious that the parameters here are not set correctly. The network administrator immediately selected the “Every Device or User” option (shown in Figure 2), and then selected the “I agree” option in the Per Device or Per Client Authorization dialog box and finally restarted. The server system; I thought that such an effort would be rewarding, but when I re-accessed the LAN web server from a normal computer, there was an annoying authentication dialog on the system screen.

Unexpectedly find the cause of the fault

When the network administrator has no clue, a LAN user suddenly rushes to the network administrator for help, saying that their department needs to work, recently I bought a network printer, connected the network printer to the core switch of the unit, and set the relevant network printing parameters. All users in their department can use the network printer to print materials normally, but today, he My computer can't use a network printer, and others can print online. Upon hearing the user's request for assistance, the network administrator immediately went to the network printer site, logged into the printer background management interface, and occasionally opened the log page of the network printer, found the IP address of the network printer and the IP address of a computer in the LAN. When a conflict occurs, and then carefully check the conflicting IP address, it is actually the IP address used by the Web server. No wonder the Web server cannot access it properly. The original IP address of the network printer has an unexpected conflict with the IP address it uses.

Originally, for the convenience of management and maintenance, a web service is also running on the network printer. Users can set various Internet access parameters of the network printer through the web-based background management interface, but the network printer The Weh server with the support does not support anonymous access by default. When the IP address set by the user for the network printer conflicts with the web server address, when the LAN user enters the IP address of the web server in the address bar of the IE browser window, the user actually accesses the background login interface of the network printer, which is also Why the authentication dialog appears on the system screen when accessing the web server. At this time, when the Ping command is used to test the connectivity of the Web server, the network printer is tested, so that the network printer can be pinged, but a legal user account needs to be input to access.

After clarifying the cause of the failure, the network administrator immediately modified the IP address of the network printer to ensure that the IP address of the Web server did not conflict with the IP address of other computers. As a result, when accessing the Web server again, it was true. The content of the page can be opened very quickly, and the failure phenomenon that the web server can ping but cannot be accessed is successfully solved.

The final summary

This kind of network failure is not very complicated to solve, and it is sure to find the final cause of the failure. However, this fault reminds us from every angle that every network administrator can not blindly apply the experience to solve network failures. Instead, familiarize yourself with the latest changes in the network environment before troubleshooting, and be familiar with the various network devices in the working environment. Functional characteristics, only know the latest changes in the network and the various characteristics of the network equipment, we will subconsciously think and associate in the event of network failure, the only way to quickly find the specific cause of the failure, and in a timely manner Take measures to quickly resolve network failures.