Comments
-
Yea..I managed to solve the issue.. its all because of address range..if we choose azue vnet 192.168.x.x. for on premise we should choose different ie. either 10.x.x.x or 172.16.x.x. as simple as that…Or you should add some extra routing/NAT rules. hope it helps.
-
Hello All, Here is the detailed informtion AZURE NSV SIDE VNET(192.168.0.0/16) X1 : 192.168.87.0/24 SONICWALL X1 IP : 192.168.87.4 X0 : 192.168.93.0/24 SONICWALL X0 IP : 192.168.93.4 VM1 : 192.168.93.5 **SITE TO SITE VPN WITH ON PREMISE NSA 2600 WORKS FINE* **GLOBAL VPN WITH DHCP/VIRTUAL ADPATOR SETTING DISABLED WORKS…
-
Hi Mustafaa, Thanks for your time for reviewing my question and your valuable advice. Yes I reviewed NSG on Azure side and policies to make the inbound connections are configured. As I mentioned site to site VPN working without any problem. On both GVC and SSL VPN, connections are established and remote PC’s can ping to…