Windows sharing problem solves the

network to provide us with a wealth of shared resources, but when accessing these resources, there will often be "access denied" or "insufficient permissions" error message, especially in the Windows workgroup environment It is difficult to effectively manage the user account and access rights of the client. In addition, different versions of the Windows operating system coexist in the network, and the network firewall is improperly configured, which is also the main reason for the above problems. The following is a question for you to solve the problem of mutual access to shared resources.

First, the crux maintenance forum

1. Improper access settings are not supported by the motherboard.

Windows NT/2000/XP/2003 supports NTFS file system. NTFS can effectively enhance the security of the system, but set the user access rights in the ACL (Access Control List). If it is not the case, the user will not be able to access the shared resources of the device normally, and the message “Insufficient permissions” will appear. Hard disk repair training

2. Incorrect account and policy settings

In a Windows workgroup environment, users generally use a Guest account to access shared resources. However, for the security of the system, the Guest account of the system is disabled. In addition, in Windows 2000/XP/2003, the group policy defaults to not allowing the Guest account to access this computer from the network, which causes other users to access the Internet. The shared resource of the machine, the message "Access denied" appears.

3. Improper setting of network firewall

In order to enhance the security of this machine and prevent illegal intrusion, the network firewall is installed. However, improper setting of the network firewall also causes other users to access the shared resources of the machine, and the message "Access Denied" appears. This is because the firewall closes the NetBIOS port required for sharing resources.

Second, the solution

After understanding the main reasons why shared resources cannot be successfully exchanged, we can solve the problem in the interview.

1. Enabling the Guest Account

In many cases, for the security of the local system, the Guest account is disabled, so that the shared resources of the machine cannot be accessed, so the Guest account must be enabled.

The author introduces Windows XP system as an example. On the shared resource provider, go to Control Panel→Administrative Tools, run the Computer Management tool, and then expand Computer Management (Local)→System Tools→Local Users and Groups→Users to find the Guest account. If a red cross is displayed in the Guest account, it indicates that the account has been deactivated. Right click on the account. In the Guest Properties dialog box, remove the checkmark of “Account Disabled” and click “OK”. The Guest account is enabled. This method is suitable for Windows 2000/XP/2003 systems.

Tip: There is a big security risk when using the Guest account to access shared resources. Of course, we can also create a specific account for each access user. First create a new account on the shared resource provider and then specify the access rights for that account. Next, create an account with the same username and password in the client that wants to access the shared resource. After logging in to the client with this account, you can normally access the shared resources allowed by the account. This method is more secure, but you need to create an account for each user on the network, which is not suitable for larger networks.

2. Modify User Access Policy

Although the local guest account is enabled, the user still cannot access the shared resources provided by the machine. This is because the group policy does not allow the guest account to access the machine from the network by default.

Click "Start → Run", enter "gpedit.msc" in the run box, and then expand "Local Computer Policy → Computer Configuration → Windows Settings → Security Settings → Local Policies → User" in the Group Policy window. Right assignment" (Figure 1), find the "Reject access to this computer from the network" item in the right column, delete the Guest account after opening, then open the "Access this computer from the network" item, add the Guest account in the properties window . In this way, you can use the Guest account to access the shared resources of the machine from the network. This method is suitable for Windows 2000/XP/2003 systems.

Figure 1

3. Properly configuring the network firewall

Many machines have a network firewall installed. If it is not properly set up, it will also prevent users from accessing the shared resources of this machine. In this case, you need to open the NetBIOS port required for the shared resources of this machine. The author takes Skynet firewall as an example. In the "Custom IP Rules" window, select the "Allow LAN machines to use my shared resources" rule, and finally click the "Save" button, thus opening the NetBIOS port.

4. Reasonable setting of user access rights

Many machines in the network use the NTFS file system. Its ACL function (access control list) can control the access rights of users. Users must access the shared resources of these machines. Permissions are fine. If you use the Guest account to access the CPCW shared folder of the machine, right click on the shared directory, select "Properties", switch to the "Security" tab, then add the Guest account to the user list, and then specify the Guest access rights, at least To give the "Read" and "List Folder Directory" permissions (Figure 2). If you want to allow multiple user accounts to access the shared directory, just add the Everyone account, and then give the "Read" and "List Folder Directory" permissions, so avoid adding and specifying each user access account one by one. This method is suitable for Windows 2000/XP/2003 systems that use the NTFS file system.

Figure 2