Secondly, there are many descriptions of the problem on the Internet, so I won't go into details here. When there is a problem with * * * access, please consider the following steps: 1. Check whether the guest account is opened. On the desktop, right-click My Computer-Administration-Local Users and Groups-Users, and then right-click Guests-Properties-Cancel Disabled Accounts in the box on the right.
XP doesn't open the guest account by default, so please enable the guest account to let others browse your computer. At the same time, for the sake of safety, please set a password or corresponding permissions for the guests. Of course, you can also set a user name and password for each machine to facilitate mutual access between computers.
2. Check whether guest users are denied access to this computer from the network.
When you open the guest account but still can't access it at all, please check whether the setting is to deny the guest access to the computer from the network, because XP 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. When the system Guest user opens, cancel the restriction on the Guest account, click Start → Run, and enter GPEDIT. In the running dialog box, MSC opens the Group Policy Editor, selects computer configuration →Windows settings → security settings → local policy → user rights assignment, and double-clicks the policy of denying access to this computer from the network to delete the GUEST account. In this way, other users can use the Guest account to access computers using Windows XP system through the network.
3. Change the network access mode
By default, XP treats all users who log in from the network as guest accounts, so even if administrators log in from the network, they only have guest rights. If it is not accessible, try to change the access mode of the network. Open the Group Policy Editor, select computer configuration →Windows settings → security settings → local policies → security options, and double-click the policy of "Network access: access and security mode of local accounts" to change the default setting of "Only guests-local users authenticate as guests" to "Classic: local users authenticate as their own".
In this way, even if you don't open a guest, you can log in to the computer you want to access by entering the local account and password, which are the existing accounts and passwords in the computer you want to access. If you need an account and password to access the network, you can log in by entering your existing account and password in the computer you want to access.
If you don't change the access mode, you may not even be able to enter the user name and password, and //computername/guest is grayed out and unavailable. Even if the password is empty, visitors can't click OK to log in without opening it. In the classic mode, you can at least enter the user name and password to log in to the computer you want to enter, just like when the guest account was not opened in 2000. Maybe you will encounter special circumstances, please see below.
4. A noteworthy problem
We may encounter another problem, that is, when the user's password is empty, even if you make all the above changes, you can't log in, and access will still be denied. This is because the policy of "Account: Only allow local accounts with blank passwords to log in to the console" is enabled by default in the system Security Options. According to the principle of denial priority in Windows XP security policy, users with empty passwords will be prohibited from accessing computers using Windows XP through the network. We just need to disable this policy to solve the problem. Find the item "Only allow local accounts with blank passwords to log in to the console" in the security options, and just disable it, otherwise even if you open the visitor, you can't log in in the classic mode. After the above changes, it is basically accessible. You can try to choose a method that suits you. Here are some other problems that may be encountered.
5. The computer can't be seen by network neighbors. You may often not see the computer you want to visit in your online neighborhood unless you know the name or IP address of the computer by searching or directly typing //computername or //IP. Please do the following: Start the Computer Browser service. The computer browser service maintains an updated list of computers on the network and provides the list to computers designated as browsers. If this service is stopped, the list will neither be updated nor maintained.
137/UDP-NetBIOS name server, Network Basic Input/Output System (NetBIOS) name server (NBNS) protocol is a part of NetBIOS(NetBT) protocol family over TCP/IP, which provides a method for mapping host names and addresses on the network based on NetBIOS name access.
138/UDP-NetBIOS datagram is a part of NetBIOS(NetBT) protocol family on TCP/IP, which is used for network login and browsing.
139/TCP-NetBIOS session service is a part of NetBIOS(NetBT) protocol family on TCP/IP, which is used for server message block (SMB) and file * * * sharing and printing. Please set the firewall to open the corresponding port. Generally, you only need to allow folders and printers to enjoy the services inside the firewall.
6. About * * * enjoyment mode
XP for * * * only gives guests permission by default or chooses to allow users to change my files. In Windows 2000 operating system, it is very simple for users to set the * * * enjoyment attribute of folders. Just right-click the folder and select Properties to see the * * * Enjoy Settings tab. However, it is complicated to set the folder * * * in Windows XP system, and users cannot see the setting label of * * * through the above operations. The specific modification method is as follows: open the tools in my computer, select folder properties, bring up the view tab, scroll to the bottom in the advanced settings section to deselect the simple file * * * before enjoying (recommended), and deselect it if there is "Mickey Mouse" in the options bar. In this way, users can modify folder properties as easily as using Windows 2000.
7. About the problem of no response or slow response when network neighbors visit.
When browsing online neighbors in WinXP and Win2000, the system will be delayed for 30 seconds by default, and Windows will use this time to search whether the remote computer has a specified scheduled task (even online search). If the network doesn't respond when searching, it will fall into infinite waiting, so it is not surprising that there is a delay or even an error exceeding 10 minutes. Here are the specific solutions. A. close the task scheduler of WinXP.
You can open the task scheduler's properties dialog box in the control panel/administrative tools/services, click the stop button to stop the service, and then set the startup type to manual, so that the service will not be started automatically next time. Delete two subkeys in the registry.
Find the primary key of "HKEY _ local _ machine software Microsoft Windows CurrentVersionExplorerModeComputerSpace" in the registry, and delete the following two subkeys.
Among them, the first subkey determines whether online neighbors should search for printers on the Internet (even on the Internet). If there is no printer on the network, you can delete this key. The second sub-health determines whether it is necessary to find the designated planned task, which is the chief culprit of the slow neighbors of online games, and this sub-health must be deleted.
abstract
Unable to access mainly because XP does not open the guest by default. Even if the guest is opened, XP does not allow the guest to access the computer from the network by default. Then there is the problem worthy of attention. I believe that some places that don't consider security or computer companies give people system passwords are empty, but this is not allowed to log in. As long as you try the above methods, I believe there will be no more problems.