Can't promote Windows 2012 Server in 2008 domain

I just joined a new Windows 2012 Server to a 2008 Domain.

I want to promote it to Domain Controller but the wizard gives me some errors.

I've investigated further and I get this error with adprep /rodcprep (with elevated privileges):

Adprep could not contact the Naming FSMO myserver.mydomain.com The Naming FSMO must be reachable for this operation proceed.

Error code: 0x3a

I am trying to do this logged as Domain Admin and I've checked Netdom Query FSMO on both the new server and the main server:

All the entries point to the same server: myserver.mydomain.com on both sides (new server and main)

The new server has not the DNS sever role and has as single dns server the main server.

What is wrong?

How can I fix this?

Thanks
LVL 1
ltpittAsked:
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.

Kamran MallikIT Technical EngineerCommented:
Are you trying to promote this DC as a Read Only Domain Controller as the command you have entered is to promote it to a Read only Domain Controller.
0
ltpittAuthor Commented:
Sorry I've now done on both Master server and new server:

adprep /domainprep

and on the master server I get: "All the domain level information are already updated" and on the new server: "Adprep could not contact the Naming FSMO myserver.mydomain.com The Naming FSMO must be reachable for this operation proceed.

Error code: 0x3a"
0
Kamran MallikIT Technical EngineerCommented:
Have you tried running dcpromo from the run menu instead. Domainprep I don't think is used to install a second DC on an existing domain. I usually use dcpromo which will run adprep anyway if needed.
0
ltpittAuthor Commented:
Solved!

It was just a firewall issue: damn me!

dcdiag /s:myservername

gave all the errors in the world and then I understood and fixed the pfsense firewall :)
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
ltpittAuthor Commented:
It was simply that
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 2012

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.