vnet to vnet gatway setting

owen.kim 176 Reputation points
2022-07-24T15:07:17.357+00:00

224138-%E1%84%8C%E1%85%A6%E1%84%86%E1%85%A9%E1%86%A8-%E1%84%8B%E1%85%A5%E1%86%B9%E1%84%8B%E1%85%B3%E1%86%B7.png

I want to connect "A vnet VM" with vpn 2 via RDP.

As in the manual, vnet to vnet connection configuration was completed, and RDP connection from "A vnet VM" to "B vnet VM" was successful. However, vnet cross-connection from local PC to p2s was not possible.

All address ranges from vnet to vnet in azure VPN client were shown in vpn route.
What's the problem??? I've been looking at this problem for about a week and it's still stuck.

(Since gateway1 must also have a vnet to vnet connection with gateway3, which will be created later, vnet peering cannot be used.)

(The purpose of using multiple gateways is to separate the gateways for developers and QA.)

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,393 questions
Accepted answer
  1. Jackson Martins 9,646 Reputation points MVP
    2022-07-24T19:54:39.093+00:00

    Hi @owen.kim
    Will start with couple of questions to get more clarity on your setup.

    On Vnet 172.30.0.0/16 did you add a return route to see the network 172.0.5.0/24 ? on custom route

    If not, add this route, because probably the vpn packet is going to the VM correctly but there is no return

    Or
    If run route print on machine with openvpn, did you see route to 172.30.0.0/16?

    If not, add this route on routes.txt in %appdata%\Microsoft\Network\Connections\Cm

    or add configuration on azure p2s config and reinstall client:
    224161-image.png

    Get in touch if you need more help with this issue.

    --please don't forget to "Accept the answer" if the reply is helpful--

    1 person found this answer helpful.

3 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. owen.kim 176 Reputation points
    2022-07-25T03:36:43.57+00:00

    Thank you for answer.
    First, I took pictures to share the status and put them in the address below (google presentation).

    I set it up according to the manual, but still no success.
    Is there any way to check more?

    https://docs.google.com/presentation/d/1oDQ7jiM3E3GRWPvmL_gylY1U3YWFa-2ZDOJnlkMpxyw/edit#slide=id.p

  2. owen.kim 176 Reputation points
    2022-07-25T03:39:22.513+00:00

    It works fine if I peer a vnet and b vnet, but I don't know why I can't make a gateway connection...
    (There are reasons why you should use a gateway.) :(

    0 comments
  3. msrini-MSFT 9,256 Reputation points Microsoft Employee
    2022-07-25T04:48:15.357+00:00

    Hi,

    Instead of creating VNET to VNET connection between Gateways, try Site to Site connection. When you choose Site to Site, you will need to create Local Network Gateway on both the sides. In your VNET 1 Local Network Gateway add your On-Premises address space as well. So that the VNET A resources will have the route to reach On-Premises/ VPN Clients.

    Regards,
    Karthik Srinivas

    0 comments