You may create a persistent route. Posting the routing table here may help.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net 
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com 
 "Adam Rosner" <adam.rosner@gmail.com> wrote in message news:1164323521.579624.216770@l12g2000cwl.googlegroups.com...
 I have a D-Link DI-808HV VPN router, which can act as an PPTP server,
 and am making PPTP connections over the internet using the XP VPN
 client. I'm running a subnet of 192.168.7.x on the LAN side. Problem is

 the D-Link offers no easy way to control the virtual IPs used, other
 than
 entering the subnet that it is to be used, and it cannot be the same as
 the local LAN subnet. So I set it to use 192.168.6.0. It then gives the

 client connection a variable IP in this range, and there is no way to
 know what this IP will be beforehand.

 If the client checks the "use default gateway on remote network"
 box, it can access the LAN behind the D-Link, as the client sets up the
 0.0.0.0 default gateway to point to the VPN connection.  However, I
 would
 like to leave this unchecked, so the client can still access the
 internet
 normally over the local connection. However, since the D-Link gives the
 VPN a 192.168.6.0 subnet, this isn't going to work.

 It will not allow setting the "Virtual IP of PPTP Server" to the same
 IP
 as the internal IP of the Router (ie. 192.168.7.1).

 Is there any resolution to this? The documentation on the D-Link
 support site
 suggests that the client should be able to ping servers on the LAN -
 not so.

 OR shall I admit defeat and leave the "Use Default Gateway..." option
 turned ON
 at the client end, and live with it?