VPN Concentrator routing problem

[chrish]

I am using a 3005 to terminate PPTP tunnels. I am handing out ip addresses to the client which are on the same subnet as the private interface. When Windows clients connect with the "use remote default-gateway" deselected (using the local default-gateway) the concentrator injects a route into the client of 10.0.0.0 via the tunnel. This is causing routing problems on the client's local network as both the local network and the subnet of the private interface are subnets within the 10.0.0.0 range. I have to assume this is configurable but I can't see how. Ideally I would want this route to be restricted to the range of subnets actually available on the remote network. How can I configure this?

[kamal-learn]

hi

the first way to get over this problem is letting your clients specifying their own addresses, the downside of this method is weak security, so if the client address is spoofed by an attacker you ll be hacked too!!!

but to alleviate the risk you need to use a stronger authentification , or even aged password, One time password...

the second try the use of split tunneling in this you specify a network-list that holds all the network that your clients are allowed to reach, so any other traffic destined to other networks not belonging to the network-list will not be tunneled ,instead it will be send to the client default gateway.

HTH

Please do rate if it does help

[5220]

Hi,

Try specifying a different pool for the remote users (ie 192.168.100.x) and create routing for this on your company pointing to the Concentrator.

Please rate if this helped.

Regards,

Daniel