Problems with RestrictAnonymous Key

  • Thread starter Thread starter Josh
  • Start date Start date
J

Josh

I have 2 W2K domains which are trusting each other.
Currently both have the RestrictAnonymous key set to 0.
When I change the DomainSecurity Policy on Domain_1 to "1
Do not allow enumeration of SAM accounts and names" I can
no longer log on interactively to a Domain_1 machine using
Domain_2 credentials.

I've already referrenced KB articles:
246261
296405
296403

From what I can tell changing the setting to 1 should have
no adverse effects between 2 W2K domains. What am I
missing?
Thanks
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

"restrictanonymous" setting problem..... 3
Disabling Null sessions on W2K machines from Win2003 DCs 1
RestrictAnonymous Problem! 2
RestrictAnonymous issue 4
Null Session Fix not working on Domain Controllers 5
restrictanonymous value wont set to 0 6
RestrictAnonymous Registry Value in Windows 2000 1
Trouble sharing files...... 2

Back
Top