Tip

Stop Win2k clients from "running home"

In a large environment that may have domain controllers spread out across a WAN, you do not want to begin your Win2k implementation at your main site and have any of your W2k clients "run home" to this DC. It will overwhelm the DC and could cause login scripts to break and slow access times.

The fix is to add a registry hack that will cause the DC to look like an NT 4.0 PDC, and therefore your Win2k clients will authenticate with their normal or closest DC. This will cause one issue in regards to bringing up more Win2k DCs into your domain. You will get an error that there are no Active Directory domains. The second registry hack will solve this problem. You will need Service Pack 2 for both of these.

First registry hack:

HKLMSystemCurrentControlSetServicesNetlogonParameters

Value: NT4Emulator
Type: REG_DWORD
Data: 0x1

Second registry hack:

HKLMSystemCurrentControlSetServicesNetlogonParameters

Value: NeutralizeNT4Emulator
Type: REG_DWORD
Data: 0x1


This was first published in October 2001

Join the conversationComment

Share
Comments

    Results

    Contribute to the conversation

    All fields are required. Comments will appear at the bottom of the article.

    Disclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.

    Back to top