AMC wrote:
> Here's my problem.
> Four PC's, two hard wired, two wireless connected via a Linksys router.
> All
> running XP.
> The two woreless connections are fine. One hard wired connection is fine.
> The problem is with the second hard wired PC ( call it PC "A" ).
>
Copy and pasting this, it has come to the rescue many times..........
This is in some cases 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.
In this case you can try to disable running programs and services and retry
until you find out which one is responsible. Or you could try to download
and run RegMon from
www.sysinternals.com. In RegMon set a filter for the
registry value in question (or wade through all the registry accesses), set
the problem value to zero, then observe which program accesses it and
changes it back to 1. Locate that program and uninstall it. And please don't
forget to report the bad program here, so we can get a list of offending
programs.
Two known Trojans that change this value (and also some network access
policies) call themselves mcafee32.exe and msconfg.exe, trying to pose as
the antivirus program of that name or as a Microsoft configuration program
module.
2005-05-17 - Peter Kavanagh wrote: Offending malware was either Gaobot.EDJ
variant or Wupd spware in file sdasd.exe, both of which had to be removed.
2005-11-18 - Justin T wrote: I found that System Mechanics Pro 6 changes
these settings to 2 as it thinks it is a security flaw.
Apart from this advice, this web page cannot help you any further, so you
can stop reading at this point. You have to remove the bad software first.
Background: RestrictAnonymous controls whether null sessions, sessions that
work without any authentication and use the permissions of the groups
Everyone and NETWORK, are allowed (value 0) or disallowed (value 1). The
value 2 is obsolete for Windows XP.
Don't mistake this for the value named restrictanonymoussam, which controls
null session SAM account name listings.
For some time I asked for the results of this procedure and recorded an 80%
success rate in 2005.