Error resolution to access Windows 2008 shared resources

Source: Internet
Author: User

To make it easier to communicate with other employees on the local area network, we often use shared access to transfer files and send data to each other. To make shared access more efficient, we've also summed up a number of proven operational cheats, but almost all of these cheats are summed up in a traditional system environment, can they work in a Windows Server 2008 system environment? In fact, the Windows Server 2008 system is a unique operating environment in which traditional cheats are sure to encounter some strange shared access failures; For this reason, we now have some common shared access errors that occur in Windows Server 2008 environments. I hope these content can help you to eliminate the new error in the new environment efficiently!

1. Shared access is intermittent

Sometimes, when we go from the same computer on the local area network to access one of the same shared resources in the Windows Server 2008 system, we encounter this strange symptom, a moment when the shared resources can be accessed smoothly, and then a shared access error occurs. So why is this happening? The cause of this phenomenon is more, for example, the reliability of network connection, network virus burst, the stability of the system itself, after excluding these possible factors, if the shared access can not solve the problem, we need to carefully check the client system's Internet settings, such as the default gateway settings, communication protocol settings.

Because, if the client system set up two gateway addresses at the same time, and the "metric" values of the two gateway addresses are identical, then the client system will often randomly choose a gateway address whenever the shared access is used, once the gateway address is selected with the Windows Server 2008 If the gateway address used by the system does not belong to the same working subnet, shared access can be faulted, and shared access will be normal if the selected gateway address is exactly the same working subnet as the gateway address used by the Windows Server 2008 system. , for intermittent failures of shared access caused by improper use of Gateway addresses, we can modify the gateway address "metric" value of a working subnet in the client system with a Windows Server 2008 system so that the value is greater than "1". This means that the client system will automatically prioritize the "metric" gateway address each time it is shared, that is, automatically selecting the gateway address of a working subnet with the Windows Server 2008 system. When modifying the "metric" value of the gateway address, we can follow the steps below:

First on the client system open the Start menu, from which to click the Run command, in the pop-up System Run dialog box, enter the string command "regedit", click the "OK" button, enter the client system Registry editing window;

Next, select the HKEY_LOCAL_MACHINE node option for the edit window with the mouse, and select the System\currentcontrolset\services\tcpip\parameters registry subkey from under this option. And then from the target registry subkey to find the target network card devices, in the corresponding target network card device, double-click the Defaulgatewaymetric key value, open as shown in Figure 1 of the Settings dialog box, where the "metric" value modified to more than "1" on it.

Figure 1

After confirming that the gateway parameter is set correctly, we also need to check the communication protocol settings of the target network card device, because the client system's network neighbor function uses the NetBIOS communication protocol at work, and if the protocol is not carefully cancelled, Then naturally we cannot find shared resources in the Windows Server 2008 system through the Network Neighborhood window, and we can follow these steps to check if the NetBIOS communication protocol is installed:

First click the start/settings/Network Connections command. In the pop-up Network Connections List window, locate the destination local connection icon, right-click the connection icon, and execute the Properties command from the pop-up shortcut menu to open the Properties Settings window for the destination local connection;

Next, select the TCP/IP protocol option from the Property Settings window. Click the Properties button, go to the TCP/IP Protocol Properties Settings window, click the Advanced button in the Settings window, and then, in the Advanced Settings page that appears, locate the NetBIOS Settings option, and check the Enable NetBIOS on TCP/IP project is selected (as shown in Figure 2), once it is found that it has not been selected, we should select it in time, and then click OK to save the above setup operation, so that the client system's Network Neighborhood function will work properly, The Network Neighborhood window allows us to successfully access shared resources in the Windows Server 2008 system.

Figure 2

In addition, it should be noted that the list of host updates for the Network Neighborhood window is often done at regular intervals, and that during this time, if the Windows Server 2008 system where the target shared resource is located has a shutdown or other abnormal behavior, Its corresponding host shortcut icon is still saved in the client system's Network Neighborhood window, and when we double-click the corresponding host shortcut icon, it is easy to see the failure of the shared access error, because the Windows Server 2008 system is actually turned off or is not functioning properly at this time. We certainly do not have access to the shared resources in it properly.

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.