Azure Virtual Server over site to site VPN - Need a static route to access?

Question

I have an Azure cloud server and I have set up the site to site vpn according to our routers online document. https://customer.cradlepoint.com/s/article/NCOS-Cradlepoint-to-Azure-Site-to-Site-VPN-Tunnel

I have a Connected status in Azure but I am unable to access the networks. Site A cannot ping the Azure server and visa versa. I added a static route to the Site A server and I added the route in the Cradlepoint:

route add 10.0.0.0 mask 255.255.255.0 192.168.0.1

Answer 1

Hi JC,

You do not need any Azure route table here.

Does your Azure VM is in the same Vnet of your VPN Gateway or in another one?

If it's in another one make sure both vnet are peered together with the following options:

• The option Allow gateway transit is set to true on the VPN Gateway peering
• The option Use remote gateways is set to true on the VM Vnet peering

James

Answer 2

The server is in the same vnet as the gateway. I can ping the remote machine from the Azure server, however I cannot ping the Azure server from Site A.

Answer 3

Let me rephrase that... My Azure server is on the 10.10 address, as well as my VNet gateway. My remote office is on the 192.168 address as well as its gateway.

Answer 4

What I am trying to do is allow my office network to access the Azure server. I can ping my office server on the 192.168 network from my Azure server (10.10 network) but I cannot ping my Azure server from my Office network.

Answer 5

This is resolved. I found that the Cradlepoint device does not operate fully if there is no subscription active. I had to purchase the license and things started working as it should be.