From: martin.bodenstedt@gmx.de   
      
   Simon schrieb:   
      
   > It could be that the remote site has   
   > more than one subnet, so in this case by default the traffic won't get   
   > there. You can drop to a cmd prompt though and add in the additional   
   > subnets as routes via the tunnel ;)   
   > Bit of a pain as normally you will get a different IP address each time   
   > you connect there, but this can be automated/semi automated with a batch   
   > file.   
      
   Excuse me.   
      
   The *external* IP address changes which is irrelevant to the routing   
   *inside* the VPN (and even if you are assigned a different vpn internal   
   IP - Address each time the tunnel is opened, that should not be a problem).   
      
   If You have to reach several IP subnets within your vpn why not set the   
   default gateway of your VPN subnet to the vpn gateway at headquarters?   
      
   Btw, split tunneling is a security headache for several reasons:   
      
   Consider your remote PC connected to a local LAN with one or more pcs   
   being virus infected. What would these pcs stop from misusing the vpn   
   connected pc to send stuff out through your vpn (remember: viruses need   
   not use the IP protocol but could use netbios rpc as well)?   
      
      
   --   
   Martin Bodenstedt   
      
   (www.die-bodenstedts.de / www.maboko.de)   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)