Setting Static Routes on Windows VPN Client
Posted on 2007-08-02
I have a Windows 2003 AD Network split into two subnets - 192.168.0.x and 192.168.1.x.
On the 192.168.1.x network we have a Draytek Vigor 3300V acting as a VPN Router at 192.168.1.1.
VPN users access the VPN using the standard Windows VPN Client. DHCP gives out IP addresses in the range of 192.168.1.225-250 to new VPN connections.
With the TCP/IP option "Use Default Gateway on Remote Network" turned on, browsing all remote services on both the 192.168.0.x and 192.168.1.x subnets is fine - but of course all Internet traffic is all pushed down the VPN route, rather than locally. This is not desirable.
If "Use Default Gateway on Remote Network" is turned off, the end-user can only browse services on the 192.168.1.x subnet, and can't reach the 192.168.0.x subnet.
I've been unable to find a way to use the Windows ROUTE command to add a static route to the 1.x subnet as the IP address of the VPN gateway changes each time the user logs on. It might be 192.168.1.225, next time .226 or .230 - depending on the number of users logged onto the VPN before them.
Can anyone offer any advice as to the best way to setup a Static Route so that 192.168.0.x traffic is routed down the VPN client, but Internet traffic is not?