Windows Server

Scott · Guest

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!

Frances [MSFT] · Guest

Hello Scott,

Thanks for your post.

According to your scenario, you have a problem when you upgrade a BDC
without NT4Emulator. Please add NT4Emulator and NeutralizeNT4Emulator keys
before you run DCPROMO.

The following words are from KB298713 and KB284937, which indicate that it
is a must to use NeutralizeNT4Emulator to upgrade additional domain
controllers.

Note: Before you upgrade additional domain controllers, you must also add
the NeutralizeNT4Emulator entry to the
HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/Netlogon/Parameters
subkey and assign it a value of 1.

You can also use this procedure to upgrade a computer that is running
Windows NT 4.0 as a backup domain controller (BDC). If the BDC has already
been upgraded and has the NT4Emulator key, you must add the
NeutralizeNT4Emulator key to the BDC before you run DCPROMO.

As for when to remove the NT4emulator key, I suggest that you perform the
task when you have sufficient Windows 2003 domain controllers to handle the
authentication tasks from all the Windows 2000/XP clients. You can remove
the key by simply deleting the NT4Emulator value from the registry on each
domain controller.In fact,NT4Emulator is just a temporary workaround. We
strongly recommend turning it off when there are enough Windows 2000/2003
DCs. As you mention it is the last NT4.0 BDC, you may consider performing
the task.

If now you still do not have enough 2003 DCs, you can add the
NeutralizeNT4Emulator keys to the Windows 2000/XP clients to make them use
DNS not NetBIOS to authenticate with the 2003 DCs.

You can refer to the following articles for more information.

298713 How to prevent overloading on the first domain controller during
domain
http://support.microsoft.com/?id=298713

284937 Windows 2000-based clients connect only to the domain controller that
http://support.microsoft.com/?id=284937

If you have any further questions don't hesitate to get in touch!

Best regards,

Frances He

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

=====================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

	Windows Server Forum Index -> Migration	All times are GMT
Page 1 of 1