- Ensure that the NSG associated with the VM's subnet or NIC allows inbound RDP (port 3389) and ICMP (ping) traffic.
- Check for any UDRs applied to the subnet that might be misrouting traffic.
- Ensure traffic destined for the on-premises network is routed through the virtual network gateway.
- Confirm the IP address range of your on-premises network is correctly defined in the Local Network Gateway in Azure.
- Ensure the Azure VPN gateway's IP is correctly configured on the SonicWall device.
- Use the Effective Routes feature in the Azure portal to verify the routing table for the VM's subnet. Ensure routes for the on-premises network are correctly configured.
- Check the Windows Firewall (or any other firewall) on the VM to ensure it allows RDP and ICMP traffic.
- If there is any Azure Firewall between your Spoke VNets and VPN gateway, make sure you allow traffic between the networks.
- Use the Network Watcher tool in Azure to test connectivity from the VM to the on-premises network and vice versa. This can help pinpoint where the traffic is blocked.
https://learn.microsoft.com/en-us/azure/network-watcher/connection-troubleshoot-manage?tabs=portal - If the issue persists, try resetting the Azure VPN gateway to resolve any transient issues with the gateway.
- Can you check the VPN diagnostic logs.
Refer this doc :https://learn.microsoft.com/en-us/azure/vpn-gateway/troubleshoot-vpn-with-azure-diagnostics
Kindly let us know if the above helps or you need further assistance on this issue.
Please do consider to “up-vote” wherever the information provided helps you, this can be beneficial to other community members.