Workgroup cannot be accessed. You may not have the permission to use network resources. Please contact the administrator of this server to check whether you have access permissions.

Solution to "Network neighbors" inability to access each other
To sum up, there are basically the following:
1. No shared resource/shared service is enabled.
Symptom: You can ping the computer but cannot access Shared resources. After you view "local sharing" in "Computer Management", the "no Server Service started" error dialog box is displayed.
Solution: Start the Server Service in Control Panel-Administrative Tools-service. Set "Start type" to "automatic ".
2. Incorrect IP settings.
Symptoms: The two hosts cannot be pinged to each other. The twisted pair wires used for connection are tested and no firewall is installed.
Solution: Check whether the IP addresses of the two computers are in the same network segment, and whether the Sub-masks are the same.
3. The default settings of WINXP are incorrect.
Symptom: you cannot access another WINXP machine from Win98/2000/2003.
Solution: Enable the Guest account in "User Account" in "Control Panel. Then, enter secpol. MSC in the run to start the Local Security Policy ".
Local policy-> User Rights Assignment, open "access to this computer from the network", add a guest account
Local policy-> security option, disable "account: Local Accounts with blank passwords can only log on to the console ".
In addition, you may also encounter another situation: when accessing XP, the username in the logon dialog box is gray, always a guest user, and cannot enter other user accounts.
Solution: local policy-> Security Options-> "Network Access: sharing and security mode of the Local Account", changed to "classic-Local User Authentication"
4. The system vulnerability FIX software modifies the security policy.
Symptom: the computer of the peer can be seen in "Network neighbors", but the system prompts "no permission to access the network" when accessing the sharing"
Solution: Enter secpol. MSC in the "Start" menu to start "Local Security Policy", "Local Policy"> "User Privilege allocation", "Deny access to this computer from the network", and delete the Guest user.
5. Firewall Rules.
Symptoms: the firewall (including the firewall built in WINXP) is installed, and the ping fails, when accessing shared resources, the system prompts "XXX cannot be accessed", "you may not have permission to use network resources", and "contact the administrator of this server to check whether you have access permissions ", similar prompts such as "network path not found.
Solution: Stop the firewall or add LAN access rules.
Firewall that comes with WINXP: Open Control Panel-> network and Internet connection-> Windows Firewall-> exceptions, and select "file and printer sharing ".
6. Mutual access between Win2000/XP and Win98
Symptom: ping command can pass, but mutual access cannot be achieved in "Network neighbors.
Solution: In the Win2000/XP system, choose Control Panel> Management Tools> Computer Management> local users and groups> users. Right-click the Guest account and choose Properties, cancel "Account Disabled" in general items"
(Note: In addition, the "file and printer sharing" function may be disabled in the Win98 system. Enable it again .)
Guest user password. Have you set it?
It is rumored that the guest users in Windows XP have severe security vulnerabilities, and we cannot set a password for the guest users in the "user account. However, you can enter:
Rundll32 netplwiz. dll, usersrundll will open the "User Account" page, which is not the "User Account" we usually see in the "control panel ". On the "user" tab of "User Account", select the Guest user and click "Reset Password" below ". Now, set a password for your guest user. By the way, mark the one above.

1. improper access permission settings
Windows NT/2000/XP/2003 systems support NTFS file systems. using NTFS can effectively enhance the security of the system. However, when the ACL (Access Control List) is not set, this will also cause the user to be unable to normally access the resources shared by the local machine, and the message "insufficient Permissions" appears.
2. Improper account and policy settings
In Windows workgroup environments, users generally need to use the Guest account to access shared resources. However, for the sake of system security, the Guest account of the system is disabled. In addition, in Windows 2000/XP/2003, by default, the Group Policy does not allow the Guest account to access the computer from the network. As a result, other users cannot access the shared resources on the machine and receive a message "Access Denied.
3. Improper network firewall settings
To enhance the security of the local machine and prevent illegal intrusion, you have installed a network firewall. However, improper configuration of the network firewall also causes other users to be unable to access the shared resources on the local machine. The message "Access Denied" is displayed because the firewall disables the NetBIOS port required to share resources.

solution
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. 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, you only need to add the everyone account and grant "read" and "list folder directories" permissions, this avoids adding and specifying each user's access account one by one. This method is applicable to Windows 2000/XP/2003 systems that use the NTFS file system.

4. Change the Network Access Mode

XP processes all users logged on from the network according to the Guest account by default. Therefore, even if the Administrator logs on from the network, the Administrator only has the guest permission, try to change the network access mode. Open the Group Policy Editor, select "Computer Configuration> Windows Settings> Security Settings> Local Policies> Security Options", and double-click the "Network Access: sharing and security modes of Local Accounts" policy, change "guest-Local User-initiated identity verification" to "classic: Local User Authentication" by default ".

In this way, even if you do not enable Guest, you can enter your local account and password to log on to the computer you want to access, the local account and password are your accounts and passwords in the computer you want to access. If you need an account and password when accessing the network, you can enter the account and password in the computer you want to access to log on.

If you do not change the access mode, you may not be able to enter the user name and password, // computername/guest is unavailable. Even if the password is empty, you cannot click confirm to log on without enabling guest. In Classic mode, you can enter the user name and password to log on to your computer.

5. 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.

6. A noteworthy question

We may also encounter another problem, that is, when the user's password is empty, the access will be rejected even if you have made all the above changes and still cannot log on. This is because the policy "Account: A local account with a blank password can only log on to the console" in the system "Security Options" is enabled by default, according to the Denial-of-priority principle in Windows XP security policy, users with blank passwords are prohibited from accessing Windows XP computers over the network. We only need to disable this policy to solve the problem. In the security options, find the "allow console logon only for local accounts with blank passwords" option and disable it. Otherwise, you cannot log on even if you have enabled guest and changed it to the classic mode. After the above changes, you can access them. You can try to select a method that suits you. Next we will add some other problems that may occur.

7. The network neighbor cannot see the computer

You may not often see the computer you want to access in the network neighbor unless you know the computer name or IP address, by searching or directly entering // computername or // ip. Follow these steps to start the "Computer Browser" service. "Computer Browser Service" maintains a computer update list on the network and provides this list to the computer designated as the browser. If the service is stopped, the list is neither updated nor maintained.

137/udp -- NetBIOS name server. The NetBIOS Name Server (NBNS) protocol is part of the NetBIOS (netbt) protocol family on TCP/IP, it provides the Host Name and Address ing method on the network accessed Based on NetBIOS name.

138/udp -- NetBIOS datagram. NetBIOS datagram is part of the NetBIOS (netbt) protocol family on TCP/IP. It is used for network login and browsing.

139/tcp -- NetBIOS session service. NetBIOS session service is part of the NetBIOS (netbt) protocol family on TCP/IP. It is used for Server Message Block (SMB), file sharing, and printing. Set the firewall to enable the corresponding port. Generally, you only need to allow the folder and printer sharing service in the firewall.

8. About the Sharing Mode

By default, shared XP only grants the guest permission or allows users to change "my files ". In Windows 2000, you can easily set the shared attributes of a folder. You only need to right-click the folder and select Properties to view the shared settings tag. In Windows XP, folder sharing is complicated, and users cannot see the sharing setting label through the above operations. The specific modification method is as follows: Open "Tools" in "My Computer", select "folder properties", and bring up the "View" tag, scroll to the bottom of the "Advanced Settings" section to cancel the selection before "simple file sharing (recommended, in addition, if the option bar contains the "Mickey Mouse" item, you can also cancel it. In this way, you can easily modify the folder attributes like Windows 2000.

9. slow response to access by network neighbors

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:

Turn off the 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.

Summary

Inaccessible mainly because XP does not enable Guest by default, and even if guest is enabled, XP does not allow guest to access the computer from the network by default. There is also a noteworthy problem. I believe that some places that do not consider security or computer companies give people blank system passwords, but this is not allowed to log on. If you have tried the above methods, I believe there will be no more problems.

These situations have always occurred recently. Computers in the same domain have been accessed by others, but they cannot access others, but he still accessed some other computers. He can ping other computers, but cannot find the IP address. He hasn't opened a firewall or something like that. What is the problem? Please give me some advice and wait for ing...
________________________________________
Basic conditions for mutual access between Windows Network neighbors:
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
First, the question about why 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 if you do not have the permission to use the network, this means that I am not quite clear !! The Guest account is also enabled! The firewall of WINXP is also disabled, and the IP address is OK !! I hope you can analyze it !! Thank you very much!
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 use a firewall vulnerability like rising, it will modify the policy of "rejecting access to this computer from the network" and modify the policy as follows:
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.
Mutual access between Win2000/XP and Win98
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 a client's network neighbor accesses the server, the "transaction processing is not set on the server" error 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.
Method 3: Install a wooden marker to prevent viruses.
Disagree with the above points.
It is not a good method to enable Guest. Microsoft's default settings for guest in XP and 2003 are not superfluous.
There are many access problems for network peers. The following are some examples:
1. Unable to obtain the list of network neighbor hosts
In addition to local problems, check whether the local machine can access the browser host or domain controller.
There are also the following reasons: browser problems (no use of hosts such as ad and 98) and Domain Controller GC problems (use of AD ).
This is the case if browser is generated in the LAN or the browser service is disabled on the host.
If the LAN uses a vswitch that restricts broadcast, the WINS service should be used.
You can use NBTSTAT to query browser problems, but it is better to use the browstat tool on the Win2k installation disc, use browstat sta to display the browser host, and use elect to force browser re-election.
For ad, you can use NSLookup to query
2. Only some hosts are listed in the network neighbor list, or the host list is incorrect.
Possible causes include browser changing, some hosts are hidden (for example, Registry "LanmanServer" Parameters "hidden = 1), and some hosts cannot be broadcast (switch restrictions, etc ).
For the solution, refer to the above.
3. You can browse the host, but the host cannot be accessed (without passing through the road ).
If wins or DNS is used, check whether their resolution is correct. If the content of the local lmhost and hosts files is correct, clear the local NetBIOS cache or ARP cache. Can I use an IP address for access.
4. Insufficient host browsing permissions, or no user name or password entered at all.
Check whether the local login account and password are owned by the host account of the other party, whether the other party has enabled account locking, and whether an account has been connected to the resource (even if it has not been accessed, it is also possible), yes
Use Net use "" ip "IPC $/d to delete any account connection and then access it. For example, use net use" "ip" IPC $ "pass"/User: "name"