XP shared access is denied!

Windows XP shared access is denied. A complete solution (ANSWERS 1 and 2 are successfully tested) Answer 1:
My colleagues failed to access my machine through network neighbors over the past two days, and each time they were prompted to reject access. However, I added the 'Manage my network password' in the user configuration of my colleague's machine'

Then you can access it normally (using the Administrator account ). However, I have not made any changes to the access that can be normally accessed with guest. So I found some rejection information on the network.

Never access the article. The error message is as follows: XXXX 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 permission.
Access denied. Solution:
Soucat.com shows that the most common method is to change the classic access method to guest,
But the problem is solved, not the protocol. Generally, in Win2k/XP, you only need to install the default four protocols.
Microsoft Network Client
File and printer sharing in Microsoft Network
QoS packet scheduler
Interenet protocol TCP/IP
You can. You do not need to install other products.
Shared access report "no permission" SOLUTION
Access reports do not have permission solution:
1. Set network access mode to Classic mode.
2. Set a user account that prohibits access to the computer from the network (delete the guest group ).
3. Set restrictanonymous to 0.
4. Set the home or small office network as the second item "this computer is connected to the Internet through the gateway or other computers in the residential area"
5. Set the user account (added to the guest group) that allows access to the computer from the network. (this may cause the user name and password to be entered for each login, which is not recommended)
6. Set the password of the local administrator account. (it is not necessary. We recommend that you set the password)
Setting Method: start --> RUN gpedit. msc --> Computer Configuration --> Windows Settings --> Security Settings --> Local Policies -->
1. Security Options --> network access: sharing and security modes of Local Accounts

(Networkaccess: sharingandsecuritymodelforlocalaccounts) --> change to Classic mode.
2.: userrightsassignment --> denyaccesstothiscomputerfromthenetwork --> Delete

Guest group.
5. (not recommended) User Privilege assignment (userrightsassignment) --> Access this computer from the network (accessthiscomputerfromthenetwork) --> Add

Guest group.
Note: For network access, apply the "everyone" permission to anonymous users. You do not need to change it to "enable" (default: disabled ).
Account: A local account with a blank password can only log on to the console-Windows 2003 must be changed to "disabled", WINXP generally does not need to be changed (default

: Enabled ).

3. If you do not use the above method, Run regedit:

HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ LSA can set restrictanonymous in this sub-Jian to 0.
Note: The restrictanonymoussam in HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ LSA does not need to be changed to 0.

: 1. restrictanonymous registers settings that control any user's acquisition of local information. If restrictanonymous is set to 0 (default,

Any user can obtain information about the local machine through the network, including the user name, detailed account policy and shared name. Attackers can exploit this information to attack computers.

. With this information, attackers may be able to understand the system administrator account of the current computer, the path shared by the network, and the weak password. Modify the security level

Run regedit.exe to edit the Registry. Go to Zijian HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ LSA and set this Zijian.

The value of restrictanonymous is changed from insecure 0 to higher security level values 1 or 2. Note: If this security level is increased, the computer may be on the LAN.

Cannot be accessed.
2. When NetBIOS settings in wins in tip/IP advanced options are disabled, the LAN cannot be accessed.
3. If the virus is infected, it will not be able to access the LAN.
4. If the IP address is not set to a fixed IP address, the LAN function will be limited.

FAQs about network neighbors
I can see it on a network neighbor sometimes, but not on a single machine sometimes?
A: Microsoft Network customers must log on to view their network neighbors. If you do not log on but choose to cancel it when starting the system, the network neighbors will not be able to see any other machine.

You can click Start-> log out, log on again, and everything will work.
I can only see my own machine in my network neighbor?
A: Generally, your network card is not set, or the network cable is faulty.
My network neighbor can only see some machines, and cannot access OA or access the Internet?
A: Your machine Nic may be disabled. If you set your own IP address, you deserve it. You can only write an apology letter to the network administrator.
I have installed network components as required, but can't I access my network neighbors?
A: Consider the netbui protocol. Sometimes netbui may be installed falsely. Delete the netbui protocol, confirm to exit, and then reinstall the netbui Protocol once.

.
I can access other people's machines, but I cannot see myself on the network as a neighbor?
A: You may not have installed Microsoft files and printer sharing. Microsoft Network customers allow you to access others, share Microsoft files and printers, and share with others

Can access you.
Network neighbors still don't work?
A: protocols are mutual, just like a language. If it still doesn't work, consider the other party. Everything will work normally only if both parties have set up the correct agreement.

Answer 2:
In fact, you only need to set the computer network ID.
My computer, right-click, property, computer name. Network ID. After running the command, you can answer 3:
Try this:
(Save the text in the Registry file. Reg format and then import it)
Regedit4; Allow sharing and printer in the firewall
[HKEY_LOCAL_MACHINE \ SYSTEM \ controlset001 \ Services \ sharedaccess \ epoch]
"Epoch" = DWORD: 201700c3 [HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Services \ sharedaccess \ epoch]
"Epoch" = DWORD: 201700c3 [HKEY_LOCAL_MACHINE \ SYSTEM \ controlset001

\ Services \ sharedaccess \ Parameters \ firewallpolicy \ standardprofile \ globallyopenports \ list]
"139: TCP" = "139: TCP: localsubnet: enabled: @ xpsp2res. dll,-22004"
"445: TCP" = "445: TCP: localsubnet: enabled: @ xpsp2res. dll,-22005"
"137: UDP" = "137: UDP: localsubnet: enabled: @ xpsp2res. dll,-22001"
"138: UDP" = "138: UDP: localsubnet: enabled: @ xpsp2res. dll,-22002"
; Shared access allows empty password login (DWORD: 00000001 by default)
[HKEY_LOCAL_MACHINE \ SYSTEM \ controlset001 \ Control \ keyboard layouts \ e01f0404]
"Limitblankpassworduse" = DWORD: 00000000 [HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ LSA]
"Limitblankpassworduse" = DWORD: 00000000; Version 2.3 restrictions
[HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ LSA]
"Restrictanonymous" = DWORD: 00000000 Answer 4:
Try this: remove the default share, but do not disable null connection to Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ LSA]
"Restrictanonymous" = DWORD: 00000000
"Restrictanonymoussam" = DWORD: 00000001
"Forceguest" = DWORD: 00000000
"Limitblankpassworduse" = DWORD: 00000000

[HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Services \ LanmanServer \ Parameters]
"AutoShareServer" = DWORD: 00000001
[HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Services \ LanmanServer \ Parameters]
"Autoscaling wksautow.wks" = DWORD: 00000001

Restart the server. OK. All end users can access my server.