Basic conditions for Windows online neighbor visits:
1) Both parties have computers turned on and network shared resources are set up;
2) Both computers have added the "Microsoft Network File and Print Sharing" service;
3) Both parties have correctly set up the IP address within the network and must be in one network segment;
4) The firewall is turned off in both computers, or there is no policy in the firewall policy that blocks access to the online neighbors.
Windows 98/2000/XP/2003 User verification issues for accessing XP
First of all, the question about why it is not accessible to enable Guest:
1. By default, XP disables Guest account
2. By default, XP's local security policy prohibits Guest users from accessing from the network.
3. By default, in XP's local security policy -> security options, "Account: Users can only log in with empty passwords" is enabled, that is, any account with empty passwords cannot be accessed from the network and can only log in locally. Guest defaults to empty password...
Therefore, if you need to use Guest user to access XP, you need to make the above three settings: enable Guest, modify security policies to allow Guest to access from the network, disable the security policies in 3, or add a password to Guest.
Sometimes you will encounter another situation: when accessing XP, the user name in the login dialog box is grayed out, and it is always a Guest user, and you cannot enter another user account.
The reason is that this security policy is at the forefront (Administrative Tools -> Local Security Policy -> Security Options -> "Network Access: Sharing and Security Mode for Local Accounts"). By default, XP access method is the "guest-only" method, so when you access it, of course, it is fixed that Guest cannot enter other user accounts.
Therefore, the easiest way to access XP is: don't enable Guest, just modify the above security policy to "classic". Other systems can enter their account information by accessing XP.
As for access 2003, Guest is disabled by default in 2003, but there is no XP's annoying default contradictory guest sharing, so you can directly enter the username and password to access.
A small office LAN is a winxp system, and can access the external network. You can also see the other party's computer, but you cannot see the other party's shared computer prompting that the network path is incorrect, or you do not have permission to use the network. This is probably what I remember clearly! ! I have enabled the guest account too! WinXP's firewall is also closed, and there is no problem with the IP address! ! Hope everyone analyze it! ! Thank you so much!
Cause: There are security policy restrictions in Win2000/XP.
Sometimes, Win2000/XP is too "smart". Although we have enabled the Guest account, we still cannot access Win2000/XP from Win98. For example, if we use a firewall vulnerability patch like Rising, it will modify the policy of "rejecting this computer from the network" and modify it back according to the following method:
Start -> Run -> -> Computer Configuration -> Windows Settings -> Local Policy -> User Rights Assignment -> Delete the guest user in "Denied access to this computer from the network".
Win2000/XP and Win98 visit each other
If both computers use Win2000/XP operating system, then forming a LAN is a very simple and easy task. After the hardware connection is completed, you can see each other immediately in the "Online Neighbor". But if there is a computer in the LAN using Win98, the situation is not certain. We often find that although the Ping command can be passed, it is still impossible to achieve mutual access in "online neighbors". What should we do at this time?
Countermeasure 1: Enable Guest user in Win2000/XP. After the Win2000/XP system is installed, two user accounts will be established by default, namely Administrator and Guest. All users who are not assigned to the account on the local computer will use the Guest account by default, which has no password. However, under the default settings, this Guest account is not enabled. We can find the "Guest" account from "Control Panel Management Tools Computer Management Local Users and Groups", and right-click to open the "Guest Properties" dialog box, and remove the hook mark on the "Account Deactivated" check box here, so that after exiting, you can access Win2000/XP from Win98.
In fact, after enabling the Guest account, the biggest benefit is that you do not need to enter your username and password when accessing Win2000/XP from Win98. This method is more suitable for local area networks with uncertain users and large access, but it is not applicable to home users.
Countermeasure 2: Check whether there are security policy restrictions in Win2000/XP. Sometimes, Win2000/XP is too "smart". Although we have enabled the Guest account, we still cannot access Win2000/XP from Win98. At this time, we need to find "Accessing this computer from the network" or "Denied access to this computer from the network" from the "Control Panel Management Tools Local Security Policy Local Policy User Rights Assignment", and then check whether there is a Guest account or other corresponding account, and then add or delete it according to different situations.
Countermeasure 3: Disable the firewall on the local connection. A firewall acts as a security system that defends the boundaries between the network and the external world. Microsoft provides users with a built-in Internet connection firewall (ICF) in WinXP. When enabled, it can limit some unsafe information from the outside to enter the internal network. However, if you enable this firewall on your local connection, it will cause the workgroup to be unable to access each other, and there will be similar prompts such as "XXX cannot access", "You may not have permission to use network resources", "Please contact the administrator of this server to find out whether you have access", "The network path cannot be found", etc. At this time, please disable the firewall blocking of the local connection.
Countermeasure 4: Add NetBEUI protocol to WinXP. In fact, adding the NetBEUI protocol directly is sometimes easier to solve the problem of not being able to access each other, and it can solve the problem of enabling firewalls mentioned above. The NetBEUI protocol will be automatically installed when Win98 is installed, but since WinXP no longer provides technical support for the NetBEUI protocol, it can only be added manually.
Find the WinXP installation CD, enter the "valueaddMsftNetNetbeui" folder, there are 3 files in total, first copy the file to the "WindowsSystem32Drivers" folder of the machine (the native computer here refers to the computer where WinXP is installed), and then copy the file to the "WindowsINF" folder of the machine. The file is optional. However, the INF folder has hidden attributes, and users need to select the display file in the "Tools Properties" window under WinXP to see the directory.
Countermeasure 5: Enable "File and Printer Sharing" in Win98. This is a very simple but often overlooked problem. Although machines with Win2000/XP can be found in "Online Neighbors", they are inaccessible. This is because Win98 is not enabled "Allow other users to access my files". Enable this option can solve this problem.
Of course, in addition to the various reasons mentioned above, there are two computers not in the same working group, or the internal IP addresses of the two computers conflict, even Hub failures, line failures, etc.
Microsoft Knowledge Base Article - 318030
Unable to access shared files and folders or browse computers in a workgroup
/?scid=kb;cn;318030
3) Both parties have correctly set up the IP address within the network and must be in one network segment;
This is not necessarily the case, because the name resolution problem can be solved by using WINS services.-
1) Both parties have computers turned on and network shared resources are set up;
2) Both computers have added the "Microsoft Network File and Print Sharing" service;
3) Both parties have correctly set up the IP address within the network and must be in one network segment;
4) The firewall is turned off in both computers, or there is no policy in the firewall policy that blocks access to the online neighbors.
Windows 98/2000/XP/2003 User verification issues for accessing XP
First of all, the question about why it is not accessible to enable Guest:
1. By default, XP disables Guest account
2. By default, XP's local security policy prohibits Guest users from accessing from the network.
3. By default, in XP's local security policy -> security options, "Account: Users can only log in with empty passwords" is enabled, that is, any account with empty passwords cannot be accessed from the network and can only log in locally. Guest defaults to empty password...
Therefore, if you need to use Guest user to access XP, you need to make the above three settings: enable Guest, modify security policies to allow Guest to access from the network, disable the security policies in 3, or add a password to Guest.
Sometimes you will encounter another situation: when accessing XP, the user name in the login dialog box is grayed out, and it is always a Guest user, and you cannot enter another user account.
The reason is that this security policy is at the forefront (Administrative Tools -> Local Security Policy -> Security Options -> "Network Access: Sharing and Security Mode for Local Accounts"). By default, XP access method is the "guest-only" method, so when you access it, of course, it is fixed that Guest cannot enter other user accounts.
Therefore, the easiest way to access XP is: don't enable Guest, just modify the above security policy to "classic". Other systems can enter their account information by accessing XP.
As for access 2003, Guest is disabled by default in 2003, but there is no XP's annoying default contradictory guest sharing, so you can directly enter the username and password to access.
A small office LAN is a winxp system, and can access the external network. You can also see the other party's computer, but you cannot see the other party's shared computer prompting that the network path is incorrect, or you do not have permission to use the network. This is probably what I remember clearly! ! I have enabled the guest account too! WinXP's firewall is also closed, and there is no problem with the IP address! ! Hope everyone analyze it! ! Thank you so much!
Cause: There are security policy restrictions in Win2000/XP.
Sometimes, Win2000/XP is too "smart". Although we have enabled the Guest account, we still cannot access Win2000/XP from Win98. For example, if we use a firewall vulnerability patch like Rising, it will modify the policy of "rejecting this computer from the network" and modify it back according to the following method:
Start -> Run -> -> Computer Configuration -> Windows Settings -> Local Policy -> User Rights Assignment -> Delete the guest user in "Denied access to this computer from the network".
Win2000/XP and Win98 visit each other
If both computers use Win2000/XP operating system, then forming a LAN is a very simple and easy task. After the hardware connection is completed, you can see each other immediately in the "Online Neighbor". But if there is a computer in the LAN using Win98, the situation is not certain. We often find that although the Ping command can be passed, it is still impossible to achieve mutual access in "online neighbors". What should we do at this time?
Countermeasure 1: Enable Guest user in Win2000/XP. After the Win2000/XP system is installed, two user accounts will be established by default, namely Administrator and Guest. All users who are not assigned to the account on the local computer will use the Guest account by default, which has no password. However, under the default settings, this Guest account is not enabled. We can find the "Guest" account from "Control Panel Management Tools Computer Management Local Users and Groups", and right-click to open the "Guest Properties" dialog box, and remove the hook mark on the "Account Deactivated" check box here, so that after exiting, you can access Win2000/XP from Win98.
In fact, after enabling the Guest account, the biggest benefit is that you do not need to enter your username and password when accessing Win2000/XP from Win98. This method is more suitable for local area networks with uncertain users and large access, but it is not applicable to home users.
Countermeasure 2: Check whether there are security policy restrictions in Win2000/XP. Sometimes, Win2000/XP is too "smart". Although we have enabled the Guest account, we still cannot access Win2000/XP from Win98. At this time, we need to find "Accessing this computer from the network" or "Denied access to this computer from the network" from the "Control Panel Management Tools Local Security Policy Local Policy User Rights Assignment", and then check whether there is a Guest account or other corresponding account, and then add or delete it according to different situations.
Countermeasure 3: Disable the firewall on the local connection. A firewall acts as a security system that defends the boundaries between the network and the external world. Microsoft provides users with a built-in Internet connection firewall (ICF) in WinXP. When enabled, it can limit some unsafe information from the outside to enter the internal network. However, if you enable this firewall on your local connection, it will cause the workgroup to be unable to access each other, and there will be similar prompts such as "XXX cannot access", "You may not have permission to use network resources", "Please contact the administrator of this server to find out whether you have access", "The network path cannot be found", etc. At this time, please disable the firewall blocking of the local connection.
Countermeasure 4: Add NetBEUI protocol to WinXP. In fact, adding the NetBEUI protocol directly is sometimes easier to solve the problem of not being able to access each other, and it can solve the problem of enabling firewalls mentioned above. The NetBEUI protocol will be automatically installed when Win98 is installed, but since WinXP no longer provides technical support for the NetBEUI protocol, it can only be added manually.
Find the WinXP installation CD, enter the "valueaddMsftNetNetbeui" folder, there are 3 files in total, first copy the file to the "WindowsSystem32Drivers" folder of the machine (the native computer here refers to the computer where WinXP is installed), and then copy the file to the "WindowsINF" folder of the machine. The file is optional. However, the INF folder has hidden attributes, and users need to select the display file in the "Tools Properties" window under WinXP to see the directory.
Countermeasure 5: Enable "File and Printer Sharing" in Win98. This is a very simple but often overlooked problem. Although machines with Win2000/XP can be found in "Online Neighbors", they are inaccessible. This is because Win98 is not enabled "Allow other users to access my files". Enable this option can solve this problem.
Of course, in addition to the various reasons mentioned above, there are two computers not in the same working group, or the internal IP addresses of the two computers conflict, even Hub failures, line failures, etc.
Microsoft Knowledge Base Article - 318030
Unable to access shared files and folders or browse computers in a workgroup
/?scid=kb;cn;318030
3) Both parties have correctly set up the IP address within the network and must be in one network segment;
This is not necessarily the case, because the name resolution problem can be solved by using WINS services.-