Win2008 shared resources can not open the fault

After seeing the target shared resources in the Windows Server 2008 system in the Network Neighborhood window, it means that the target shared resources are already beckoning to us, but can't hold it with it, this is not necessarily the case. This is because when we try to double-click the target shared resource icon with the mouse, we often encounter obstacles such as prohibiting access and not finding the network path. The causes of different phenomena are also different. We need to follow up the specific phenomena in order to clear the obstacles that the target shared resources cannot open.

Generally speaking, when we double-click the target shared resource icon with the mouse, Windows Server 2008 will first authenticate the shared access operation. After the verification is passed, it will judge whether it has the right to access. To display the content of the target shared resource. According to this shared access process, it is not difficult to conclude that when the system has a phenomenon that prohibits access, it is likely that the Windows Server 2008 system does not allow users to access shared resources through the network, or the access user does not have access rights. The following steps are taken:

First, click the “Start” and “Run” command in the Windows Server 2008 system desktop. In the pop-up system operation box, execute the string command “ldquo; Gpedit.msc”, open the group policy console window of the corresponding system, click the “Computer Configuration” node option in the left pane of the window, and expand from the node below, “Windows Settings”//“ ; security settings & rdquo; /& ldquo; local policy & rdquo; /& ldquo; user rights allocation & rdquo; group policy branch. Next, double-click the “Access this computer from the network” option under the target branch. When the setup dialog box shown in Figure 2 appears on the system screen, we carefully check the “Local Security Settings” setting page to see if it exists. The shared access account used by the user; for example, when we share the access operation by default with the “Guest” account, if the “Guest” account does not appear in the settings dialog, the system will prompt to prohibit access. When we click the “Add” button, we can add the shared access account we use.

If the shared access account used by us does not have a password, we may also encounter a failure warning. This is because the Windows Server 2008 system only allows blank password accounts to access the console operation by default. Instead of allowing them to do anything else; for this, we also need to check the relevant Group Policy parameters of the Windows Server 2008 system to see if it restricts access to the blank password account:

First open Windows Server 2008 system running dialog box, enter the "gpedit.msc" role in the string command, click the Enter key, enter the corresponding system's Group Policy console window, click in the display pane on the left side of the window "Computer Configuration" node option, and from the bottom of the node, expand <;Windows Settings" &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&;

Secondly, in the right area of ​​the corresponding "Security Options" group policy branch, double-click "Account:": A local account with a blank password is only allowed to log in to the console. Target Group Policy, open the settings dialog. If you see the "Enabled" option is selected, it means that the Windows Server 2008 system prohibits blank users. The account is shared access operation. At this time, we must select the “disabled” option, and then click the <;OK" button to save the above settings.

After the above setting operation, if there is a fault message such as the network path not found on the system screen, then we can try to refresh the network neighbor window in the client system to prevent the Windows Server 2008 system. The target shared resource location has really changed. If the fault prompt still does not disappear after the refresh operation, it is likely that the hidden shared ipC$ in Windows Server 2008 system is closed unexpectedly because the shared content can It shows that IPC$ support is required. If it is not supported, the system will prompt that the network path of the target shared resource cannot be found. When checking if the hidden shared IPC$ in the Windows Server 2008 system is enabled, we can follow the steps below:

First click on the “Start” button in the Windows Server 2008 system desktop. In the pop-up "Start" menu, click the "Programs" >; "Accessories""/“command prompt” option, then right-click the "command prompt" option, and then execute “Run as administrator” to switch the system screen to the DOS command line work window;

Next, enter the string command “htm share” in the window command prompt. After the Enter key, we can see the hidden shared IPC$ enabled status from the subsequent results interface. If we find that it is not working properly, we simply execute the string command “net share IPC$” It will be fine.