Network errors under Windows Server 2008

Window Server 2008, as a server platform, typically deploys many services that are often network-related. The complexity of the service creates network complexity, so network scheduling under Windows Server 2008 is more cumbersome. In fact, as long as the use of its tools and the relevant command network error can be very simple. The following author and you share

Network debugging under Windows Server 2008 several tips and related experience.

1. Troubleshoot local connectivity problems with the Windows Network Diagnostics Tool

such as the disappearance of the connection, the connection is limited, exclamation, etc. and "local connection" related to the fault, we have encountered it! For such a failure, usually through the detection of network cards, network cable to arrange the wrong, often this is enough to solve most of the fault. However, there are a number of exceptions, when you reconnect the network cable and replace the network card, "local connection" although the presence of other failures as well. What do you do when you're in a situation like this? Let's try the Network "diagnostics" feature under Windows Server 2008, which generally solves the problem.

Click start → network to open the Network Manager window and click the Network and Sharing Center button on its toolbar to open the Network and Shared Center window, and then click the Manage Network Connections link. Finally, right click the local connection with the problem to select Diagnostics, and then the Windows Network Diagnostics Tool detects the local network. When a recognizable configuration problem is detected, the tool displays a list that contains all possible solutions. Where the solution prompts for the automatic fix option, we can click the solution to perform the repair operation. In addition, some solutions may require us to do manual repairs, such as requiring reconfiguration of the network, and so on, we can follow the instructions. The Windows Network Diagnostics tool can diagnose and resolve most of the local connection-related failures, and I hope you can use them flexibly. (Figure 1)

Figure 1 Windows Network Diagnostics

2, using the Diagnostics and Repair tool Internet connectivity issues

For server systems such as Windows Server 2008, many services are typically run, and most services are related to the Internet. There is a dependency between these services, protocols, and configurations, so troubleshooting network failures can be cumbersome. Windows Server 2008 contains a powerful Network diagnostics tool, "diagnostics and Repair," which can often be used to diagnose and repair failures more quickly. And the tool is widely used, in addition to being able to diagnose and fix general network connectivity problems, and to diagnose and fix e-mail, newsgroups, proxy services, DNS, DHCP, WINS, and default gateways and IP addresses.

To troubleshoot these Internet connection-related failures, we can do this by first entering the network and Sharing Center window according to the operation in 1, and then clicking the Diagnostics and Repair link in the Tasks list, and then the Windows Network Diagnostics tool scans the network state. Then make a judgment listing the probable cause of the failure. Similarly, when a recognizable configuration problem is detected, the tool displays a list that contains all possible solutions. Some of these solutions provide automatic repair options, and clicking the scheme automatically completes the repair. Of course, some of these programs require us to manually operate, you can follow the prompts to complete the operation. Typically, using the diagnostics and Repair tool fixes most network failures, and we need further troubleshooting for failures that cannot be repaired. (Figure 2)

Figure 2 Windows Network Diagnostics

4, comprehensive application of the diagnosis and resolution of IP address problems

If the server is having problems accessing other network resources or communicating with other computers, it is most likely caused by an IP address setup issue. This kind of problem is more complex, with Windows Server 2008 system As an example, we can arrange the error from the IP address setting that the computer is currently using and other important IP addresses. The following is the author of 3 kinds of situations and we talk about their own mistakes experience.

(1). IP address is private address

Sometimes we find that the IPV4 address used by the server is an IP in the range of 169.254.0.1-169.254.255.254, which means that the computer is using an automatic private IP address. This is typically because the server is set up to obtain an IP address through DHCP, but it can be caused by a failure to connect to the DHCP server. For Windows Server 2008来, when using private IP, it automatically checks periodically for the availability of the DHCP server, which can cause problems if the dynamic IP address is not eventually successfully obtained. It is now necessary to detect connectivity between the host and the DHCP server, such as network cables, switches, hubs, and so on. (Figure 4)

Figure 3 Using Ping Diagnostics Network