Forum Discussion
Azure VM Windows Server 2022 Domain Joining Issue
We have multiple Windows Server 2022 VMs in a dedicated Resource Group, created as per best practices for each engagement. All firewall roles, VNet, routing, and NSGs are configured, with Azure Firewall set up to communicate with the on-premises Active Directory. Telnet, nslookup, and ping tests are successful, but attempts to join the domain result in an error stating the network path object is no longer available. Any recommendation for effective troubleshooting steps?
4 Replies
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_sAzureDiagnostics
| where Category == "AZFWNetworkRule"
| sort by TimeGenerated
| project TimeGenerated, Protocol, SourceIP, DestinationIP, DestinationPort, Action_s, RuleCollection_sWould 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.
Dear Kidd_Ip i did the same but still the issue persist. Is it due to OS image while the same OS i install different RG and it's working properly
- DNS configuration
