XPost: comp.security.firewalls, comp.os.ms-windows.networking.tcp-ip,   
   microsoft.public.windowsxp.work_remotely   
   From: notme@notme.com   
      
   landenmelton@gmail.com wrote in news:1127954292.212270.248590   
   @g47g2000cwa.googlegroups.com:   
      
   > I have successfully setup a VPN tunnel between a PC using the Netgear   
   > VPN Client Software and a Netgear FVS318v3 router. Here is the setup. I   
   > have a client PC running the client software behind a router connected   
   > to a cable modem. This client PC's internal IP is 192.168.111.3. I have   
   > the FVS318v3 configured as a DHCP server. It's internal IP Address is   
   > 192.168.10.1. The external IP Address of the router for example is   
   > 63.23.228.125. I can connect using the client and successfully ping the   
   > router's internal IP address of 192.168.10.1 from the client. I'm   
   > assuming the VPN tunnel is connected and working correctly. What I'm   
   > trying to accomplish is to route all of the client's traffic through   
   > the VPN for security reasons.   
      
   >  I've tried configuring my ip settings on   
   > the client machine point it's gateway to 192.168.10.1 and that didn't   
   > work.   
      
   What does that mean? What didn't work?   
      
   And what's wrong with using a static IP that's in the 192.168.10.xxx   
   range, like the device/gateway IP of the router?   
      
   Duane :)   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)