This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(163.2, 18%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMH%3C/text%3E%3C/svg%3E)
Hi everyone, I have three Vnet (192..., 172..., 10...)and two VPN gateways that are connected to my two onprem VPN gateways through Local network gateway. I have peered all the vnets but when I try to ping my onprem server 172... from one of the vnets that has vm 192... It doesn't get through. Alternatively I tried enabling the remote gateway in the peering and I was able to ping from that particular network 192... To 172 but 10.... Cannot ping to 172.. How to solve this. I would image if the vnets are peered then it should just be able to reach all the ips as if it is the same network.. please clarify. Thanks 🙏
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(134.4, 59%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECM%3C/text%3E%3C/svg%3E)
Thank you for reaching out.
I understand you have created Azure VPN connections with your on-prem but you are unable to reach all the virtual networks even though you have peered them.
In order to help troubleshoot this issue please share a Network Diagram of your set-up here showcasing the Vnets and their IP addresses and VPN Gateway connectivity to on-prem?
Common troubleshooting steps you can follow here are
Additional troubleshooting references:
Please let me know if you have any questions. Thank you!
Hi chaitanya,
Below is the network diagram
Gateway transit is enabled.
ON the below screenshot you can see the settings where we have unchecked the remote gateway (when checked it can be reached from Vnet-tmp to on-prem 172.20.50.253) but at the same time I am not able to reach the bcp network 192.168.152.243. But if i go in to the bcp peering and enable the remote gateway peering setting there then only i am able to ping to 192.168.152.243. But as you have explained above " a vnet can have only one gateway, local or remote" then in such situation how do i route the vnet_temp to bcp 192.168.152.243
Hope you understand the scenario. Thanks a ton for your reply.
Not sure if you got my reply as i dont see it after hitting add comment.
So i am resending it to you.
Below is the scenario.
Gateway transit is enabled.
As you explained if i have the remote gateway setting checked in the peering of Vnet_temp to Vnet......hq then I am able to ping from 10.98.200.4 to 172.20.50.253 but at the same time i am not able to ping to 192.168.152.243
Configure BGP is enabled.
Please refer the second comment as well. We have BGP configure checked..
Thanks @Silvia Wibowo I have done that now and I am able to reach both S1 and S2 from the VM1.
We created two VPN gateways to serve HA between two on-prem vpn devices but having one Zone Redundant type vpn gateway and 4 LNG connections to both the on-prem vpn devices on a separate ISP also serves the active-active HA capabilities.
Thank you for letting us know the issue was resolved. I have converted Silvia's to an answer below, it will help if you could click "Accept the answer" which might be beneficial to other community members reading this thread. And, if you have any further query do let us know.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(25.6, 0%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESW%3C/text%3E%3C/svg%3E)
Hi @Mohamed Hasan Adnan , why do you need two VPN gateways? If you use one VPN gateway to connect to both your on-prem locations, your VM1 will be able to reach both S1 and S2.