Azure VM Routing table loose default gateway when connecting to a VPN fro within the VM
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
Vultr, with the VPN
Azure without the VPN
Azure With the VPN
Can someone explain me why is this happening? Thank you