Discussion Locked

RestrictAnonymous Key

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I'm getting an error in Baseline Security Analyzer concerning the RestrictAnonymous Registry key either being set to zero or not existing at all. I can't seem to find much information on that key. Before I add/update that key, is there any reason I would NOT want to put it on a NT or W2K server?

7 replies

by joseph moore

Now, I keep RestrictAnonymous set to 2 on my Win2K boxes that are NOT part of a domain. I like the security of workgroup-member machines with RA set to 2.
I even do that with my home computers on dial-up connections.

You need to look at how RA works and see if it is right for your network. If you have NT & 2K machines with NO trust going on, then I would set it to 1 on all machines, so the NT boxes won't have problems with the 2K boxes.

by joseph moore

Lastly, please remember that RA=1 has a problem. You can bypass it to still get a user account enumeration using tools like NBTENUM and/or USERINFO. RA=1 has a problem that programmers have figured out how to bypass it. On Win2K, RA=2 has not been vulnerable to this problem.
Just something to keep in mind.
But, if you can turn on RA at all, I highly suggest you do!

by ireilly

Perfect! The KB articles coupled with your experience is exactly the help I needed! Thanks!

This discussion is closed to new replies.