Windows Forum

Ask something
Discussion Locked

Additional Domain Controller fails.

0 helpful
4 replies

by pattownsend 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I'm trying to add an additional domain controller for an existing domain, as a backup. When I try to install active directory to my new server I get the message: 'The Domain "MDPLASTIC.com" is not an Active Directory domain, or an Active Directory domain controller for the domain could not be contacted.'

The old server has this server in the active directory. I can ping each server from the other.
I mapped a drive on the new server to a folder on the old server.

What's the problem
Thanks, Pat

4 replies

by timwalsh

This sounds very much like a DNS issue.

Do you host your own DNS or is it hosted by an ISP? If it is being hosted by an ISP, that is your problem. Most ISPs will not accept the necessary DNS entries to make AD fully functional. Without these entries AD will never operate correctly.

If you are hosting your own DNS, (NORMALLY) AD will add an additional four folders (labeled _msdcs, _sites, _tcp, and _udp), with numerous entries in each, into your DNS table under the forward lookup zone.Without these folders correctly populated, there is no way to locate Active Directory Domain Controllers.

by pattownsend

I checked and the folders are present on the current AD server. The current server is running DHCP and DNS. I did have DNS server addresses setup for our ISP under the TCP/IP setup to allow for Internet access. I removed them from both servers. The problem remains the same.
Thanks, Pat

by everyoneall

I had similar problem when I upgrade a NT PDC to AD DC.

First, ensure you got the "Dynamic Update" on the DNS set to Yes, do a "ipconfig /registerdns", restart the DNS service. Check if a list of SRV records are created under the AD integrated zone, in DNS MMC. If you start seeing the SRV records, you can re-add the DC and it shld be ok.

However, if the SRV records are still not there. Also, confirm if your fully-qualified domain name in the Computer Name matches the Windows 2000 Domain Name. If it doesn't, it may be a bigger problem which I had earlier.

To further confirm, check out your Event Log to see if there's a Error No 5788 / 5789. If yes, check out this TechNote Q262376. It says there's a known Win2K bug, and you suppose to upgrade WinNT to Win2K OS, update with min SP1/2, then do the DCPromo to AD DC.

Is this the scenerio?
Regards.

by pattownsend

I checked DNS for dynamic update, it has 'only secure updates'. Can't change it to yes, get 'Data on the primary zone failed to set. Access denied.' I think being a beginner I have more than one setting wrong.
Thanks, Pat

This discussion is closed to new replies.