Share via

Azure Virtual Network Gateway connected, but ping fails

Sven Erik Matzen 76 Reputation points
2023-02-22T14:24:11.9866667+00:00

I'm sure that it's a very obvious problem, but I cannot see it.

My configuration:

  • Azure Virtual Network Gateway
    • custom selectors: 
      • Local address range: 10.20.53.0/25 
      • Remote address range: 10.20.53.128/25
    • S2S-connection with status: Connected => I assume that the all connection parameters are ok and the gateways should work as expected
    • Gateway Subnet: 10.20.53.32/27
  • Test-VM
    • NIC in same VNET, but additional subnet: 10.20.53.112/28
    • ping to 8.8.8.8 => Success
    • route 0.0.0.0 MASK 0.0.0.0 gateway: 10.20.53.113 interface 10.20.53.116
    • http-connection to 10.20.53.100 (application gateway) => ok
    • ping 10.20.53.150 (on-prem-server) => timeout
    • http-connection to 10.20.53.150 (on-prem-server) => timeout
    • tracert 10.20.53.150 => all "Request timed out" without showing any IP addresses

Do I need to "tell" my VM to use the VPN gateway for 10.20.53.128/25 addresses? If so: how?

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,436 questions
Azure Virtual Network
Azure Virtual Network
An Azure networking service that is used to provision private networks and optionally to connect to on-premises datacenters.
2,267 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. KapilAnanth-MSFT 39,461 Reputation points Microsoft Employee
    2023-02-24T09:55:10.5666667+00:00

    @Sven Erik Matzen

    Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well.

    I understand that you are facing connectivity issues between OnPrem server and a Azure VM via S2S Connection

    I suggested you to,

    • Can you check the VM's effective route and see if 10.20.53.128/25 route is pointing towards Azure VPN Gateway? Here
    • Please make sure the NSGs and local firewalls allow and support ICMP ping. You can also test the same using TCP Pings (use RDP Ports)

    Later, you informed it was a Traffic Selector MisMatch (typo in address range).

    Fixing this, resolved the issue.

    Thanks,

    Kapil

    Please don’t forget to close the thread by clicking "Accept the answer" wherever the information provided helps you, as this can be beneficial to other community members.

    0 comments