VPN clients getting wrong default gateway and unable to access internal resources

Hi all ,

I have installed TMG 2010 on Windows Server 2008 R2 with the intention of setting up VPN.VPN clients can dial in but they receive the wrong subnet mask and default getway.As a result when the VPN is connected from the client they are unable to connect to the internet and access internal resources such as share folders..I have tried to change VPN client properties not to use network default getway , that gets the internet working but the resources to the internal resources remain unreachable.any suggestions on what to try  ?

June 28th, 2015 2:30pm

Where are they getting their IP configuration from? In TMG in VPN Address assignment select the internal adapter so they will receive the same as you LAN clients and then act the same. 
Free Windows Admin Tool Kit Click here and download it now
July 1st, 2015 12:03pm

VPN assignment is set on TMG to use the internal adaptor but still no luck. Anything else that can be tried ?
July 4th, 2015 8:18am

One more observation , when I successfully dial in I still cannot ping the domain controller
Free Windows Admin Tool Kit Click here and download it now
July 4th, 2015 8:24am

Another vital observation. In TMG logs I see a status from the default rule stating in " An incoming packet was dropped because its destination address does not exist on the system and no appropriate interfaces exist " 

The source : VPN client

destination : external multi cast

Protocol :Link-local name resolution

July 5th, 2015 2:01pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics