Smooth access to "neighbors" in a Windows Server 2008 network

Through the Network Neighborhood window to find shared resources, is a lot of LAN users often do a "homework", in order to do this "homework", many friends accumulated and summed up a lot of Network Neighborhood troubleshooting experience; However, these experiences are in a Windows Server 2008 network environment, Most of them are not very useful, after all, the Windows Server 2008 system is a completely new work environment, and you need to summarize the new Network Neighborhood troubleshooting experience to find the "neighbor" you want to interact with seamlessly from your Windows Server 2008 network. To this end, this article is now on the Windows Server 2008 system of the Network Neighborhood common failures and solutions to introduce, I hope that these things can help you.

From a Windows Server 2008 network, there are a number of things that often occur when you look for "Neighbors":

1, the Windows Server 2008 system desktop does not have a "network" icon, users can not go to the Network Neighborhood window to find shared resources;

2, double-click the "Network" icon in the system desktop, although the ability to enter the online neighborhood window, but not through the window to find the "neighbor" host in the shared resources;

3. Unable to view workgroup information on LAN in Windows Server 2008 System's Network Neighborhood window;

4, through the Windows Server 2008 network, although you can see the "neighbor" host in the shared resources, but with the mouse double-click the folder icon of the shared resource, but can not see the specific shared content;

5. When you double-click the Network icon in the Windows Server 2008 system desktop with your mouse, the system is unresponsive and even an unresponsive symptom occurs.

Although the above symptoms appear to be "familiar", the cause of the failure and the specific troubleshooting steps are not necessarily the same as before, after all, the Windows Server 2008 system is very different from the traditional operating system; Now, this article is for some of the common symptom, Propose a solution to the problem so that you can help your friends to find the "neighbors" that they want to interact with smoothly.

1. Troubleshoot "network" icon not found

In general, as long as we install the driver for the NIC device correctly into a Windows Server 2008 system environment, you should see the network icon in the corresponding system desktop, so when we find that the network is not available from the Windows Server 2008 system desktop icon, you can click "Start"/"Settings"/"Network Connection" command, then see if you can find the "Local Area Connection" icon in the Network Connections List window, and if you see the "Local Area Connection" icon, then the driver installation of the NIC is correct. At this point, we can make the network icon appear again on the Windows Server 2008 system desktop by setting up the Windows Server 2008 system as follows:

First in the Windows Server 2008 system Desktop, right-click a blank location, from the popup shortcut menu to perform the personalization command, open the System's Personalization dialog box, click the "Change Desktop Icon" option in the left Task List area of the dialog box, open the Settings window shown in 1. Check that the network option is selected in the Settings window, and if it is not checked, we should re-select it and then click OK to save the settings.

650) this.width=650; "Width=" 404 "height=" 417 "alt=" Windows Server "src=" http://files.jb51.net/file_images/ Win2008/2009721495628177801.jpg "/>

Figure 1 Desktop icons

Of course, if we do not see the "Local Connection" icon in the Network Connection List window of the local system, it is mostly the driver of the NIC device is not correct, at this time we only have to reinstall the driver of the network card device to ensure that the "network" icon appears in Windows Server 2008 the System desktop.

2. Resolve a "neighbor" host failure is not found

Opening the Windows Server 2008 system's Network and Sharing Center window, we sometimes cannot find the "neighbor" host in the LAN, when we encounter this symptom, we first check whether the Network Discovery feature of the Windows Server 2008 system is enabled. If this feature is not enabled, then any "neighbor" host Windows Server 2008 system on the LAN will not be found, and the other "neighbor" hosts will not see the Windows Server 2008 system host. When checking whether the Network Discovery feature is enabled, we can follow these steps:

First double-click the "Network" icon in the Windows Server 2008 system desktop with your mouse, and in the following screen you open the Network and Sharing Center Management window of the corresponding system by clicking the "Network and Sharing Center" function button in the toolbar;

Second, find the "Network Discovery" setting item from the Admin window, click the down arrow button to the right of the setting item, expand the Network Discovery feature Settings area, 2, check whether the "Enable Network Discovery" option is selected, and if it is not selected, we should select it again, then click "Apply" button so that network discovery does not prevent us from looking for "neighbor" hosts on the LAN.

If the settings above still do not help us find the "neighbor" host, it is necessary to see if the Windows Server 2008 system has the "Enable File and Printer Sharing" feature component, and once the feature component is not installed, we from the Windows Server 2008 the network also does not see the "neighbor" host figure. When you check whether the Enable File and Printer Sharing feature component is installed, we can do this by doing the following:

650) this.width=650; "Width=" 383 "height=" 189 "alt=" Windows Server 2008 Enable Network Discovery "src=" http://files.jb51.net/file_images /win2008/2009721495632877802.jpg "/>

Figure 2 Enabling Network Discovery

Click the start/settings/Network Connections command in the Windows Server 2008 System Desktop First, in the list of network Connections pop-up window, locate the destination Local Area Connection icon, right-click the Local Area Connection icon, and select the Properties command from the popup shortcut menu. Enter the property Settings dialog box for the destination local area connection, and in the list of network features in the dialog box, check whether the Enable File and Printer Sharing feature option is selected, and once it is found that the option is not selected, we should re-select it, and then click the OK button so that The Enable file and Printer Sharing feature component will be installed successfully.

In addition, we need to check that the Tcp/ipv4 property parameter is set correctly here, in particular, to verify that the IP address of the Windows Server 2008 System host is in the same working subnet as the IP address of the LAN "neighbor" host, so that we can guarantee the Windows The Server 2008 system network looks for a "neighbor" host.

3. Resolve inability to view workgroup failures

If we are unable to view workgroup information on the LAN in the Windows Server 2008 system's Network and Sharing Center window, we can simply follow the steps below:

First open the Windows Server 2008 System Desktop in the Start menu, click the "Run" command, in the System Run text box, enter the string command "Services.msc", click the "OK" button, enter the corresponding system of the Service List window;

Next, locate the target system service "computer Browser" from the Service List window, right-click the service option, execute the "Properties" command from the popup shortcut menu, and open the Target Service Property settings window shown in 3; normally, "Computer Browser" The service should be "started", the startup type should be "automatic", and if we find that the "computer Browser" service is not working properly, it must be modified in time.

650) this.width=650; "width=" 420 "height=" 468 "alt=" Windows Server "src=" http://files.jb51.net/file_images/ Win2008/2009721495637577803.jpg "/>

Figure 3 Starting the Computer Browser service

When you modify the working state of the Computer Browser service, the system is likely to fail with a failure to start the service, which is mostly the "Workstation" service and the "Server" Service for Windows Server 2008 systems that are also unexpectedly stopped. Because these two system services provide us with the most basic network access support, once these two services are not working properly, we must not be able to display the name of the LAN "neighbor" host in the local system's Network and Sharing Center window. As a result, it is possible to quickly resolve a failure to view a workgroup if the "Workstation" service and the "server" service for Windows Server 2008 systems are in good working time.

It should be noted that if our computer is not in the LAN working environment, it can be "Workstation", "Server", "Computer Browser" and other services all run off, so as to effectively save the system valuable resources, Increase the speed of system operation.

4. Resolving shared resources is not expected

Many times, we can see the target "neighbor" host from the Windows Server 2008 System network, but with the mouse double-click the "neighbor" host icon, try to enter the shared resources window, found that the target folder window is not open at all. The cause of this failure is very complicated, the possible failure factors are as follows: The Windows Server 2008 system host is not in the same workgroup as the target neighbor host, does not have the appropriate share access rights, is restricted by the system firewall, etc. At this point we must follow the steps below in order to resolve the expected failure of shared resources:

First check that the shared two hosts are in the same workgroup, and when you view the workgroup information for the Windows Server 2008 System host, click Start/Settings/Control Panel, double-click the System icon in the pop-up Control Panel window, and then on the left side of the interface. Advanced system Settings Project, open the Advanced Settings dialog box for Windows Server 2008 system, click on the "Computer name" tab, and open the label Settings page shown in 4, where we can clearly see the target host's workgroup information; If you find the workgroup name and the "neighbor" When the host's workgroup name is different, we can simply click the "Change" button here to complete the task of modifying the workgroup name.

650) this.width=650; "Width=" 410 "height=" 430 "alt=" Windows Server "src=" http://files.jb51.net/file_images/ Win2008/2009721495642177804.jpg "/>

Figure 4 Workgroup and Domain

Second, check whether the local area network is enabled domain, if domain is enabled on the LAN, and one of the hosts in the shared host is not joined to the domain, we also cannot access the shared resources, so once we find that a host is not joined to the LAN domain, we must join it in the domain in time. When you join a Windows Server 2008 system host to a domain, we simply click the "Change" button in the Figure 4 interface, select the "domain" option in the subsequent interface, set the domain name, and then click the OK button.

Then check if the system comes with a firewall or not, and when you check whether the Windows Server 2008 system firewall restricts shared access operations, click Start/Settings/Control Panel, and in the System Control Panel window that pops up, Double-click the Windows Firewall icon to open the basic configuration interface for the Windows Server 2008 System firewall by clicking the "Enable or disable Firewall" option in the left Task List area of the interface, click the "Exceptions" tab in the interface, and in the corresponding label Settings page, check the " If the file or printer share is selected, we should check it again if it is not selected, and then click the OK button to remove the firewall's restrictions on shared access operations.

The following checks whether the shared resource in the target neighbor host has access restrictions, and when we do this, we check that the shared resource has a security limit set, and if it is enabled, check that the access account we are currently using has the appropriate access, and if you do not have access rights, We should reassign appropriate access rights for this access account in a timely manner.

5, solve the network window unresponsive fault

Sometimes, when we double-click the "Network" icon in the Windows Server 2008 System Desktop, we find that the system is slow to enter the corresponding window, and there may even be an unresponsive symptom; When we encounter this behavior, we can try to troubleshoot by doing the following:

First open the Windows Server 2008 System Desktop in the Start menu, click the "Run" command, in the System Run text box, enter the string command "Services.msc", click the "OK" button, enter the corresponding system of the Service List window;

Next, locate the target system service "Task Scheduler" from the Service List window, double-click the service option with the mouse, open the Service Property Settings window shown in 5, click the Stop button in the Settings window, and set the startup type of the corresponding service to manual, and then click OK to return;

650) this.width=650; "Width=" 410 "height=" 429 "alt=" Windows Server "src=" http://files.jb51.net/file_images/ Win2008/2009721495646877805.jpg "/>

Figure 5 Task Scheduler service shutdown

Click the "Start"/"Settings"/"Network Connection" command in the pop-up Network Connections List window, locate the target Local Area Connection icon, right-click the Local Area Connection icon, select the "Properties" command from the popup shortcut menu, and go to the target local Area Connection's property Settings dialog box; Just select the Tcp/ipv4 option and file or printer Sharing options from the dialog box, uncheck all the remaining options, click OK, and then restart the Windows Server 2008 system, which I believe will solve the network window unresponsive symptom.

This article is from the "system and Security Technology" blog, please be sure to keep this source http://foreverzpk.blog.51cto.com/683356/1626030

Smooth access to "neighbors" in a Windows Server 2008 network