NT4Emulator Registry Key, Do's and Dont's

From: Scott (Scott_at_discussions.microsoft.com)
Date: 01/20/05 

Date: Thu, 20 Jan 2005 09:57:06 -0800

I upgraded an NT4.0 PDC to W2K3 and AD, which installed DNS as well.
Before I performed the in-place upgrade of the NT4.0 PDC I added the
NT4Emulator registry key, as outlined in KB298713.
I now have a second server that I performed an in-place NT4.0 -> W2K3
upgrade on. I DID NOT add the NT4Emulator key on this server prior to
install, as this was my last NT4.0 BDC. The problem lies in that this server
cannot contact the DC to complete the install. I get to the where the wizard
asks wether I want to make this an Additional Domain Controller, or Member
Server and then it cannot locate the DC to authenticate. The error states:

"DNS was successfully queried for the service location (SRV) resource
record used to locate a domain controller for domain sliedrecht.lan:

The query was for the SRV record for
_ldap._tcp.dc._msdcs.domain.com

The following domain controllers were identified by the query:

computer.domain.com

Common causes of this error include:

- Host (A) records that map the name of the domain controller to its
IP addresses are missing or contain incorrect addresses.

- Domain controllers registered in DNS are not connected to the
network or are not running.

For information about correcting this problem, click Help."

Could this be attributed to the NT4Emulator key still being set on the DC
performing as the DNS server?
At what point should I turn this off?
I have been concerned about removing this key, because almost all of the XP
clients are still using the NEtBIOS domain name, and haven't changed to the
new DNS domain name.

Any help would be appreciated!

Relevant Pages

  • Issues migrating SBS 2003 domain to Server 2008 Standard
    ... We are stuck migrating our SBS 2003 domain to Server 2008. ... Fatal Error:DsGetDcName (SRV-EXCH) call failed, ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)
  • Re: Issues migrating SBS 2003 domain to Server 2008 Standard
    ... Since you have migrated to standard server 2008 you would be better served posting in a Standard server NG. ... Event String: ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 and Replication Errors with Remote DC
    ... alpha server as soon as you can to get things going. ... A simple DNS replication test is to create a host record in the SBS server ... Domain Controller Diagnosis ...
    (microsoft.public.windows.server.sbs)
  • Re: Issues migrating SBS 2003 domain to Server 2008 Standard
    ... One thought, when you introduced the Windows Server 2008 and before making them DC's, did you extend the schema on the SBS 2003 server? ... Event String: ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)
  • Re: Big trouble with DC in China
    ... > Since then, this server has so may errors in the event logs (KCC, ... > DNS, FRS) that I wouldnt know where to start. ... > Source domain controller address: ...
    (microsoft.public.windows.server.active_directory)