Solution to access Windows 2008 shared resources error method

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? Windows Server 2008 system is a unique operating environment, in which the traditional cheats will definitely encounter some strange shared access failures; for this reason, we now have some common shared accesses in the Windows Server 2008 environment. Misunderstanding, I hope this content can help you to effectively eliminate new errors in the new environment!

1, shared access intermittent

Sometimes, we are from the same LAN When the computer starts and accesses the same shared resource in the Windows Server 2008 system, it will encounter such a strange failure phenomenon. After sharing the resources for a while, and then the shared access error occurs, why is this happening? What are the reasons for this phenomenon, such as the reliability of network connections, the network The suddenness of the virus, the stability of the system itself, etc., after eliminating these possible factors, if the shared access fault cannot be solved, we need to carefully check the client system's Internet settings, such as default gateway settings, communication. Protocol settings, etc.

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 be 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 The 2008 system is located at the same gateway address as a working 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 SYSTEM\\CurrentControlSet\\Services\\Tcpip\\Parameters registry subkey from the option, and 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, here the "metric" value is modified to be greater than “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 working with the NetBIOS communication protocol, if not If you carefully cancel the installation, then we naturally can't 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:

First click the “Start”/“Settings>;&"Network Connections" command, in the pop-up network connection list window, find the target local connection icon, right click on the connection icon, from In the shortcut menu that pops up, execute the “Properties” command to open the property setting window of the target local connection;

Secondly, select the “TCP/IP protocol” option from the property setting window, and then click ““ ;Properties” button, enter the TCP/IP protocol property setting window, click "High" in the settings window ” button, in the advanced settings page that appears, find the "NetBIOS settings" option, check the "Enable TCP/IP NetBIOS" option under the option, if it is found, it has not been When 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, we also Successful access to shared resources in the Windows Server 2008 system.

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 during this period of time, if the Windows Server 2008 system where the target shared resources are located is shut down or In the case of other abnormal phenomena, the 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 have a shared access error phenomenon, because this When the Windows Server 2008 system has actually shut down or running the icon, execute the “Properties” command from the pop-up shortcut menu to open the property setting window of the target local connection;