question

AtharvGupta-5596 avatar image
0 Votes"
AtharvGupta-5596 asked GitaraniSharmaMSFT-4262 commented

Azure VPN Vnet

When transitioning to Azure, had thought that this pattern would work as a replacement for the Cisco ASA to support our partners requiring limited access to our environment. Having an issue with gateway transit, however, between the partner VPN gateways and our primary VNet.

  • Client can connect okay to partner VNet and access resources (e.g., VM) in the partner VNet (VPN connect)

  • Routing to primary VNet (10.190.0.0/16) using partner VPN interface appears correctly in client routing table

  • VM in the partner VNet can access resources in primary VNet okay (peering)
    The client, however, is unable reach any resources in the primary VNet which suggests a gateway transit issue in the peering.

Hoping that you might have some insight or suggestions.

azure-virtual-networkazure-vpn-gateway
· 3
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hello @AtharvGupta-5596 ,

Could you please share a network diagram of your setup?
If I understand correctly, client (on-premises) <----VPN----> Partner Vnet <----Vnet peering----> Primary Vnet is the connection setup. Please correct me if I am wrong.

When you say client, is it from on-premises network?
Please confirm if it is S2S VPN or P2S VPN?

So, on-premise can connect to Partner Vnet via Azure VPN and the Partner Vnet VMs can connect to Primary Vnet via Vnet peering. The Vnet peering has gateway transit enabled but on-premise client is unable to access the primary Vnet, is that correct?

Regards,
Gita Sharma

0 Votes 0 ·

Hello @AtharvGupta-5596 , any updates on this post?

0 Votes 0 ·

Hello @AtharvGupta-5596 , any updates on this post from your end?

0 Votes 0 ·

0 Answers