Can't ping or RDP other Virtual Networks across VPN
JamesJoy
Newbie ✭
I have a trial NSV270 setup on Azure on its own Virtual Network (VNetA). There are 2 other Virtual Networks on this Azure test system (VNetB and VNetC)
I also have an on-premise system with a TZ670 so I have a Site-to-Site VPN setup.
Everything is working with the expectation that I can't ping or RDP VMs on the other virtual networks (VNetB and VNetC) from on-premise PCs. I can ping and RDP VMs on that are on the same virtual network as the NSv (VNetA) and can ping the on-premise devices from all Azure Virtual Networks as well as ping across the Virtual Networks.
Any clues?
I have tried various rules, disabling Network Security Groups, etc but still will not work.
Best Answer
-
CORRECT ANSWERJamesJoy
Newbie ✭
Thanks this helped but it was not the answer.
I followed this to set it up initially.
However, this is slightly wrong. So I removed all the peering and routing between the VNets, then set up the peering, allowing forwarding between them, and then in SonicWall VNet routing table associated the other VNets, rather than setting up routing tables on each VNet and this resolved the issue and all now working.
0
Answers
@JamesJoy
You need to set the Allow gateway transit option in the "Hub-RM" virtual network in a peering from Azure VNETA to Azure VNETB and enable the Use remote gateways in the "Spoke-RM" virtual network in a peering from Azure VNETB to Azure VNETA. Do not select allow traffic forwarding.