Windows XP system cannot set folder sharing

Windows XP system sharing Workgroup is inaccessible. You may not have permission to use network resources. 1. Check if the guest account is open. On the desktop, right click on My Computer - Manage - Local Users and Groups - User, then in the box on the right, right click on the guest - Properties - Uncheck the account has been disabled Just fine. XP system does not open the guest account by default, so for others to browse your computer, please enable the guest account. At the same time, for security, please set a password or corresponding permission for the guest. Of course, you can also set a username and password for each machine so that computers can access each other. 2. Check if the Guest is denied access to the machine from the network. When you open the guest account but still cannot access it at all, please check if the setting is to reject the guest from the network to access the computer, because the XP system home does not allow the guest to log in from the network by default. , so even if you open the guest, you can't access it. Unlock the Guest account when the system Guest user is enabled, click “Start →Run”, in the "Run” dialog box, enter “GPEDIT.MSC” to open the Group Policy Editor, in turn Select “Computer Configuration & Rarr; Windows Settings & Rarr; Security Settings & Rarr; Local Policies & Rarr; User Rights Assignment & rdquo;, double-click "Reject access to this computer from the network" strategy, delete the "GUEST" account. In this way, other users can use the Guest account to access the computer using Windows XP system through the network. 3. Change the network access mode By default, the XP system processes all users who log in from the network according to the guest account. Therefore, even if the administrator logs in from the network, it only has the guest's permission. If it is unable to access, please try to change the network. Access mode. Open the Group Policy Editor and select “Computer Configuration →Windows Settings →Security Settings →Local Policies & Rarr;Security Options", double-click "Network Access: Local Account Sharing and Security Mode”Strategy, Default Set “only guest & mdash; local user since guest authentication & rdquo;, change to “ classic: local users authenticate with their own & rdquo;. So even if you don't open the guest, you can log in to the computer you want to access by entering your local account and password. The local account and password are the accounts and passwords already on the computer you want to access. If you need an account and password to access the network, you can log in by entering the account and password already on the computer you want to access. If you do not change the access mode, you may not be able to enter the username and password, and computername/guest is grayed out. Even if the password is empty, you can't make sure to log in without turning on the guest. Change to the classic mode, at least as long as the case of not opening the guest account in 2000, you can enter the user name and password to log in to the computer you want to enter. Maybe you will also encounter a special situation, please see the next one. 4. A noteworthy issue We may also encounter another problem, that is, when the user's password is empty, even if you do not make the login after all the above changes, the access will be rejected. This is because, in the deep system "Security Options", there is a "Account: Local account with a blank password is only allowed to log in to the console" policy is enabled by default, according to the Windows XP system security policy, the priority is denied. The principle is that when a user whose password is empty accesses a computer using Windows XP through the network, it is prohibited. We just need to disable this strategy to solve the problem. In the security options, find the "Local account with blank password only allows console login", deactivated, otherwise you can not log in even if you open the guest and change to the classic mode. After the above changes are basically accessible, you can try to choose a method that suits you. Here are some additional questions you might encounter. 5. Network Neighborhoods Cannot See Computers You may often not be able to see the computer you want to access in Network Neighborhood unless you know the computer's name or IP address, either by searching or by typing /computername or //IP. Please follow the steps below to activate: Start “ Computer Browser & rdquo; Service. “Computer Browser Service" Maintain a list of computer updates on the network and provide this list to computers designated as browsers. If this service is stopped, the list is neither updated nor maintained. 137/UDP--NetBIOS name server, Network Basic Input/Output System (NetBIOS) Name Server (NBNS) protocol is part of the NetBIOS (NetBT) protocol family on TCP/IP, which provides hosts on networks based on NetBIOS name access. Name and address mapping methods. 138/UDP--NetBIOS datagram, NetBIOS datagram is part of the NetBIOS (NetBT) protocol family on TCP/IP, which is used for network login and browsing. 139/TCP--NetBIOS Session Service, part of the NetBIOS (NetBT) protocol suite on TCP/IP, used for server message block (SMB), file sharing, and printing. Please set the firewall to open the corresponding port. Generally, it is only necessary to allow folder and printer sharing services in the firewall. 6. About the sharing mode For the XP system to download and install, the sharing default only gives the guest permission or choose to allow the user to change "my file". In the Windows 2000 operating system, users can easily set the shared properties of a folder. Just right-click on the folder and select Properties to see the Sharing Settings tab. In the latest XP system download and installation settings folder sharing is more complicated, users can not see the sharing settings tab through the above operation. The specific modification method is as follows: open “>;My Computer>;>;Tools", select “folder attribute", bring up the “view” tag, and scroll to the “Advanced Settings" At the bottom, the option "Cancel File Sharing (Recommended)" is canceled, and if the option bar has "Mickey Mouse", the item will also be cancelled. After this modification, the user can easily modify the folder properties as with Windows 2000. 7. About the problem of non-responsive or slow response to network neighbor access When browsing the network neighborhood in WinXP system and Win2000, the system will delay 30 seconds by default. Windows will use this time to search for the remote computer to have the specified scheduled task (even May go to the Internet to search). If the network does not respond when searching, it will fall into an unrestricted wait, so it is not surprising that the delay of more than 10 minutes is even reported. The following are specific solutions. A. Turn off the Schedule Taskr of the WinXP system. Go to the Properties dialog box of “Task Scheduler” in the “Control Panel/Administrative Tools/Services” and click the “Stop” button to stop the item. Service, then set the startup type to “manual", so that the service will not be started automatically the next time you start it. B. Delete the two subkeys in the registry. Locate the main key in the registry. HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionExplorerRemoteComputerNameSpace> Delete the two subkeys below. Among them, the first child determines whether the network neighbor wants to search for the printer on the Internet (even to the Internet to search), if the network does not have a shared printer, you can delete this button. The second child determines whether you need to find the specified scheduled task. This is the culprit of the very slow online neighbors. You must delete this child. Summary The main reason is that the XP system does not open the guest by default, and even if the guest is opened, the XP system does not allow the guest to access the computer from the network by default. There is also a noteworthy question. I believe that some places that do not consider security or computer companies give people the latest system passwords are empty, but this is not allowed to log in. Just try the above method, I believe there will be no more problems