Azure VM Windows Server 2022 Domain Joining Issue

Hi Salamat_Shah​ 

Since basic connectivity tests (ping, nslookup, and telnet) are working, the issue may be related to authentication or Active Directory communication rather than general network connectivity.

Ensure the VM is using the Active Directory DNS servers instead of Azure's default DNS. Also verify that RPC, LDAP, Kerberos, and SMB ports are allowed through Azure Firewall and any on-premises firewalls. Confirm that the VM's system time is synchronized with the domain controllers, as Kerberos authentication can fail if there is a time difference. Finally, review the System and NetSetup event logs on the VM for more detailed error messages.

This error is commonly caused by blocked RPC traffic or DNS misconfiguration, even when basic connectivity tests are successful. Does the issue occur when trying to join any domain controller, or only a specific one?

For domain join, successful ping/telnet is useful but not enough. The usual failure point is DNS/service discovery or one of the AD ports being blocked asymmetrically.

I would check these in order:

1. On the Azure VM, confirm DNS points to the domain DNS/DCs, not Azure-provided DNS, and run `nltest /dsgetdc:<domain>` plus `nslookup -type=SRV _ldap._tcp.dc._msdcs.<domain>`.

2. Use Network Watcher Connection troubleshoot from the VM to a domain controller on TCP 53, 88, 135, 389, 445, 464, 636 if used, 3268 if GC is needed, and the dynamic RPC range.

3. Check effective routes on the VM NIC. Make sure traffic to the DCs is not forced through a firewall path that SNATs or drops dynamic RPC.

4. Check effective NSG rules on both subnet and NIC.

5. On the DC/firewall side, verify the Azure VM subnet is allowed and that return traffic follows the expected route.

The "network path was not found" style error is often DNS/DC locator or SMB/RPC reachability, not just basic ICMP reachability.

Useful docs:

https://learn.microsoft.com/azure/network-watcher/connection-troubleshoot-overview

https://learn.microsoft.com/troubleshoot/azure/virtual-network/virtual-network-troubleshoot-connectivity-problem-between-vms

Seems like a DNS or connectivity issue. Could you also resolve AD-domain using nslookup?

Have you checked that Azure Firewall have policies for all the needed ports? https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/config-firewall-for-ad-domains-and-trusts

You can use Test-NetConnection -ComputerName "NameOfDC" -Port 88

And then test the required ports. 

Also worth checking out the firewall logs in Azure Firewall to see if some traffic is being intercepted. 

    AzureDiagnostics
    | where Category == "AZFWApplicationRule"
    | sort by TimeGenerated
    | project TimeGenerated, Fqdn_s, TargetUrl_s, Action_s, ActionReason_s, DestinationPort_d, RuleCollection_s

    AzureDiagnostics
    | where Category == "AZFWNetworkRule"
    | sort by TimeGenerated
    | project TimeGenerated, Protocol, SourceIP, DestinationIP, DestinationPort, Action_s, RuleCollection_s

Would suggest checking below as a first step:

• DNS configuration
  • Ensure Azure VM points to the on-prem DNS server directly, not Azure’s default DNS.
  • Use ipconfig /all to confirm DNS settings.
• Time synchronization
  • Make sure Azure VM and Domain Controllers have time within 5 minutes of each other.
  • Run: w32tm /resync and verify with w32tm /query /status.