Hello everyone. Im having a problem with My network places in Windows XP. One computer on the network can not be seen by any other of the computers. The weird thing is this computer can see and access all the other computer pcs on the network. Things were working fine until I tried to install Windoes vista but during install it had an error and didnt finish the install. It didn'g do anything to my windows xp as I just cancelled the installation. Just thought I would mention that. I did a spyware check also but came clean. Any thoughts?
![[H]ard|Forum](/styles/hardforum/xenforo/logo_dark.png){kind=logo}
Navigation
Install the app
How to install the app on iOS
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
More options
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
"My Network Places" Problem
- Thread starter qtqc
- Start date
what do you mean?
On that PC, Start > Run > cmd > Ipconfig. Note the IP address.
On another PC, Start > Run > enter the IP address.
I tried adding them manually on another computer. it says it adds the directory succesfull but I still cant see the folder
Even on the computer which is not communicating correctly, my shared folders are not comming up in "my network places" automatically. I added them manually, but its weird because when you add a folder for sharing it should come up automatically.
Even on the computer which is not communicating correctly, my shared folders are not comming up in "my network places" automatically. I added them manually, but its weird because when you add a folder for sharing it should come up automatically.
Well I found the problem. I will post just incase anyone ever has the same problem
The RestrictAnonymous registry value:
You have both the following symptoms:
You can ping the computer by IP and by name.
When you type on another computer, replacing computername with the name of the inaccessible computer:
net view \\computername
you get one of the various "Error 5" error messages, like "System error 5 has occurred. Access is denied" or "Error 5: You do not currently have access to this file. ..." (However, other commands, like
net use Z: \\computername\sharename
or typing the full network path into Windows Explorer may work.)
This can be caused by a registry setting named RestrictAnonymous. Go to the computer which you cannot access, start a registry editor and change the following registry value.
HKEY_LOCAL_MACHINE
\SYSTEM
\CurrentControlSet
\Control
\Lsa
Value name: RestrictAnonymous
Value type: DWORD
If the value is 1 or even 2, change it to 0, reboot and retest. If the problem is solved, leave the value at zero. If not, you can change it back if you like.
Check immediately afterwards and again after a reboot, whether the value changes back to non-zero on its own. If that happens, then you have to find the culprit, which can be spyware, a worm, or a badly designed security program. In this case this procedure most likely solved your problem, but then the bad software stepped back in and recreated the problem.
The RestrictAnonymous registry value:
You have both the following symptoms:
You can ping the computer by IP and by name.
When you type on another computer, replacing computername with the name of the inaccessible computer:
net view \\computername
you get one of the various "Error 5" error messages, like "System error 5 has occurred. Access is denied" or "Error 5: You do not currently have access to this file. ..." (However, other commands, like
net use Z: \\computername\sharename
or typing the full network path into Windows Explorer may work.)
This can be caused by a registry setting named RestrictAnonymous. Go to the computer which you cannot access, start a registry editor and change the following registry value.
HKEY_LOCAL_MACHINE
\SYSTEM
\CurrentControlSet
\Control
\Lsa
Value name: RestrictAnonymous
Value type: DWORD
If the value is 1 or even 2, change it to 0, reboot and retest. If the problem is solved, leave the value at zero. If not, you can change it back if you like.
Check immediately afterwards and again after a reboot, whether the value changes back to non-zero on its own. If that happens, then you have to find the culprit, which can be spyware, a worm, or a badly designed security program. In this case this procedure most likely solved your problem, but then the bad software stepped back in and recreated the problem.