Always ON VPN no access to internal resources

0

Hi

I have setup an Always On VPN lab environment up in Hyper-V. My RRAS server's external connection (192.168.1.160) is on the 192.168.1.0/24 network and this has the default gateway set to my Internet router of 192.168.1.254. The internal connection of the RRAS server (172.16.0.104) is on the 172.16.0.0/24. It also has a PPP adapter RAS (dial In) Interface that has picked up an IP address out of the dynamic pool of 172.16.0.210.

The Always On VPN client is set up for force tunnelling.

If I move one of my domain joined clients to the 192.168.1.0/24 network the Always On VPN connects and I can access internal resources, such as pinging 172.16.0.100 (DC and DNS server). So everything is working as expected.

If I now introduce a Kemp LB and follow your instructions for configuring it by creating 2 x Virtual Servers on UDP ports 500 and 4500 and set up port following, etc that you kindly provided, the Always On VPN client connects, but I cannot access any internal resources.

I have compared routing tables and performed network traces but nothing really shows why I cannot access the internal resources.

Do you have any ideas or tips that could help me out as I really need to get this working before we implement this for real?

Thanks,

Stuart

0 comments