Causes and solutions for Windows xp failure to Access Windows 7 Shared Folders

 

For system security, the system's Guest account is disabled. In addition, in Windows 2003/XP/operating systems, the Group Policy does not allow the Guest account to Access this computer from the network by default, in this way, other users are unable to access the shared resources on the local machine, and the message "Access Denied" is displayed.

 

 

1. improper access permission settings WindowsNT/2000/XP/2003 systems support NTFS file systems. using NTFS can effectively enhance system security, but in the ACL (Access Control List) if the user's access permission is not set at the time, the user may not be able to access the resources shared by the local computer, and the message "insufficient Permissions" appears.

 

2. Improper account and policy settings are in the Windows Working Group environment. Generally, you must use the Guest account to access shared resources. [Failure is often the darkness before dawn, followed by the sunset of success].

 

However, for the sake of system security, the system's Guest account is disabled. In addition, in Windows2000/XP/2003 systems, the Group Policy by default does not allow the Guest account to Access this computer from the network, in this way, other users are unable to access the shared resources on the local machine, and the message "Access Denied" is displayed.

 

3. Users with improper network firewall settings have installed a network firewall to enhance the security of the local machine and prevent illegal intrusion.

 

However, improper configuration of the network firewall also causes other users to be unable to access the shared resources on the local machine. The message "Access Denied" is displayed because the firewall disables the NetBIOS port required to share resources. TIPS: no happiness is pure, but it is always sad.

 

Solution

1. Enable 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. Therefore, you must enable the Guest account. Take Windows XP as an example. On the shared resource provider, go to "Control Panel> Management Tools", run the "Computer Management" tool, and then expand "Computer Management (local) → System Tools → local users and groups → users ", find the Guest account.

 

If a Red Cross sign appears in the Guest account, it indicates that the account has been disabled. Right-click the account and remove the check mark of "account deactivated" in the Guest Properties dialog box, click OK to enable the Guest account. This method is applicable to Windows2000, XP, and 2003 systems. * What is path? It is from the ground where there is no way to trample on, And from the place where only the thorns exist *.

 

Tip: using a Guest account to access Shared resources poses a major security risk. Of course, we can also create a specified account for each access user.

 

First, create a new account on the shared resource provider, and then specify the access permission for this account. Next, create an account with the same user name and password in the client to access the shared resource. After you log on to the client using this account, you can access the shared resources allowed by this account.

 

This method is relatively safe, but it is not suitable for large networks to create an account for each user in the network. PS: Life is very short, and it never appears twice at a time. It must be on the fly or never.

 

2. Although the local Guest account is enabled to modify the user access policy, the user still cannot access the shared resources provided by the local machine because the Group Policy does not allow the Guest account to access the local machine from the network by default.

 

Click Start> run, and enter gpedit in the run box. msc. In the Group Policy window, expand "Local Computer Policy → Computer Configuration → Windows Settings → Security Settings → local policy → user rights assignment" (figure 1 ), in the right column, find the "Deny access to this computer from the network" option, open it, delete the Guest account, and then open the "access to this computer from the network" option, add a 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 applicable to Windows2000, XP, and 2003 systems. * When others are present or alone, do not mean anything: the most important thing is self-esteem *.

 

3. Reasonably set user access permissions many machines in the network use the NTFS file system. Its ACL function (Access Control List) can control user access permissions, to access the shared resources of these machines, you must grant corresponding permissions. For example, if you use the Guest account to access the CPCW shared folder of the machine, right-click the shared directory, select "properties", switch to the "Security" tab, and add the Guest account to the user list, specify the access permission for the Guest, at least grant the "read" and "list folder directories" permissions (figure 2 ).

 

To allow multiple user accounts to access the shared directory, you only need to add the Everyone account and grant "read" and "list folder directories" permissions, this avoids adding and specifying each user's access account one by one. This method is applicable to Windows 2003, XP, and systems that use the NTFS file system.

 

4. Change the network access mode. By default, XP processes all users logging on from the network according to the Guest account. Therefore, even if the Administrator logs on from the network, only the Guest account is authorized, if the network cannot be accessed, try to 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 ". In this way, even if you do not enable guest, you can enter your local account and password to log on to the computer you want to access, the local account and password are your accounts and passwords in the computer you want to access.

 

If you need an account and password when accessing the network, you can enter the account and password in the computer you want to access to log on. If you do not change the access mode, you may not be able to enter the user name and password, // computername/guest is unavailable. Even if the password is empty, you cannot click confirm to log on without enabling guest. In Classic mode, you can enter the user name and password to log on to your computer.

 

5. Correctly configure the network firewall. Many machines have installed the network firewall. Its improper configuration also prevents users from accessing the shared resources of the local machine. In this case, the NetBIOS port required for sharing resources of the local machine must be opened. Taking Skynet firewall as an example, in the "custom IP rules" window, select the "allow LAN machines to use my shared resources" rule, and click "save, in this way, the NetBIOS port is opened.

 

6. We may also encounter another noteworthy problem, that is, when the user's password is empty, you cannot log on even if you have made any of the above changes, access is rejected.

 

This is because the policy "Account: A local account with a blank password can only log on to the console" in the system "Security Options" is enabled by default, based on the Denial-of-priority principle in the Windows XP security policy, users with blank passwords are prohibited from accessing Windows XP computers over the network. We only need to disable this policy to solve the problem. In the security options, find the "allow console logon only for local accounts with blank passwords" option and disable it. Otherwise, you cannot log on even if you have enabled guest and changed it to the classic mode.

 

After the above changes, you can access them. You can try to select a method that suits you. Next we will add some other problems that may occur.

 

7. The network neighbor may not be able to see the computer you want to access in the network neighbor, unless you know the computer name or IP address, by searching or directly entering // computername or // IP.

 

Follow these steps to start the "Computer Browser" service. "Computer Browser Service" maintains a computer update list on the network and provides this list to the computer designated as the browser. If the service is stopped, the list is neither updated nor maintained.

 

8. Add the NetBEUI protocol to the local network protocol.

 

9. If XPHome is used, you can only use the simple file sharing function.