An Active directory domain controller for the domain could not be contacted

I am trying to add a second domain controller to a domain using the Active Directory Installation Wizard.  
I am getting the following error.

An Active directory domain controller for the domain - could not be contacted
Kevin RobinsonPrivate VB.NET ContractorAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Seelan NaidooMicrosoft Systems AdminCommented:
Have u specified a static IP on the 2nd DC ?

Are they on the same subnet ?

Have you disabled the Windows based firewall for the NIC ?

Can u ping your 1st DC from the 2nd DC, and vice versa ?

Are you logged into the 2nd DC, with a user account that it a member of the Domain Admins group, when attempting DCPROMO
Kevin RobinsonPrivate VB.NET ContractorAuthor Commented:

Seelan NaidooMicrosoft Systems AdminCommented:
It could be DNS problems might be preventing name resolution for the 1st DC.

run the following from a command prompt

netdiag /test:dsgetdc /d:DomainName /v

If any of the tests fail, follow the recommendations provided in the output.


or it could be that your sysvol isnt shared, so you have share the SYSVOL directory.

To verify that the SYSVOL directory is shared out, use the net share command to see if the SYSVOL share is showing.

By default, the SYSVOL share is located in the following folder: %SystemRoot%\Sysvol\Sysvol

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Kevin RobinsonPrivate VB.NET ContractorAuthor Commented:
i have tried to run netdiag on the first domain controller to make sure DNS is installed here first.  I am getting an error

"the Dns entries for this DC are not registered correctly"

No DNS servers have the DNS records for this DC Registered
Kevin RobinsonPrivate VB.NET ContractorAuthor Commented:
Fixed it

Deleted the DNS zone on the first DC and recreated it.  

Then I ran ipconfig /registerdns.

The new server is now connecting and setting up active driectory.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.