Quantcast
Channel: Azure Networking (DNS, Traffic Manager, VPN, VNET) forum
Viewing all articles
Browse latest Browse all 6513

site to site vpn not working correctly

$
0
0

Hi,

We are new to azure and want to set up a Site2Site VPN with our azure environment.

I’ve set up a virtual machine in Azure in the subnet of 10.1.0.0/24. It also has a public IP address so I can access it via RDP.

And added a Virtual Network Gateway in the subnet of 10.1.1.0/24 (GatewaySubnet) with a Route-Based VPN.

Also we configured our local firewall and everything worked. So I went home.

When I came into the office the next morning, it was broken and we have no idea why. The VPN seems to be up, but no traffic is coming from azure though the tunnel (the data is only supposed to flow from azure -> on premise).

The VPN connection switches it’s status from connected to succeeded all the time.  It was like that from the beginning.

What does that mean?

I checked the connection’s audit logs  and it shows no errors.

The last entry reads:

Operation Name

 Microsoft.Network/connections/write  

Status

 Succeeded  

 

Event Timestamp

 Mon Jun 27 2016 17:15:57 GMT+0200 (W. Europe Daylight Time)  

UTC Timestamp

 Mon, 27 Jun 2016 15:15:57 GMT

I have no idea why it switches it’s status all the time.

Our firewall guys confirmed that the VPN is up.

All Resources are located in Western Europe.

Yes I tried rebooting the VM.

The VM’s IP is 10.1.0.4 and it’s default gateway is 10.1.0.1

We have a Virtual Network which both the VM and the virtual network gateway are connected to.

It shows it’s address space as 10.1.0.0/23 and it’s subnets as 10.1.0.0/24 and 10.1.1.0/24.

The thing is there seems to be some kind of magic that makes the traffic flow through the VPN and I don’t get it. Where can I configure the routes?

If I should clarify anything else, please do ask!

Thanks!


Viewing all articles
Browse latest Browse all 6513

Latest Images

Trending Articles



Latest Images

<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>