Forum Discussion
Error joining Azure VM AD to on_prem AD through VPN
Hi Kurt,
Having said you created AD Sites and services. Did you put the Azure AD01 into another site you created on-prem.?
Hi Kurt,
can you please check if you able to Telnet 53 port and 137 Port?
Best
Sunit Patil
However, I turned off NetBIOS in the NIC on DC01 per some instructions I read.
Let me turn it back on and see if that resolves the telnet to 137 issue.
Hi Kurt,
Having said you created AD Sites and services. Did you put the Azure AD01 into another site you created on-prem.?
Well, yes. About that. A couple things. First, I DID create a Site, I assigned the appropriate subnet, but I did NOT assign the server. Because there was no server called AD01 joined to the domain at the time I created the site.
Second, I did NOT try to join AD01 to the domain before I tried to install ADDS and DCPROMO it up. Why not? Dunno, just didn't. So, I blew away that server and re-created it. I joined it tothe domain first (it worked), then I ran ADDS, then I DCPROMO'd it up, and BOOM! New AD DC and DNS Server. I added the DNS Server address hosted in Azure to the Virtual Network, rebooted both servers to get the new DNS adddress listed in the NICs, then... couldn't replicate from Azure to on_prem.
THEN I added the AD01 server to the Site I created in AD Sites and Services. At which point everything replicated and I became a happy camper. So, excellent point, JIDE, thank you.
While I fixed this issue myself, I will give you both credit as both of you addressed 2 separate but valid issues you cna have while trying to join across a VPN.
Thank you both for responding.
Kurt
Apparently I cannot have TWO best answers. Ah well.
