Remove File Sharing restrictions for Windows XP

After installing windows? On XP computers, even if the network connection and sharing settings are correct (if the IP address belongs to the same subnet, NetBIOS on TCP/IP is enabled, no ports 135, 137, 138, and 139 are required for file sharing? 9x/ME/2000/XP) users still cannot access the computer. How should we solve this problem? By default, windows? XP's local security settings require that all network access users use the guest mode. At the same time, in windows? The User Rights Assignment in the XP security policy prohibits the Guest user from accessing the system through the network. These two conflicting security policies make it impossible for other users in the network to access windows through the network? XP computer. You can use the following methods.
Method 1. Remove the Guest account Restriction
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. So that other users can? Which of the following operations can I use to access windows through the Internet? Windows XP computer. (See)
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-only local user-initiated Identity Authentication" to "classic: Local User Authentication" by default ".
Now, when other users access a computer using Windows XP over the network, they can log on with their own "identities" (provided that windows? XP already has this account 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 original "Security Options", an "Account: A local account with a blank password can only log on to the console" policy is enabled by default. According to windows? In XP security policy, deny priority. Users with blank passwords cannot access Windows XP computers over the network. We only need to disable this policy to solve the problem.