Problems with Windows Server 2008 shared Resources Setup Steps

Many people think that access to shared resources is simple, just find the shared resources, then double-click on the shared target, and then log in to access the operation. In fact, each of these steps can be limited by Windows systems, and this does not, when we try to access the shared resources in the Windows Server 2008 system, the system has set a barrier to each of them, we must set the right remedy to overcome the obstacles, Give shared access a green light.

1. Clear the Invisible barrier

Supposedly, from the normal computer in the LAN, open the Network Neighborhood window to see the target shared resources, but the Windows Server 2008 system of shared resources is not so easy to see, this is why? Originally, Windows Server The 2008 system enhances security by default, and it controls the normal client at random to view the target shared resources that are stored in it through the newly added Network Discovery feature. Therefore, when we are unable to view the target shared resources in the Windows Server 2008 system from the Network Places window, it is necessary to check that the corresponding system is functioning properly, and the following are the specific viewing steps:

Open the Windows Server 2008 System Start menu, select the Settings/Control Panel command, and then double-click the Network and Sharing Center icon in the Control Panel window to open the network and Sharing Center Management window for the corresponding system;

Next, from the share and discover list in the Administration window, locate the Network Discovery option, expand the Option Settings area (1), check whether the Enable Network Discovery option is selected by default, and if it is not selected, it means that the Windows Server 2008 the system prohibits any user on the LAN from viewing and accessing all of the shared resources on the network, so that we naturally cannot see the target shared resources;

At this point, we can check the "Enable Network Discovery" option, and then click the "Apply" button to save the above settings. Of course, here we must make sure that the file sharing option is also selected, otherwise the Windows Server 2008 system cannot publish the target resource share to the LAN network.

Of course, there's a point. Note that the normal computer on the LAN must be in the same working subnet as the Windows Server 2008 system host, and they will use the same workgroup name, if this condition is not guaranteed, Then we may not see the target shared resources on the host's "figure", let's not talk about access to it.

2, clear open the barrier

When I see a target shared resource in a Windows Server 2008 system in My Network Places window, it means that the target shared resource is already waving to us, but it's not always possible to get a grip on it, because when we try to double-click the target shared resource icon with the mouse, Often encounter a similar ban on access, unable to find the network path and other phenomena of open barriers. Different phenomena caused by different reasons, we need to follow the specific phenomenon in turn, in order to clear the target of shared resources can not open the barrier.

In general, when we double-click the target shared resource icon with the mouse, the Windows Server 2008 system authenticates the shared access operation before it is verified to have access, and finally decides whether to display the target shared resource content. In accordance with this shared access process, it is not difficult to find that when the system is forbidden to access the phenomenon, it is 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, 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 click "Computer Configuration" in the display pane on the left side of the window. Node option and expand the Windows Settings/security Settings/Local Policies/User Rights Assignment Group Policy branch from below the node;

Next double-clicking the "Access this computer from the network" option below the target branch, when the Settings dialog box shown in 2 appears on the system screen, we examine the local Security Settings page to see if there is a shared access account that you use, for example, when we do share access by default with the "Guest" account. If the "Guest" account does not appear in the Setup dialog shown in Figure 2, the system will be prompted to disable access, at which point we simply click the "Add" button to add the shared access account you use.

If you use a shared access account that does not have a password set, we may also encounter a bug that prevents access, because the Windows Server 2008 system allows only blank password accounts to access console operations in the default state and does not allow them to do anything else; We also need to look at the relevant Group Policy parameters for the Windows Server 2008 system to see if it restricts access to the blank password account:

Open the Windows Server 2008 System's Run dialog box, enter the "gpedit.msc" string command, click Enter, enter the corresponding system's Group Policy console window, select the "Computer Configuration" node option in the display pane on the left side of the window. and expand the Windows Settings/security Settings/Local Policies/Security Options Group Policy Branch from below the node;

Second, in the display area to the right of the "Security Options" Group Policy Branch, double-click the "account: local account with blank password only allows console logon" target Group Policy, open the Settings dialog box shown in 3, and if you see the "Enabled" option selected, it means that Windows The Server 2008 system prohibits a blank user account from sharing access, and we must select the disabled option, and then click OK to save the above settings.

After the above settings, if the system screen can not find the network path, such as the failure prompt, then we may try to refresh the client system in the Web Places window to prevent the target shared resource location in the Windows Server 2008 system has really changed, if after the refresh operation, If the fault prompt still does not disappear, it is likely that the hidden share ipc$ in the Windows Server 2008 system has been shut down unexpectedly because the shared content can be displayed with ipc$ support, and if it is not supported, The system will then prompt that the network path to the target shared resource cannot be found. When checking if hidden shared ipc$ is enabled in Windows Server 2008 systems, we can follow these steps:

First click the Start button in the Windows Server 2008 system desktop, select the Programs/Accessories/Command Prompt option from the pop-up Start menu, right-click the command prompt option, and then execute the Run as Administrator command. Switch the system screen to the DOS command-line work window;

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

3. Clear the barriers to boarding

Sometimes, when we double-click the target shared resource icon in a Windows Server 2008 system, an authentication dialog box appears on the system screen, which is supposed to open the folder window for the target shared resource and share access, as long as the shared access account is properly entered. However, when actually accessing the shared resources in a Windows Server 2008 system, we sometimes encounter a strange symptom, that is, regardless of the type of shared access account, the Windows Server 2008 system always prompts that the login is not successful; In the face of such a shared access barrier, how can we sweep it away?

As you know, when you perform a shared access operation, the Windows client system automatically takes precedence over the "Guest" account to log in, and if the login is unsuccessful, the system automatically appears with the authentication dialog box asking us to use a different user account to share the login. Now, the authentication dialog box appears on the system screen, which means that the "Guest" account does not authenticate to the Windows Server 2008 system, so we can log into the Windows Server 2008 system as soon as we enter the appropriate other user account; , there is no matter what type of account entered into the strange phenomenon, which is why? In fact, the Windows Server 2008 system supports two shared access modes, one is simple access mode, the other is Advanced access mode, if simple access mode is enabled, The Windows Server 2008 system does not authenticate any shared users, and conversely, if advanced access mode is selected, the Windows Server 2008 system will forcibly share authentication with any user, and the "Guest" account is naturally no exception. Obviously, the Windows Server 2008 system uses advanced access mode, in which case it forces the "guest" account to enter a shared access password, in fact the "guest" account does not have a password set by default. So there's a strange failure to enter whatever the shared access password does not log in successfully. Figuring out the cause of the failure, we just have to change the shared access mode of the Windows Server 2008 system:

Open the Windows Server 2008 System's Run dialog box, enter the "gpedit.msc" string command, click Enter, enter the corresponding system's Group Policy console window, select the "Computer Configuration" node option in the display pane on the left side of the window. and expand the Windows Settings/security Settings/Local Policies/Security Options Group Policy Branch from below the node;

Next, locate the "Network access: Sharing and security mode for local accounts" option under the target branch, and right-click the option, execute the Properties command on the shortcut menu, open the Target Group Policy Properties window shown in 4, select the guest-only-local users as guest authentication item in the window, and then click OK "button to save the set operation, so that can solve the above fault phenomenon.

Of course, for security reasons, we'd better turn off the "Guest" account for the Windows Server 2008 system, and let the system still use advanced access mode while creating a user account with normal access to the shared resources in the Windows Server 2008 system. In the future, we just use the newly created user account to share the login, so as to prevent illegal users from arbitrarily accessing the target shared resources

This article is from the "system and Security Technology" blog, please be sure to keep this source http://foreverzpk.blog.51cto.com/683356/1626033

Problems with Windows Server 2008 shared Resources Setup Steps