What if Windows 2008 shared resources cannot be opened?

First, generally speaking, when we double-click the target shared resource icon with the mouse, the Windows Server 2008 system authenticates the shared access operation first, and the validation passes before it determines whether or not to have access, before deciding whether to display the target shared resource content. In accordance with this shared access process, it is not difficult to conclude that when a system appears to be blocked from access, it is most likely that the Windows Server 2008 system does not allow users to access shared resources over the network, or access users do not have access rights, at this time we can follow the following steps to troubleshoot:

First click the start/Run command in the Windows Server 2008 System desktop, and in the system Run box that pops up, execute the string command "Gpedit.msc", open the Group Policy Console window for the corresponding system, and select "Computer Configuration" in the left pane of the window. Node options and expand the Windows Settings/Security Settings/Local Policy/User Rights Assignment Group Policy Branch from the node below.

Second, under the target branch, double-click the "Access this computer from the network" option, when the Setup dialog appears on the System screen, let's examine the local Security Settings page for a shared access account that you use; For example, when we default to the "Guest" account for a shared access operation, if " Guest "account does not appear in the Setup dialog box, the system will be blocked access prompts, at this time we just click the" Add "button, we use the shared access account to add it.

If the shared access account you use does not have a password set, we are also likely to encounter blocked access failure prompts because the Windows Server 2008 system allows only blank password accounts to access the console operation by default and does not allow them to do anything else; We also need to look at the related 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's Run dialog box, enter the "gpedit.msc" string command, click the ENTER key, go to the Group Policy Console window of the corresponding system, and select the Computer Configuration node option in the left pane of the window. and expand the Windows Settings/Security Settings/Local Policy/Security Options Group Policy Branch from the node below.

Second, in the right-hand display area of the Security Options Group Policy Branch, double-click "Account: local account with blank password only allow console login" target Group Policy, open the Settings dialog box, if you see the "Enabled" option is selected, that means Windows Server 2008 the system prohibits the blank user account for sharing access operation, at this time we must select the "Disabled" option, and then click the "OK" button to save the above setup operation.

Three, after the above setup operation, if the system screen can not find the network path, and other fault prompts, then we may try to refresh the client system in the Online neighborhood window to prevent the Windows Server 2008 system target shared resource location has really changed, If the fault tip does not disappear after a refresh operation, it is most likely that the hidden share ipc$ in the Windows Server 2008 system was accidentally shut down because the shared content could be displayed with ipc$ support, and if it is not supported, Then the system prompts that the network path for the target shared resource cannot be found. When checking to see if the hidden shared ipc$ in the Windows Server 2008 system is enabled, we can follow these steps:

First click the Start button in the Windows Server 2008 System desktop, from the Start menu that pops up, click programs/attachments/Command prompt options, right-click the command prompt option, and then perform the run as Administrator command,. Switch the system screen to the DOS command Line Working window;

Second, at the command prompt at the window, enter the string command "net share", and after clicking the ENTER key, we can see the enabled state of the hidden shared ipc$ from the resulting interface, and if we find it not working properly, we simply execute the string command "net share ipc$ "It's okay.