When promoting AD server in the azure getting an error

Question

When promoting AD server in the azure getting an error

arjuna_svr 101

The scenario:

DC01 - hosted on premises. Is the first AD server of a domain named: testlab.local
DC02 - hosted on Azure IAAS server. Is joined in the domain testlab.local

When tryting to promote DC02 I am getting the following error message: "Error getting the list of sites from the target enviroment: the user name or password is incorrect"
I am logging in with the right password and username (testlab\administrator).
Ping is succefull to domain and dc01
I am using a site to site vpn to have a connection between azure and on prem.
dcdiag /s:testlab.local gives the following message on DC02:

"Directory Server Diagnosis

Performing initial setup:
[cloudcomputing.local] LDAP bind failed with error 1326,
The user name or password is incorrect.."

dcdiag on DC01 is succesfull. Firewall settings are all open at the router, DC01, DC02 and Azure NSG. Its only open for the vpn tunnel.

Can someone please give me some guidance to troubleshoot this issue?

0 comments

Answer accepted by question author

Anonymous

Might work through these ones. The log files may provide something useful.
https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/deploy/troubleshooting-domain-controller-deployment
https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-2000-server/cc959340(v=technet.10)?redirectedfrom=MSDN

--please don't forget to upvote and Accept as answer if the reply is helpful--

Anonymous

2022-10-18T12:47:27.233+00:00

Just checking if there's any progress or updates?

--please don't forget to upvote and Accept as answer if the reply is helpful--

4 additional answers

Your answer

Anonymous

2022-10-18T12:47:27.233+00:00

Just checking if there's any progress or updates?

--please don't forget to upvote and Accept as answer if the reply is helpful--

Answer 1

arjuna_svr 101

So i fixed the issue with authenticating with administrator@Teddy .local instead of TESTLAB\Administrator.

Anonymous

2022-10-22T19:30:31.897+00:00

Glad to hear, please don't forget to close up the thread by
Doug Tucker 6 Reputation points

2023-08-21T22:05:48.39+00:00

Yes. Also worked for me logging in with user@domain.local
cs 5 Reputation points

2023-11-01T04:44:04.6633333+00:00

Thanks, this did the trick for me
William Menant 11 Reputation points

2024-01-03T10:08:52.73+00:00

Helped a lot, thanks!
Ciprian Lazar 5 Reputation points

2024-02-07T09:16:22.0066667+00:00

This trick also worked for me, also (admin@domain.sufix) So, we should try to avoid netbios naming format from Azure? :D
jpcapone 1,791 Reputation points

2024-09-23T17:22:17.73+00:00

Still helping people!
Akin Tosh 0 Reputation points

2025-03-28T07:45:08.4366667+00:00

Thanks !
hp9 30 Reputation points

2025-08-21T09:04:54.57+00:00

Just had the exact same issue trying to promote a 2025 server to a domain controller. Using <username>@<domainname> works but <domainname>\<username> gives an error. This has nothing to do with group membership so ignore all the posts that reference that.

Answer 2

hp9 30

Just had the exact same issue trying to promote a 2025 server to a domain controller. Using <username>@<domainname> works but <domainname>\<username> gives an error. This has nothing to do with group membership so ignore all the posts that reference that.

Lucas GONZALEZ | ASSYMBA - IT's all you need 0 Reputation points

2025-09-30T08:22:04.4433333+00:00

Thanks !

Answer 3

arjuna_svr 101

Hi DSPatrick,

I did read the microsoft learn sites u send me yesterday. I will try to walk trough them in the evening. I will give u an update when I did that.

0 comments

Answer 4

Anonymous

Might check the account has Domain Admins group membership (or higher) or try with another account.

arjuna_svr 101 Reputation points

2022-10-17T21:24:42.657+00:00

Already tried that. I used the administrator account and also a copy of the administrator account to verify myself