0
votes

We have single subscription with single vnet in azure which has site to site vpn connection between different branch office. Connectivity is working fine with all branch’s and azure.

Now we have a requirement to setup point to site vpn connectivity where users will dial into azure gateway(we have a flat vnet no hub and spoke) and access azure and on prem. We have deployed azure gateway and setup point to site configuration. Users are able to access azure resources(VM) when they dial into vpn But not able to access on-prem resources.

Onprem -> meraki(deployed in azure) -> azure gateway(deployed on same vnet as meraki) -> windows 10 connected to azure gateway(point to site vpn)

1
Welcome to stackoverflow.com. For any specific problem you are having please include a stackoverflow.com/help/minimal-reproducible-example. Please also read stackoverflow.com/help/how-to-ask and stackoverflow.com/help/dont-ask. Make sure that your questions are specific and not overly broad, see also stackoverflow.com/help/on-topic. Also, be sure to take the stackoverflow.com/tour (you get a badge!).Daniel Björk
Make sure you have activated Allow gateway transit on your Gateway. azure.microsoft.com/en-us/blog/…Daniel Björk
We have a flat network in azure. For that we do not require to create vnet peering and configure gateway transit.vsanjivaiah
ah in that case You need to and the route manually on the clients. docs.microsoft.com/en-us/azure/vpn-gateway/…Daniel Björk

1 Answers

0
votes

As @daniel-björk points out, in the similar case of One VNet and a branch office (BGP), you need to manually add the route to your on-premise site to your Windows client. The non-Windows clients do not have such requirements. Also, the Azure VPN gateway should enable BGP and the site to site VPN connection is running BGP.

enter image description here