Windows 2000/2003 Domain Controller appears as BDC in NT Server Manager

After adding a Windows 2000 or 2003 domain controller (2kDC) to an NT 4 domain, the 2kDC should automatically become the new PDC for the domain and the existing NT PDC will automatically be demoted to a BDC.

After completing this migration the NT BDC may not synchronize correctly with the new PDC. As a result the 2kDC may appear as a BDC in Server Manager. New user accounts, password changes, etc. may not appear on the NT BDC indicating that the domain database is not synchronizing properly.

This can be caused by NetBIOS name resolution not working properly resulting in the NT BDC being unable to locate the PDC. To resolve:

- Ensure NetBIOS is enabled on the 2kDC. This is done on the Properties page of the network connection -> Advanced -> WINS tab.

- Ensure all DCs are referencing the same WINS servers and/or that all WINS servers are replicating properly. Check the WINS database for <1b> (Domain) and <1c> (Domain Controller) records. If these are not pointing to the 2kDC, delete them and run "nbtstat -RR" (note, arguments for nbtstat are case sensitive) to re-register the records. Query the records again from all DCs using "nbtstat -c" to ensure the new PDC name is being resolved correctly.

- Check the local LMHOSTS file (%WINDIR%\System32\drivers\etc\lmhosts) on each NT BDCs to ensure it contains no #PRE or #DOM references to the old NT PDC. Delete them if they exist.

Author: ASAK
Created: Oct 20 2005 (last modified Oct 21 2005)
Categories: Windows 2000 Server - Windows 2003 Server
TechByte #63

Warning: By visiting this site and/or by using any information contained herein, you agree to the Techbytes.ca terms of use.