A complete solution for xp lan access with no permissions and mutual access problems

A complete solution for xp lan access with no permissions:

1: log on to the system with an Administrator Account

2: Enter gpedit. MSC in "start"-"run" to enable group policy options.

3: Expand "Windows Settings"-"Local Policy"-"user assignment right", find "Deny access to this computer from the network" in the right pane of the window, and double-click it, delete the Guest account in it

4: Expand "Windows Settings"-"Local Policy"-"Security Options", and find "Network Access: sharing and security modes of Local Accounts" on the right bar, change it to "classic: Local User Authentication"

5: Expand "Windows Settings"-"Local Policy"-"Security Options" in turn and find "Account" in the right bar: local users with blank passwords can only log on to the console. "set it to" disabled "and expand" Windows Settings "-" Local Policy "-" Security Options "in the right pane. find "network access: double-click Local Account Sharing and security mode, and change it to "Guest only" to solve the problem that the local network cannot access each other.

Diagnosis of failures of mutual access within the LAN
1. incorrect user permission settings because Windows 2000/XP has a complete user management system, users cannot directly access these files only in the conventional sharing mode, but a user connection window appears, you must enter the correct user name and password to establish a connection. In this case, we need to make appropriate settings for the user group. The following describes how to implement the most common Guest users.

Step 1: double-click the "Computer Management" icon in the control panel and go to the "local users and groups → users" menu in the pop-up window, you can view all users in the current system in the right part of the window.

Step 2: double-click the "guest" user and remove the "account deactivated" check box from the pop-up Properties window (figure 2). After saving the box, you can enable the Guest account that is attached to the system. After the Guest account is activated, other users only need to double-click the shared folder in their network neighbors to perform operations on the file as a user. However, because the Guest account is attached to the Windows system, that is to say, anyone can access the files you share in this way. If some important shared resources are only provided to specific users for access, you need to set separate user permissions for them. In this case, right-click the blank area on the right of the user window, select "new user" from the pop-up window, and enter the user name and the corresponding password respectively, in this way, only the correct user name and password can be entered to establish a connection.

2. Incorrect group policy settings because the user group can manage permissions more conveniently, important files are shared in this way. However, if the user group permission settings are incorrect, file sharing may fail. For example, if you have created a user group named "file" and added users who are allowed to access important files, you can follow these steps to grant file sharing permissions. Step 1: Enter "gpedit. msc" in the "Start> Run" command window to activate the Group Policy Editor. Step 2: Go to "Computer Configuration> Windows Settings> Security Settings> Local Policy> User permission assignment" on the left side of the editor window, in this case, you can view all the policies in the current system in the right area.

Step 3: Double-click "get ownership of a file or other objects", click "add user or group" in the pop-up window, and enter a user group name such as "piII \ file. After this setting, we can block the default Windows Guest Account and use the user group method to ensure normal file sharing and greatly improve file security. In addition, some application software or maliciousProgramIt will modify some default settings in the Group Policy to allow the local machine to reject access from other machines in the LAN, in this case, double-click "Deny access to this computer from the network" in the policy option on the right of the Second Step interface, and then delete the host User Name of the local machine from the pop-up access denied list. If you do not want a user in the network to access the local machine, you can add the host User Name of the other user here. When the other user accesses your computer, the error message 7 appears. 3. firewall setup errors to enhance computer security, many friends have installed a network firewall to defend against external intrusions. However, the firewall is actually a double-edged sword, it blocks external illegal connections and may also block normal connections. If access to the computer of the other party fails, it may be due to firewall interference. Fortunately, all firewalls currently provide the trusted area access function.

Common network neighbor access problems:

1) the computers on both sides are enabled, and network sharing resources are configured;

2) both computers have added the Microsoft network file and print sharing service;

3) both parties have correctly set the IP address in the network and must be in the same network segment;

4) both computers have disabled the firewall, or the firewall policy does not block access from network peers.
Windows 98/2000/XP/2003 access to XP user authentication problems first about why the guest cannot be accessed:

1. By default, XP disables the Guest account

2. By default, XP's Local Security Policy prohibits Guest users from accessing the network.

3. By default, in XP's Local Security Policy-> Security Options, "account: users with empty passwords can only log on to the console" is enabled, that is, any account with a blank password cannot access from the network and can only log on locally. By default, guest has a blank password ...... therefore, if you need to use a guest user to access XP, You need to perform the preceding three settings: enable Guest, modify the security policy to allow guest to access from the network, disable the security policy in 3, or add a password to guest. Sometimes you may encounter another situation: when accessing XP, the username in the Login Dialog Box is gray, always a guest user, and cannot enter another user account. The reason is that this security policy is at odds (Administrative Tools> Local Security Policies> Security Options> "Network Access: sharing and security modes of Local Accounts "). By default, the XP Access Method is "only guests", so you can access it, of course, it is fixed that guest cannot enter other user accounts. Therefore, the simplest way to Access XP is: you do not need to enable Guest, just change the security policy above to "classic. Other systems can Access XP and enter their own account information. For access to 2003, guest is disabled by default in 2003, but there is no such annoying XP Guest sharing by default, so you can directly enter the user name and password for access. A small office LAN is a WINXP system that can be accessed over the Internet and can also see the other computer, but cannot see the computer shared by the other side, prompting that the network path is incorrect, or you do not have the permission to use the network! The Guest account is also enabled! The firewall of WINXP is also disabled, and there is no problem with the IP address! Cause: security policy restrictions exist in Win2000/XP. Sometimes, Win2000/XP is "smart". Although we have enabled the Guest account, we still cannot access Win2000/XP from Win98, for example, if you have used a firewall vulnerability like rising to fix it, it will modify the "Deny access to this computer from the network" policy and modify it back in the following way: Start-> Run-> gpedit. MSC-> Computer Configuration-> Windows Settings-> local policy-> User Privilege allocation-> Delete the Guest user in "Deny Access From the network to this computer. Win2000/XP and Win98 mutual access if both computers use the Win2000/XP operating system, it is very easy to set up a LAN. After the hardware connection is complete, under normal circumstances, you can immediately see the other party in "Network neighbors. However, if a computer in the LAN uses Win98, this may not be the case. We often find that although the ping command can pass, mutual access still cannot be achieved in "Network neighbors, what should I do now?

Countermeasure 1: enable Guest users in Win2000/XP. After the Win2000/XP system is installed, two user accounts are created by default, namely administrator and guest ), all users who have not been assigned an account on the local computer will use the Guest account by default. This account has no password. However, this guest account is not enabled by default, you can find the "guest" account in "Control Panel | Administrative Tools | Computer Management | local users and groups | users", and right-click the account to open the "guest properties" dialog box, remove the check mark on the "Account Disabled" check box. After exiting, you can access Win2000/XP from Win98. In fact, after the Guest account is enabled, the biggest benefit is that you do not need to enter the user name and password when accessing Win2000/XP from Win98. This method is more suitable for LAN with uncertain user and high access volume, but it is not applicable to home users.

Countermeasure 2: Check whether there are security policy restrictions in Win2000/XP. Sometimes, Win2000/XP is "smart". Although we have enabled the Guest account, we still cannot access Win2000/XP from Win98, in this case, you need to find "Access From Network" or "Deny Access From Network" from "Control Panel | Administrative Tools | Local Security Policy | Local Policy | User Privilege assignment ", check whether there is a guest account or another corresponding account, and then add or delete the account according to different situations.

Countermeasure 3: Disable the firewall on the local connection. A firewall acts as a security system to protect the boundaries between the network and the external world. In WINXP, Microsoft provides users with a built-in Internet Connection Firewall (ICF ), when enabled, You can restrict some insecure information from accessing the internal network. However, if you enable the firewall on a local connection, mutual access between Working Groups will fail, "XXX inaccessible", "you may not have the permission to use network resources", "please contact the administrator of this server to check whether you have the permission to access", "cannot find the network path" and other similar prompts, disable firewall shielding for local connections.

Countermeasure 4: add the netbeui protocol to WINXP. In fact, directly adding the netbeui protocol is sometimes easier to solve the problem of mutual access, and it can solve the problem of enabling the firewall mentioned above. The netbeui protocol is automatically installed during Win98 installation. However, since WINXP no longer provides technical support for the netbeui protocol, it can only be manually added. Find the WINXP installation CD and go to the "valueadd \ MSFT \ net \ netbeui" folder, which contains nbf.sys?netbeui.txt and netnbf. INF contains three files. copy the SYS file to the "windows \ system32 \ drivers" folder on the local machine (here the local machine refers to the computer with WINXP installed), and then copy netnbf. copy the INF file to the local "WINDOWS \ inf" folder. The netbeui.txt file is optional. However, the INF folder has a hidden attribute. You must select a display file in the "Tools | properties" window under WINXP to view the directory.

Countermeasure 5: Enable "file and printer sharing" in Win98 ". This is a very simple but often overlooked problem, that is, although machines with Win2000/XP can find machines with Win98 from "Network neighbors", but they cannot be accessed, this is because "allow other users to access my files" is not enabled in Win98. Enabling 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 are in conflict, and even include hub faults and line faults. Problem: when the client's network neighbor accesses the server, "the server does not set transaction processing" occurs, and thus the server's shared resources cannot be accessed. The same is true when you enter an IP address directly. Possible condition: IPC $ is not enabled or caused by viruses. Solution:

Method 1: run the net share IPC $ command, or directly add net share IPC $ to the registry run startup Item.

Method 2: delete the wuamgre. EXE file under % SystemRoot % \ system32.