From: stephen@dino.dnsalias.com   
      
   "lou"  writes:   
   > I currently have a VPN set up that works great if the connection is not   
   > from the same network. Example if the client 's computer has an address   
   > of 192.168.0.xxx, it connects via vpn everything is great.  If the   
   > client has an address 192.168.1.xxx it connects, but cannot see   
   > anything on the other network even though the connection is connected.   
   > The server side of the VPN is on a 192.168.1.xxx network.  I cannot   
   > change the network on the server side nor can I control the clients lan   
   > connections.  Any help would be greatly appreciated,I have to go   
   > through hoops to configure clients routers to do DHCP for diffrent   
   > addresses and can be a pain for the non computer savy.   
      
   If the client is setting up a subnet<->subnet VPN then you are either   
   going to have to re-number one or both sides or use NAT to remap your   
   subnet to another range for each client who clashes.   
      
   Is each client is a "road warrior" that just wants to connect up a   
   single computer to your network then you can make this work your IPsec   
   server supports allocating a virtual IP for each user that connects in   
   and your clients IPsec system supports binding to that virtual IP.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)