Hi All,
Here are the specifics. We have a Point to Site setup for our VM Lab running on Azure, this is working correctly. We are using the following:
- VNET = 10.0.0.0/24
- VNETGW = 192.168.200.0/24
- CLIENTPOOL = 172.16.1.0/24
Routing from 10.0.0.0/24 to/from 172.16.1.0/24 works correctly. Meaning that when you logon to the VPN the client is able to access the VM in the VNET and the VM is able to access the Client via the VNETGW/CLIENTPOOL. So, the question we have, is there something additional (e.g.: Routing Table, Network Security Group, ...??) that needs to be put in place so that the clients logged onto the VPN (CLIENTPOOL) can communicate with one another over the VPN? So, for example, I have to client PC's that connect to the VPN:
- PC1 = 172.16.1.4
- PC2 = 172.16.1.5
Currently, neither of these clients can ping one another (and yes, we already opened up the local firewall on the PC and tested that, so that is not the issue). Hence, it appears that the routing on the Azure side is not able to pass the packets between clients in the 172.16.1.0/24 client pool. We very much would like to see this working if it is possible. Thanks for your time.