The instance solves the problem that the Web server cannot be accessed.

According to the media report in February 10, accessing Web servers is a "homework" that many LAN users often do. During frequent access, many friends have accumulated some Web server access experience, these experiences often help them quickly solve some small faults that cannot be accessed. However, the failure caused by the failure to access Web servers in this article is quite special. If you do not analyze it carefully and solve the fault simply with experience, most of them will be prone to detours; in order to help your friends efficiently access the Web server, I have now restored this special network access troubleshooting process. I hope you will receive some inspiration!

Can be pinged but cannot be accessed

The local area network of a certain organization is small, with a total of 18 General computers, and a Web Server installed with Windows Server 2003 system. All common computers and Web servers are connected to a manageable core switch, and shared LAN access through a Broadband Router. In normal times, the operating systems installed and used on 18 General computers are different, including Windows XP and Windows Vista, two computers are still running Windows 98, but they can access the Web servers on the LAN.

However, in the recent period, when a LAN User accesses the content of a Web server site through the IE browser, the identity verification dialog box appears on the System screen, asking the user to enter the appropriate user name and password information; in fact, the Web server does not enable the identity authentication function at all. It allows any user in the LAN to log on to and access the site content through an anonymous identity. Why does this happen now? What's even more strange is that the network administrator cannot pass the Web server's identity verification, regardless of the valid user account of the Web server or the super administrator account. Why? When the network administrator tries to use the Ping command to test the connectivity of the target Web server in the LAN, it finds that the Web server can be pinged normally, this also proves that the physical connection line between the LAN common computer and the Web server is normal. when the line is smooth, the Web server may fail to access normally, this is probably because of a problem with the Web server itself.

Check website Access Permissions

At first, the network administrator thought that the Web server was improperly configured, resulting in abnormal access by LAN users. Considering that the Web Server suddenly requires authentication, the network administrator determines that the access permission of the Web Server is accidentally modified, and immediately enters the Windows Server 2003 Server system, click "start"/"Settings"/"Control Panel", double-click the "Management Tools" icon in the control panel, and then double-click the IIS control icon, open the IIS Console window of the corresponding system, find the site name corresponding to the target Web server, right-click the target site name, right-click the "properties" command in the menu to open the attribute settings window of the target site. Click the "Directory Security" tab in the settings window, click "edit" in "authentication and Access Control" on the "Settings" page to open the Settings dialog box shown in 1, here, the network administrator still needs to perform authentication on the Web server, regardless of whether the "Anonymous Access" and "Integrated Windows Authentication" options are selected or deselected, this indicates that the fault is irrelevant to the access permission settings of the target Web server.

Check server connection restrictions

Because a valid user account or even a super Administrator account cannot log on to the Web Server correctly, the network administrator starts to suspect that the Windows Server 2003 Server System may limit the number of simultaneous connections of users, if you limit the number of user connections to the site Home Directory on the Web server, users who log on later will not access the site content on the Web server in any way. To do this, the network administrator first opens the resource manager window of the server system, finds the Home Directory of the Web server site, right-click the directory icon, and runs the "properties" command in the shortcut menu, open the attribute settings window of the home directory of the target site. Click the share tab in the settings window. On the option settings page, the Network Administrator found that the Windows Server 2003 Server System limited the number of user accesses to this directory to 5, so he tried to change this parameter to 20 and saved the setting operation, the same fault still occurs when you access the Web server again.

Later, when the network administrator searched the user connection restrictions online, he found that if the authorization mode of the Windows Server 2003 Server System was not set, the number of user connections would also be limited. After searching for such a result, the network administrator was excited. It seems that the failure of the Web server could be solved immediately; he immediately opened the "Start" menu of the Windows Server 2003 Server System, clicked the "set"/"Control Panel" command in turn, and double-click the "authorize" option, on the following page, the network administrator finds that the server system selects the "per server" option by default, and displays the number of user connections as "5 ", obviously, the parameters here are not set correctly. The Network Administrator immediately selects the "per device or user" option (2), and then selects the "I agree" option in the "per device" or "per customer authorization" dialog box, finally, I restarted the server system. I thought this kind of effort would be rewarding, but when I re-accessed the LAN Web server from a common computer, the annoying Authentication Dialog Box still appears on the System screen.

Unexpected Fault Cause found

Just as the network administrator had no clue, a LAN User suddenly ran to seek help from the network administrator, saying that their Department had recently bought a new network printer for work needs, after connecting the network printer to the core switch of the Organization and setting relevant network print parameters, all users in their department can use the network printer to print materials normally. However, today, his computer cannot use a network printer, but others can print the printer. Hearing this user's support, the network administrator immediately came to the network printer site, logged on to the printer background management interface, accidentally opened the Network Printer log page, I found that the IP address of the Network Printer conflicts with the IP address of a computer in the LAN. When I carefully checked the IP address that conflicted, it turned out to be the IP address used by the Web server. No wonder the Web server cannot be accessed normally, the IP address of the original network printer unexpectedly conflicted with the IP address used by the printer.

Originally, in order to facilitate management and maintenance, a Web Service is also running on the network printer. You can easily set various Internet parameters for the network printer through the Web-based background management interface, however, the Weh server of the network printer does not support anonymous access by default. When the IP address you set for the Network Printer conflicts with the address of the Web server, the LAN user enters the IP address of the Web server in the address bar of the IE browser window, in fact, it accesses the background login interface of the network printer, which is why the authentication dialog box appears on the System screen when accessing the Web server. In this case, when the Ping command is used to test the connectivity of the Web server, the network printer is tested. In this way, the network printer can be pinged, but you need to enter a valid user account to access it.

After finding out the cause of the fault, the network administrator immediately changed the IP address of the network printer to ensure that the IP address of the Web server does not conflict with the IP address of other computers, as a result, the page content can be quickly opened, so that the Web server can be pinged but cannot be accessed, and the fault is successfully solved.

Conclusion

It is not very complicated to solve such network faults, and the ultimate fault cause can be found easily. However, this fault reminds every network administrator from another point of view that to solve network faults, we should first be familiar with the latest changes in the network environment before resolving the fault, familiar with the features of various network devices in the work environment. Only when we know the latest changes in the network and the features of network devices, will we encounter network faults, subconsciously think about and associate with each other. Only in this way can we quickly find the specific cause of failure and take timely measures to quickly solve network faults.

 

You are reading: The instance solves the problem that the Web server cannot be accessed.

1. What are the advantages and disadvantages of virtualization technology?
2. How can we predict how HP will compete with Cisco in the server field?
3. How to control the server virtual test environment