Ask the local area network not to enjoy * * * and visit the other computer.

Your question is not clearly described. Let me show you what it is.

Open the Group Policy Editor and select Computer Configuration →Windows Settings → Security Settings → Local Policy → Security Options.

Double-click the "Network Access: * * Access and Security Mode of Local Accounts" policy, and the default setting will be "Guests only-local users will be authenticated as guests".

Change to Classic: Local users authenticate themselves.

Computers installed with Windows XP in the local area network cannot access each other with computers installed with Windows 98, and computers installed with Windows XP cannot communicate with each other. I have seen many experts' clever tricks, which can be summarized as follows: first, open a guest account; The second is to install NetBEUI protocol; The third is to check whether the GUEST account is disabled by the local security policy setting; The fourth is to set up * * * shared folders. However, even if these four points are achieved, sometimes the problem of mutual visits between Windows XP cannot be solved. Because if you want to exchange visits in Windows XP, you need to set this step:

Right-click My Computer on the Windows desktop, select Properties, and then click the Computer Name tab to see if your LAN workgroup name, such as TL2000, appears in this tab. Then click the "Network ID" button to start the "Network Identification Wizard": click "Next" and select "This computer is part of a commercial network, and use it to connect other working computers"; Click "Next" and select "The company uses a domain-free network"; Click the Next button, then enter the workgroup name of your local area network, such as "TL2000", click the Next button again, and finally click the Finish button to complete the setup.

After restarting the computer, computers in the local area network can access each other.

Common Online Neighborhood Access Problem Set

Basic conditions for window neighbors to exchange visits;

1) Both computers are turned on and network resources are set up;

2) The "Microsoft Network File and Print * * *" service has been added to both computers;

3) Both parties have correctly set the IP addresses in the network, and they must be in a network segment;

4) Both computers have turned off the firewall, or there is no policy in the firewall policy to prevent online neighbors from accessing.

User authentication of Windows 98/2000/XP/2003 accessing XP

First of all, why can't I access an enabled guest?

1. By default, XP disables guest accounts.

2. By default, XP's local security policy prohibits guest users from accessing the network.

3. By default, the local security policy of XP-- >; In the security option, "account: users with blank passwords can only log in to the console" is enabled, that is to say, any account with blank passwords can not be accessed from the network, and can only log in locally, and the default password for guests is blank. ......

Therefore, if you need to use the Guest user to access XP, you should make the above three settings: enable the Guest, modify the security policy to allow the Guest to access from the network, disable the security policy in 3 or add a password to the Guest.

Sometimes you will encounter another situation: when accessing XP, the user name in the login dialog box is gray, and it has always been a Guest user, so you can't access other user accounts.

The reason is that this security policy is at work (administrative tools->; Local security policy->; Security options-> "Network Access: Access and Security Mode of Local Accounts"). By default, XP's access mode is "Guest only", so if you visit, you can't enter other user accounts as a Guest.

Therefore, the easiest way to access XP is to change the above security policy to "classic" without enabling Guest. Other systems can enter their own account information when accessing XP.

As for access to 2003, by default, visitors are forbidden in 2003, but XP is not enjoyed, that is, the annoying default and contradictory visitor mode, where you can directly enter your user name and password to access.

A small office LAN, all of which are winxp systems, can access the external network and see the other party's computer, but not seeing the computer shared by the other party means that the network path is incorrect, or you don't have permission to use the network. That's probably what it means. I can't remember clearly! ! I also enabled the guest account! The firewall of winxp is also closed, and there is no problem with the ip address! ! I hope everyone will analyze it! ! Thank you very much.

Reason: There are security policy restrictions in Win2000/XP.

Sometimes, Win2000/XP is too smart. Although we have enabled the Guest account, we still can't access Win2000/XP from Win98. For example, if we use a firewall vulnerability patch like Rising, it will modify the policy of "denying network access to this computer" in the following ways:

Start-> Run-> gpedit . MSC-& gt； Computer configuration-> Windows settings-> Local policy-> User rights assignment-> Delete the guest user in "Deny access to this computer from the network".

Exchange visits between Win2000/XP and Win98

If both computers use Win2000/XP operating system, it is very easy to set up a local area network. When the hardware connection is completed, you can see each other in the "Online Neighborhood" immediately under normal circumstances. However, if the computers in the LAN use Win98, the situation is not necessarily the case. We often find that although the Ping command can be passed, it is still impossible for "online neighbors" to exchange visits. What should we do at this time?

Countermeasure 1: Enable the Guest user in Win2000/XP. After Win2000/XP system is installed, two user accounts will be established by default, namely Administrator (System Administrator) and Guest (Guest Account). By default, all users who are not assigned to the local computer account will use the guest account, and the account has no password. However, by default, this guest account is not enabled. We can find the "Guest" account in Control Panel | Administrative Tools | Computer Management | Local Users and Groups | Users, right-click to open the "Guest Properties" dialog box, and remove the check mark of the "Disable Account" check box here, so that we can access Win2000/XP from Win98 after exiting.

In fact, after the Guest account is enabled, the biggest advantage is that you don't need to enter a user name and password when accessing Win2000/XP from Win98. This method is more suitable for local area networks with uncertain users and large visits, but not suitable for 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 can't access Win2000/XP from Win98. At this point, we should find "Access this computer from the network" or "Access this computer from the network is denied" from "Control Panel | Administrative Tools | Local Security Policy | Local Policy | User Rights Assignment", and then check whether it appears.

-

Countermeasure 3: Disable the firewall for local connection. Firewall is a kind of security system, which acts as the boundary between the network and the outside world. Microsoft provides users with a built-in Internet Connection Firewall (ICF) in WinXP, which can prevent some unsafe information from entering the intranet from the outside. However, if this firewall is enabled on the local connection, mutual access between workgroups will be prevented, and similar prompts will appear, 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 permission" and "The network path cannot be found". Please disable firewall shielding for local connection at this time.

-

Countermeasure 4: add NetBEUI protocol to WinXP. In fact, it is sometimes easier to solve the problem of mutual access by directly adding NetBEUI protocol, and it can also solve the problem of enabling firewall mentioned above. NetBEUI protocol will be automatically installed when Win98 is installed, but it can only be added manually because WinXP no longer provides technical support for NetBEUI protocol.

Find out the installation CD of WinXP and enter the folder "valueadd\Msft\Net\Netbeui", which contains three files: Nbf.sys, Netbeui.txt and netnbf.inf * * *. Copy the Nbf.sys file to the "Windows\System32\ Drivers" folder (the local computer here refers to the computer with WinXP installed), and then copy the Netnbf.inf file to the "Windows\INF" folder of the local computer, and the Netbeui.txt file is optional. However, the INF folder has hidden properties, and users need to select "Show 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, that is, a machine with Win2000/XP can find a machine with Win98 from "My Network Neighborhood", but because Win98 has not enabled "Allow other users to access my files", it cannot be accessed. Enabling this option can solve this problem.

Of course, in addition to the reasons mentioned above, there are two computers that are not in the same workgroup, or the IP addresses of the two computers conflict, even including hub failure and line failure.

=======================================================================

Six classic exchange visits in LAN

The topic of not accessing each other in LAN has always been very concerned by network managers. Recently, many netizens have raised similar problems, mainly because Windows98 cannot access WindowsXP, or Windows2000 and WindowsXP cannot access WindowsXP. The following is a summary of the solutions for these mutual visits.

Question 1: How to use the hardware exclusion method?

Using the ping command combined with the method of checking the indicator light of the network card can verify whether it is a hardware problem or a software problem.

Check the network card light first. If they are not turned on, there is something wrong with the network card. If only the signal light of the network card is off, click Start → Run and enter "ping the other IP -t" (the actual input is without quotation marks). If "request timeout" (request pause//timeout) appears four times in a row in the prompt, it means that the physical line is blocked or the network is too busy. You can use the line tester to further check the network cable and network header and troubleshoot them one by one.

Question 2: What if there is no agreement?

The necessary protocols for LAN mutual visits: TCP/IP (IPX/SPX, Novell network and some online games should be set up when necessary) and NetBIOS.

1.NetBIOS protocol

NetBIOS protocol is not supported by default in WindowsXP, but it is adopted by many small networks now. The adding method is as follows:

(1) copy the nbf.sys file in the Valueadd\MSFT\Net\netbeui directory of the Windows XP installation CD to the \system32\Drivers directory of the system;

(2) Copy netnbf.inf to the \lnf directory of the system, and then add the protocol as usual (online neighbors have the corresponding option to add the protocol, so you can add it directly by putting the Windows installation disk into the CD-ROM drive).

2.NetBEUI protocol

This communication protocol is the product of the Windows95/98 era, and there is no such protocol in WindowsXP (but NetBEUI related files are still on the WindowsXP CD). Some LANs must have NetBEUI to access some or all computer data in the network, so it is necessary to install NetBEUI. The method is as follows:

Put it into the WindowsXP installation CD, and copy Netnbf.inf to C:\Windows\INF in the directory of "ValueaddMsftNetNetbeui"; Copy Nbf.sys to c: \ Windows \ System32 \ drivers; Click "Start → Control Panel → Network Neighborhood" in turn, select "Network Connection", right-click "LAN Connection" and select the content; In the "General" item, click "Install → Communication Protocol → Add" in turn, and you will see "NetBEUI Protocol". After selecting NetBEUI, press OK.

Question 3: How to deal with the setting error?

Ensure that the IP of all computers are in the same network segment and all computers are in the same workgroup (or domain). Before changing the workgroup, if your computer is already a member of the domain, you should ask the administrator to detach you from the domain and deactivate your computer account. To modify a workgroup, you must log in as an administrator.

In addition, make sure that the firewall is not set too high, otherwise the necessary communication ports may be closed. It is recommended to shut down and try again.

Question 4: Is the service installed?

In order to achieve * * *, "Microsoft Network File and Print Service" needs to be installed. The steps are as follows: enter the control panel → Local Area Connection → Properties → Installation, click Services → Add in the Select Network Component Type dialog box, and click the service to be installed in the Select Network Service dialog box.

Question 5: Do you want to distinguish between local networks?

Local area networks (LANs) include local area networks with and without domains. For the domain network, you should also select "Microsoft Network User" in the "Main Network Login" of the "Network" attribute to ensure that the domain name is filled in correctly.

Question 6: What should I do if the account is miscalculated?

If you are connected to an external network, it is not recommended to enable the guest account. If it is only used in the local area network, it can be enabled directly, which is more convenient to access, but there are also many precautions.

1. Open the guest user

You don't need to set a password, just enter the account Guest to log in (exchange visits). However, it is necessary to ensure that the following strategies are enabled.

Click "Start → Run" and enter "gpedit.msc" to open the group policy. Click "Computer Configuration →Windows Settings → Security Settings → Local Policies → Security Options" and find "Account: Only local users with blank passwords are allowed to log on to the console". Once enabled, you cannot access it remotely with a blank password. Turn it off.

Lift the ban on guests

(1) Open Group Policy, click "Computer Configuration →Windows Settings → Security Settings → Local Policy → User Permission Assignment" in turn, and double-click "Deny access to this computer from the network" to see if there are any guests. If yes, please delete it.

(2) Still in the above group policy, double-click the item "Access this computer from the network" to see if there are any guests. If not, please add.

(3) Still in the group policy, click Computer Configuration →Windows Settings → Security Settings → Security Options, double-click Network Access: Access and Security Mode of Local Accounts, and change the default setting of "Guests only → Local users authenticate as guests" to "Classic → Local users authenticate as their own".

In addition, if you can only see the file directory of WindowsXP computer, you can't enter the folder. This is because WindowsXP defaults to a simple * * * way to enjoy files, which can be modified: in the Explorer, click Tools → Folder Options, and in the View tab, remove the check in front of "Enjoy Simple Files * * * (Recommended)" in the advanced settings.