Forum Discussion
Mutliple subnets VPN S2S can't access peered VNets in Azure from Site B
I'm having problems setting up an S2S VPN Connection towards Azure, the connection it self is working and I can access the virtual machines connected to this Virtual Network (let's call it VNet-VPN)....
normaly when specifying your next hop, you would have to indicate the acualy ip of the device able to handle the request. I belive you would need a VM with Routing and remote services to help assist the packets reaching the subnet on the other side of you VNET peering.
i could be mistaken, but lets start with what VPN version are you using, policy or Route based ?
Hi
Thanks for your reply, we're using booth Route- and policy-based VPN Connections some of our customers need Policy-based. But as of now we've just created a Route-based VPN Connection which is up andr running.
And Site-B have access to Site-A, well at least the VMs and resources connected to that VNet.
Regards,
Erik