Configuring Server 2012 R2 as new DC in a Server 2003 R2 environment

Good afternoon,

I am trying to promote a new server that we just received as a domain controller to an existing domain.  The new server(HPDSERVER1) is running Windows Server 2012R2 while the old DC(HPDSERVER) is running Windows Server 2003R2.  The new server,HPDSERVER1,  is configured with a static ip and dns setting is configured as the ip of the old DC(HPDSERVER).  From reading the articles on Microsoft's website, it sounds like we no longer need to run adprep.exe on the old server any longer.  It seems as though when you are going through the Active Directory Domain Services Configuration Wizard it should now take care of all of this automatically.  The problem arises when I try to add this new server as a domain controller to the existing domain.  I specify the domain information(HPD.local) or (HPD), and when I click Next I consistently get an error message stating "An Active Directory domain controller for the domain "HPD.local" could not be contacted.  Ensuree that you supplied the correct DNS domain name.  I have no problems pinging the old DC with either the hostname or ip address.  I have done a nslookup on the new server for hpd.local and HPDSERVER and they both return with a proper ip address of the old server, which is currently hosting DNS.  I can also join the new server to the domain.  What am I missing?
IMG-0746.JPG
LVL 1
Steven BlackAsked:
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.

Will SzymkowskiSenior Solution ArchitectCommented:
Couple of things below...
- if this was a DC from another domain, you will need to remove the machine from the old domain and add it to a new domain (re-imaging the OS would be most preferred)
- you need to ensure that this server is pointing to a DC that is already online for DNS
- make sure no firewall rules are blocking communication
- make sure that your 2003 domain environment is at 2003 Forest/Domain functional level
- make sure that your account that you are using to promote this first 2012 DC is part of domain admins, schema admins and enterprise admins

Thats is all that is required.

Will.
0

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
Steven BlackAuthor Commented:
We found out that the primary domain controller was failing, and would not allow the connection.
0
Will SzymkowskiSenior Solution ArchitectCommented:
Glad it is working now.

Will.
0
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.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.