I am having the same problem as the original post and also tried the
restrictanonymous registry fix only I was not so lucky, it did not fix my
problem on that machine. While editing the registry, I did note that I had
two restrictanonymous keys in LSA, one was set at 0 and one at 1. I reset
both to 0, rebooted and confirmed the new settings yet still the machine
cannot access the workgroup.
Thus far I have:
1. Run the Help & Support Network tool; All test passed.
2. Reset the Node to Hybrid from unknown as indicated by the IPCONFIG report.
3. Looked for hiden fire walls, none found.
4. Renamed the machine and workgroup; access permitted on first reboot after
rename, denied on second and all other reboots.
5. Removed IPV6.
6. Confirmed NetBIOS over TCP/IP setting on WINS tab.
What's next? I am lost.
"Hans-Georg Michna" wrote:
> On Thu, 3 Nov 2005 10:58:41 +0100, Pvest wrote:
>
> >So now I'm wondering what I did when I changed this value from 1 to 0? Have
> >I open my PC's for the rest of the world so to say, or is it safe to run
> >like this?
>
> Pvest,
>
> nothing to worry, 0 is actually the default value for
> RestrictAnonymous.
>
> You can find a bit of background information in
> http://winhlp.com/wxnet.htm by not filling the form, but instead
> skipping down to the chapter on the RestrictAnonymous value. You
> can use the search function (Ctrl + F) of your browser to get
> there quickly, the page is big.
>
> Hans-Georg
>
> --
> No mail, please.
>