What should I do if Windows 2008 shared resources cannot be opened?

Under the Windows2008 system, when a user accesses a network share resource, the mouse clicks on the target shared resource. It is not forbidden to access or the network path cannot be found, and the shared resource cannot be opened. What is the reason? We can conduct detailed investigations based on specific phenomena.

First, 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. Decide whether you want 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 settings dialog box 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.

Second, 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 account access control by default. The operation does not allow 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 the Windows Server 2008 system run dialog box, enter the "gpedit.msc" role in the string command, click the Enter key, enter the corresponding system's Group Policy console window, in the left pane of the window Click the “Computer Configuration” node option, and from the bottom of the node, expand “Windows Settings” & rdquo; /& ldquo; Security Settings & rdquo; /& ldquo; Local Policies & rdquo; /& ldquo; Security Options & rdquo; Group Policy Branch; Br>

Secondly, in the corresponding display area of ​​the corresponding "Security Options" group policy branch, double click with the mouse User: Local account with blank password only allows console login & target group policy, open the settings dialog box, if you see the "Enabled" option is selected, it means that Windows Server 2008 system is forbidden A blank user account is used for shared access operations. At this time, we must select the “disabled” option, and then click the <;OK" button to save the above settings.

Third, after the above setting operation, if there is a fault message indicating that the network path cannot be 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 location of the target shared resource has really changed. If the fault prompt still does not disappear after the refresh operation, it is likely that the hidden shared ipC$ in the Windows Server 2008 system is accidentally shut down because the shared content Can you show that you need IPC$ support? If you don't get support, you will be prompted to find the network path of the target shared resource. 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.

Under the Windows2008 system, sometimes you can see the target shared resources in the network neighborhood, but you may not be able to browse the documents inside, because the windows2008 system will authenticate the shared access or prohibit access, etc. Users will only encounter situations where shared resources cannot be opened.