Turn: How can I solve the problem of one of the two connected computers failing to open the shared files in the other?

1. if an error "cannot find the network path" is reported, ping its IP address first. If the ping fails, check whether it is connected to the network or the network connectivity is normal. Check whether the firewall is enabled or the corresponding port is blocked. If the IP address can be pinged but the computer name of the target machine cannot be pinged, check whether the network name resolution is correct. For how to diagnose the name resolution problem, you can first check whether there is a problem with all client machines or a machine. If the name resolution of all machines is incorrect, you need to check the DNS or WINS server on the network. If there is a problem with only one machine, you need to check the hosts and LmHosts files first. If yes, you can re-register the DNS name (ipconfig/reisterdns ).

2. If "xxx computer cannot be accessed, you may not be authorized to use network resources. Please contact the administrator of this server to check whether you have access permissions. "The error may be that the computer's security settings have been changed, and the target computer cannot be accessed. Follow these steps:

1. open "my computer", choose "Tools"> "Folder Options"> "View" from the menu, and clear the "use simple file sharing (recommended)" option.

2. right-click "my computer", select "manage", select "local user and group"-> "user", right-click the Guest user, and select "attribute ", clear the "Account Disabled" option.

3. click Start> Run and enter secpol. MSC, select "Local Policy" on the left-> "User power assignment", and double-click "access to this computer from the network" on the right to ensure that there is everyone, double-click "Deny access to this computer from the network" on the left to make sure it is empty.

4. select "Local Policy" on the left-> "Security Options",. confirm "network access: the sharing and security mode of the Local Account" on the right is "classic"; B. confirm "Microsoft Network Customer: enable digital signature for communications (always)" on the right is "disabled"; C. confirm "Microsoft Network Customer: enable digital signature for communications (if Server permits)" on the right is "enabled"; D. confirm "Microsoft network server: enable digital signature for communications (always)" on the right is "disabled"; E. check that "Microsoft network server: enable digital signature for communications (if allowed by the server)" on the right is "enabled ".

5. restart the computer.
Provide some ideas.
Set machine 2000b as follows:
1. Enable the Guest account

In many cases, for the security of the local system, the Guest account is disabled, so that you cannot access the shared resources of the machine. Therefore, you must enable the Guest account.

I will introduce Windows XP as an example. On the shared resource provider, go to "Control Panel> Management Tools", run the "Computer Management" tool, and then expand "Computer Management (local) → System Tools → local users and groups → users ", find the Guest account. If a Red Cross sign appears in the Guest account, it indicates that the account has been disabled. Right-click the account and remove the check mark of "account deactivated" in the guest Properties dialog box, click OK to enable the Guest account. This method is applicable to Windows 2000/XP/2003.

Tip: using a guest account to access Shared resources poses a major security risk. Of course, we can also create a specified account for each access user. First, create a new account on the shared resource provider, and then specify the access permission for this account. Next, create an account with the same user name and password in the client to access the shared resource. After you log on to the client using this account, you can access the shared resources allowed by this account. This method is relatively safe, but it is not suitable for large networks to create an account for each user in the network.

2. Modify the User Access Policy

Although the local guest account is enabled, the user still cannot access the shared resources provided by the local machine, because the Group Policy does not allow the Guest account to access the local machine from the network by default.

Click Start> run, and enter gpedit in the run box. MSC. In the Group Policy window, expand "Local Computer Policy → Computer Configuration → Windows Settings → Security Settings → local policy → user rights assignment" (figure 1 ), in the right column, find the "Deny access to this computer from the network" option, open it, delete the Guest account, and then open the "access to this computer from the network" option, add a guest account in the Properties window. In this way, you can use the Guest account to access the shared resources of the machine from the network. This method is applicable to Windows 2000/XP/2003.

3. Correctly configure the Network Firewall
Many machines are installed with a network firewall, Which is improperly configured. Users cannot access the shared resources of the local machine. In this case, the NetBIOS port required to share resources of the local machine must be opened. Taking Skynet firewall as an example, in the "custom IP rules" window, select the "allow LAN machines to use my shared resources" rule, and click "save, in this way, the NetBIOS port is opened.
.
4. Set Reasonable User Access Permissions
Many machines in the network use the NTFS file system. Its ACL function (Access Control List) can control user access permissions. users need to access the shared resources of these machines, you must grant the corresponding permissions. For example, if you use the Guest account to access the CPCW shared folder of the machine, right-click the shared directory, select "properties", switch to the "Security" tab, and add the Guest account to the user list, specify the access permission for the guest, at least grant the "read" and "list folder directories" permissions (figure 2 ). To allow multiple user accounts to access the shared directory, add the eeryone account and grant "read" and "list folders ?..
Currently, many people are using Win2000 and WINXP to connect to the Internet. However, many netizens report that Win2000 and WINXP are slow in browsing network neighbors, especially when the network includes Win9x and winme workstation, sometimes it may take more than 10 minutes to enable the network neighbors and often report errors. So what are the slow-speed writers? I infer that there are two main reasons.

A. Network Protocol configuration problems,

B. Problems with Windows XP scheduled tasks.

However, if other Windows computers do not see the WINXP computer in their network neighbors, it may be that the user is locked and the security policy is not set. At this time, we need to start from the following aspects. I have encountered similar problems before, but I have summarized a set of effective solutions in a large number of networking experiments, now I will teach you one by one.

I. Installation and setting of network protocols

1. Install netbeui protocol in WINXP

Yes. If you are not mistaken, install the netbeui protocol in WINXP. In WINXP, Microsoft only supports the TCP/IP protocol and the nwlink IPX/SPX/NetBIOS protocol. It officially announced that it no longer supports the netbeui protocol. However, the two Protocols Supported by Microsoft are not satisfactory in the actual use of small LAN. For example, in the process of solving the slow problem of the network neighbors, the speed of the network neighbors after I adopted many methods is better, but it is still as slow as a snail bait. In addition, when you set the protocol, client, and service binding for multiple NICs, the two Protocols also have bugs. Multiple NICs must be bound to all the protocols at the same time (except nwlink NetBIOS), customers and services, even if you cancel some of the binding and restart, the system will automatically add, which obviously cannot meet the actual needs of network construction. When I installed the netbeui protocol in WINXP, the above two problems were successfully solved.

In the "// valueadd // MSFT // net // netbeui" directory of the WINXP installation disc, there are three files, "netbeui. TXT "is the installation instructions, the other two are the files required to install the netbeui protocol. The installation procedure is as follows:

Copy "NBF. sys" to the "% SystemRoot % // system32 // drivers //" directory;
Copy "netnbf. inf" to the "% SystemRoot % // INF/" directory;

Click "Install" in Network Connection Properties to install the netbeui protocol.

Note: % SystemRoot % is the installation directory of WINXP. For example, if my WINXP is installed in the F: // Windows Directory, replace % SystemRoot % with F: // windows.

2. Set other network protocols in WINXP

I suggest that if your LAN does not need to be connected to the Internet, you only need to install the netbeui protocol. In a small LAN (with around 200 computers), netbeui is the protocol with the least memory usage and the fastest speed. The nwlink IPX/SPX/NetBIOS compatibility protocol should be deleted.

If your LAN is going to be connected to the Internet, you must install the TCP/IP protocol. However, for fast network access, we recommend that you specify the IP address of each workstation (unless there is a DHCP server in the network). Otherwise, the workstation always keeps searching for the DHCP server to slow down the network speed.

Of course, if only the TCP/IP protocol is installed in the network, mutual access can be achieved in the LAN, but it is difficult to directly see other machines in the network neighbors, you must search for a machine before accessing it. this is inconvenient for many practical networks.

3. Other Windows computer network protocol settings

Careful users may have discovered that there is a "set up home or small office network" Wizard in WINXP's network neighbors. This wizard allows you to conveniently set up LAN sharing, Internet connection, and small LAN. The wizard also provides a network installation floppy disk for other Windows computers connected to WINXP.

However, I do not advocate using this network to install a floppy disk. On other Windows computers connected to WINXP, you only need to install the netbeui protocol and set the network flag; to connect to the Internet, you only need to install the TCP/IP protocol and specify the IP address. This is exactly the same as the traditional LAN Settings. We recommend that you use less IPX/SPX compatible protocols.

Ii. Completely disable scheduled tasks of WINXP

When browsing network neighbors in WINXP and win2000, the system will be delayed by 30 seconds by default. Windows will use this time to search for specific scheduled tasks on the remote computer (or even to search the Internet ). If the network does not respond during the search, there will be an unlimited wait, so it is not surprising that the latency of more than 10 minutes or even an error is reported. The specific solution is as follows.

1. Disable the scheduled Task Service (Task sched) of WINXP)

You can go to "control panel, administrative tools, and services" to open the "Task Scheduler" attribute dialog box, click "stop" to stop the service, and set the start type to "Manual ", in this way, the service will not be automatically started at the next startup.

2. Delete two subkeys in the registry.

Find the primary key"
HKEY_LOCAL_MACHINE // software // Microsoft // windows // CurrentVersion // explorer // remotecomputer //
Namespace"
Delete the following two child keys
{2227a280-3aea-1069-a2de-08002b30309d}
{D6277990-4C6A-11CF-87-00AA0060F5BF}

Among them, the first child Jian decides whether to search for online printers (or even search for printers on the internet). If there is no shared printer on the network, the key can be deleted. The second child Jian decides whether to search for the specified scheduled task, which is the culprit of slow network neighbors and must be deleted.

3. Solve the problem that other Windows computers cannot access WINXP computers

After installing the Network, some netizens found that computers installed with the Win9x or winme operating system could not access the WINXP computer, or even the other party could not be seen in the network neighbors. If you encounter such problems, perform the following checks.

1. Check whether the Guest user is enabled

By default, the guest users in Win2000 and WINXP are disabled. To enable the Guest user, go to control panel/Administrative Tools/Computer Management/local users and groups/users to remove the tick before "Account Disabled. It is recommended that you do not set a password and select "the user cannot change the password" and "the password will never expire" to facilitate user access and reduce the possibility of troubles. The premise is that you must set the permissions and Group of the guest user, otherwise there will be endless troubles.

2. Check whether the Guest user is denied access to the local machine from the network

In WINXP, by default, the guest user is denied to access the local machine from the network. You can go to "Control Panel/Administrative Tools/local security policies/Local Policies/user permission assignment/Deny access to this computer from the network" and delete it if it includes a guest user. If you are creating a Win2000 Server or winxp.net server with a domain, you must also delete the Guest user in the corresponding project of the "Domain Security Policy". It should be noted that the deletion takes several minutes to take effect.