Azure VM Routing table loose default gateway when connecting to a VPN fro within the VM

Gustavo Puente 1 Reputation point
2021-03-23T13:24:25.227+00:00

Hi, Hpoe you can help. I migrated a Vultr Windows Server VM to Azure, so right know, I have exactly the same VM on both services. I have a VPN client on those VMs. When dialing the VPN on Vultr, it works correctly without any issues. The route print, appears completly fine. But on Azure (remember is a clone) when I dial the VPN, the RDP connection drops and I loose all connectivity to the VM, I captured the route print in the process and found that the default route 0.0.0.0 .0.0.0. Gateway Interface is deleted when the VPN dial, and also there are a few routes that are like incomplete, like for example w.x.y.x 255.255.255.0 nothing nothing nothing 17 (just a number 7 instead of a gateway IP). Here are the route prints, from before and after dialing the VPN from both servers.

Vultr, Without the VPN
80742-image.png
Vultr, with the VPN
80743-image.png
Azure without the VPN
80751-image.png
Azure With the VPN
80696-image.png

Can someone explain me why is this happening? Thank you

Azure VPN Gateway
Azure VPN Gateway
An Azure service that enables the connection of on-premises networks to Azure through site-to-site virtual private networks.
1,378 questions
{count} votes