Having Issues Promoting a New 2025 DC in a 2016 Domain

0
35
Asked By TechnoGnome77 On

Hey everyone! I'm having a tough time promoting one of my new 2025 domain controllers in my Server 2016 domain. I previously had a 2012 R2 domain with a 2012 R2 DC and a 2016 DC, which I've demoted and removed cleanly to prepare for the new servers. I've successfully raised the domain and forest to 2016, but when I attempt to promote the new 2025 server, I keep getting an error saying "encountered an error contacting domain . The user name or password is incorrect." I'm certain the credentials I'm using are correct since they belong to a domain admin and enterprise admin. DCDiag shows that all tests pass and all ports are open. I've even tested connecting another member server to the domain successfully, but the promotion still fails. Has anyone experienced this issue or have any specific troubleshooting steps I could try?

5 Answers

Answered By ServerWhisperer42 On

We decided to keep our 2019 DCs due to the known problems with 2025 DCs. Can't risk stability for the sake of a newer version! But I get that you want to move forward with your setup.

Answered By HappyITGuru On

Honestly, I was in the same boat! I was using domainusername and switched to domain.localusername which solved the problem for me. Sometimes it’s just those little things that trip us up! Glad you’re moving forward now!

Answered By AdminNinja99 On

A lot of folks have mentioned that there are significant issues with 2025 DCs right now, so maybe consider sticking with what you have for a bit. Just to be sure, did you double-check AD Sites to see if you actually have a site configured with your subnet? It might seem basic, but you'd be surprised how many small organizations overlook this. Good luck!

Answered By CuriousCoder21 On

Have you transferred the FSMO roles to the 2016 DC? It’s crucial to make sure that step is completed. You might want to check it with 'netdom query fsmo'. Also, are you attempting to promote the 2025 server directly? It might be worth joining it to the domain first before promoting.

Answered By NetworkWizard10 On

Glad you figured it out, using FQDN credentials can really make a difference. Also, don’t forget, are you running the server admin center as an admin? It can sometimes cause issues if not!

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.