Make communication more free. Unlock Win XP file sharing restrictions

        Many of my friends have encountered such a problem: on a computer with Windows XP installed, even if the network connection and sharing settings are correct (such as the IP address belongs to the same subnet, NetBiOS on TCP/IP is enabled, the firewall software does not have Users who use 135, 137, 138, and 139 ports for file sharing are prohibited. Users who use other systems (including Windows 9X/Me/2000/XP, etc.) still cannot access the computer. How should we solve this problem?

By default, the Windows XP local security settings require users to access the network in the guest mode. At the same time, the Guest user is prohibited from accessing the system through the network in the user rights assignment of the Windows XP security policy. These two conflicting security policies have caused other users on the network to access computers using Windows XP over the network. You can use the following methods to solve.

Method 1 Unlock the Guest Account

Click “Start→Run”, enter “GPEDIT.MSC” in the “Run” dialog box, open the Group Policy Editor, and select “ Computer Configuration→Windows Settings→Security Settings→Local Policies→User Rights Assignment, double-click the “Deny access to this computer from the network” policy (see Figure 1), delete the “GUEST” account inside. In this way, other users can use the Guest account to access the computer using Windows XP system through the network.

Figure 1

Method 2 Change the network access mode

Open the Group Policy Editor and select "Computer Configuration→Windows Settings→Security Settings→Local Policies→Security Options" Double-click the "Network access: Sharing and security mode for local accounts" policy, and change the default setting "Guest only - Local user authentication" to "Classic: Local users authenticate with their own identity".

Now, when other users access a computer using Windows XP over the network, they can log in with their own "identity" (provided that this account already exists in Windows XP and the password is correct).

When the policy is changed, the way the files are shared is also changed. After the "Classic: Local users authenticate by themselves" mode is enabled, we can limit the number of users accessing shared files at the same time, and Different access rights can be set for different users.

However, we may encounter another problem. When the user's password is empty, the access will be rejected. Originally, in the "Security Options", there is an "Account: Local account with blank password only allows console login" policy is enabled by default. According to the principle of rejecting priority in Windows XP security policy, users with empty passwords access through the network. Computers using Windows XP will be banned. We just need to disable this strategy to solve the problem.