P2S routing issue

FunMum 120 Reputation points
2025-06-16T18:56:45.5366667+00:00

Hi, I am facing an issue.

I have 2 networks. VNET1 (10.1.0.0/16) is hosting the VPN Gateway. VNET2 (10.2.0.0/16) has a virtual machine(10.2.0.10) that the VPN user is trying to reach (Windows Client). VNET2 is a vnet in a different subscription than VNET1 but in the same tenant.

I added VNET2 to the "additional routes to advertise' in the point to site settings and redownloaded the configuration file.

I cannot reach the vm 10.2.0.10 when I cannot to the VPN client. I am not sure what I am missing or if I hit a limitation with peering across subscriptions with P2S. Thank you!

VNET1 to VNET2 Peer Settings (good connection status)

Allow 'vnet1' to access 'vnet2' (enabled)

Allow 'vnet1' to receive forwarded traffic from 'vnet1'(enabled)

Allow gateway or route server in 'vnet1' to forward traffic to 'vnet' (enabled)

Enable 'vnet1'to use 'vnet2' remote gateway or route server (disabled)

VNET2 to VNET Peer Settings (good connection status)

Allow 'vnet2' to access 'vnet1'(enabled)

Allow 'vnet2' to receive forwarded traffic from 'vnet1'(enabled)

Allow gateway or route server in 'vnet2' to forward traffic to 'vnet1'(disabled)

Enable 'vnet2' to use 'vnet1's' remote gateway or route server (enabled)

Azure VPN Gateway
Azure VPN Gateway
An Azure service that enables the connection of on-premises networks to Azure through site-to-site virtual private networks.
1,778 questions
{count} votes

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.