Free Network Access removes Windows XP file sharing restrictions

Many of my friends have encountered this problem: on a computer with Windows XP installed, even if the network connection and sharing settings are correct (for example, the IP address belongs to the same subnet, enable NetBIOS on TCP/IP. The firewall software does not prohibit ports 135, 137, 138, and 139 required for file sharing ), users using other systems, including Windows 9x/ME/2000/XP, still cannot access the computer. How should we solve this problem?

By default, Windows XP's local security settings require that all users who access the network use the guest mode. In addition, in the User Privilege assignment of Windows XP security policy, Guest users are prohibited from accessing the system through the network. These two conflicting security policies prevent other users in the network from accessing Windows XP computers over the network. You can use the following methods.

Method 1 remove the restrictions on the Guest account

Click Start> Run. In the run dialog box, enter gpedit. MSC, open the Group Policy Editor, select Computer Configuration> Windows Settings> Security Settings> Local Policy> User Rights Assignment, and double-click the Deny access to this computer from the network policy, delete the "guest" account. In this way, other users can use the Guest account to access computers using Windows XP through the network.

Method 2 Change the Network Access Mode

Open the Group Policy Editor, select "Computer Configuration> Windows Settings> Security Settings> Local Policies> Security Options", and double-click the "Network Access: sharing and security modes of Local Accounts" policy, change "guest-Local User-initiated identity verification" to "classic: Local User Authentication" by default ".

When other users access a computer that uses Windows XP over the network, you can log on with your own "Identity" (provided that this account is already in Windows XP and the password is correct ).

After this policy is changed, the file sharing method also changes. After the "classic: local user authenticates with his/her own identity" method is enabled, we can limit the number of users simultaneously accessing shared files and set different access permissions for different users.

However, we may encounter another problem. When the user's password is blank, the access will still be rejected. In the past, there was an "Account: A local account with a blank password can only log on to the console" policy in the "Security Options". This policy is enabled by default. According to the deny priority principle in the Windows XP security policy, if the password is null, users cannot access Windows XP computers over the network. We only need to disable this policy to solve the problem.

# Operating System