Resolve access to Windows 2008 shared resources error

In order to more easily communicate with other employees on the LAN, we often use the shared access method to transfer files and send data to each other. In order to make the shared access operation more effective, we also summarized a number of effective operating cheats, but these cheats are almost all summarized in the traditional system environment, can they be effective in the Windows Server 2008 system environment? In fact, the Windows Server 2008 system is a different operating environment. In this environment, traditional cheats will definitely encounter some strange shared access failures; for this reason, we now have some common sharing in the Windows Server 2008 environment. Access errors to solve problems, I hope that these contents can help you to effectively eliminate new errors in the new environment!

1, shared access intermittently

Sometimes, when we start from the same computer on the LAN, when accessing the same shared resource in Windows Server 2008 system, we will encounter Such a strange failure phenomenon, a shared resource can be accessed smoothly in a while, but a shared access error occurs in a while, then why is this happening? There are many reasons for this phenomenon, such as the reliability of network connection, the burstiness of network virus, the stability of the system itself, etc. After excluding these possible factors, if the shared access fault cannot be solved, we You need to carefully check the Internet settings of the client system, such as the default gateway settings, communication protocol settings, and so on.

Because, if the client system has two gateway addresses set at the same time, and the values ​​of the two gateway addresses are the same, then the client system will often feel free to share access each time. Select a gateway address. Once the selected gateway address does not belong to the same working subnet as the gateway address used by the Windows Server 2008 system, the shared access will be faulty. If the selected gateway address happens to be the same as Windows Server. When the gateway address used by the 2008 system belongs to the same working subnet, the shared access can be normal; for the shared access intermittent failure caused by improper selection of the gateway address, we can modify the Windows Server 2008 in the client system. The system has the same gateway address of a working subnet, “metric”, so that the value is greater than “1””, so that the client system automatically selects the “metric” value every time the shared access is performed in the future. High gateway address, which means automatic selection with Windows Server 2008 EC with a job at the gateway address of the subnet. When modifying the "metric" value of the gateway address, we can follow the steps below:

First open the "Start" menu on the client system, click on the "Run" command from the pop-up menu. In the system running dialog box, enter the string command “regedit”, click the "OK" button to enter the registry editing window of the client system;

Secondly select the editing window with the mouse HKEY_LOCAL_MACHINE node option, select the SYSTEMCurrentControlSetServicesTcpipParameters registry subkey from the option, then find the target NIC device from the target registry subkey, double-click the DefaulGatewayMetric key under the corresponding target NIC device to open the setup dialog box shown in Figure 1. Modify the "metric" value to be greater than “1” here.

Figure 1

After confirming that the gateway parameters are set correctly, we also need to check the communication protocol settings of the target NIC device, because the network neighbor function of the client system is used at work. The NetBIOS communication protocol, if you accidentally cancel the installation, then we naturally can not find the shared resources in the Windows Server 2008 system through the Network Neighborhood window; when checking whether the NetBIOS communication protocol is installed, we can follow the steps below To do this:

First click on the "Start" "Start”/“Settings"&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& Right-click the connection icon and execute the “Properties" command from the pop-up shortcut menu to open the property setting window of the target local connection;

Second from the property setting window, select "TCP/IP protocol" ”Options, click the <;Properties" button to enter the TCP/IP Protocol Properties Settings window, click on “Advanced &rdqu in the Settings window o; button, in the advanced settings page that appears, find the "NetBIOS Settings" option, check the "Enable NetBIOS on TCP/IP" option under the option (as shown in Figure 2) Once it is found that it has not been selected, we should re-select it in time, and then click the "OK" button to save the above settings, so that the network neighbor function of the client system can work normally, through The online neighbor window will also be able to successfully access shared resources in the Windows Server 2008 system.

Figure 2

In addition, you need to be reminded that the list of host updates in the Network Neighborhood window is often done at regular intervals, and in this period of time, if the target shared resources are located When the Windows Server 2008 system shuts down or other abnormal phenomena, its corresponding host shortcut icon will still be saved in the network neighbor window of the client system. At this time, when we double-click the corresponding host shortcut icon, it is easy to share. Accessing the wrong symptom, because the Windows Server 2008 system is actually shut down or not working properly, we certainly can't access the shared resources correctly.

2, can not find the shared path

As mentioned in the previous article, once the operating state of the NetBIOS communication protocol is turned off, we are unable to access Windows through the Network Neighborhood function in the client system. In the Server 2008 system, the target shares resources. However, at this time, we can enter a shared path like “IP address” in the address bar of the client system to successfully access the target shared resource. However, in the process of actually accessing shared resources, we often find that after inputting the “IP address” path, the system always pops up the failure phenomenon that the shared path cannot be found. Why is this, what should we do to solve this problem? A strange shared access failure?

There are three main reasons for this phenomenon. One is that the network discovery function of Windows Server 2008 system is accidentally closed, resulting in the "IP address" path not found; the second is the host system where the shared resources are located. Unexpectedly shut down the operating status of the system service <;Computer Browser", causing the client system to fail to obtain the host list correctly; third, the hidden share in Windows Server 2008 system was temporarily disabled, resulting in the system being unable to Displays shared resources of the target host system. Follow the steps below to check the possible causes one by one, and we can successfully solve the failure phenomenon that the shared path cannot be found:

First check if the network discovery function is closed unexpectedly; when doing this check, we To enter the Windows Server 2008 system with super privileges, click the “Start” and “Settings” button in the system tray of the system. In the pop-up system control panel window, double-click “Network”. And the sharing center” icon, enter the network and sharing center window of the Windows Server 2008 system; secondly, expand the “Network Discovery” setting area in this window, at this time we will see the setting page shown in Figure 3, see See if the "Enable Network Discovery" option is selected. If you see that it is not already selected, we just need to re-select it and click the "Apply" button to make the network discovery of Windows Server 2008 system. The function is working properly.