From: stephen_hope@xx.ntlworld.com   
      
   "Michael Salem"  wrote in message   
   news:MPG.1a17598eb54eff3d989897@News.individual.NET...   
   > I asked:   
   >   
   > > > The requirement is to VPN a workstation, which is connected to its own   
   > > > local network, to a remote network. However, both the local network   
   and   
   > > > the remote network use the same address range (192.168.0.x actually),   
   > > > and specific addresses are duplicated;   
   >   
   > Alan Smith responded:   
   >   
   > > If can renumber one of the subnets, that would be the easiest solution.   
   > >   
   > > Else you would need another router and double NAT to get round this.   
   >   
   > Thanks; this is much as I thought. For my purposes the moral is: if you   
   > are going to connect to a variety of VPNs, set up your own network to   
   > use an obscure address range to prevent this sort of clash.   
      
   You do have another option - needing unique addresses for an "extranet"   
   style interconnect is one of the things you can apply for an IP address   
   allocation - even if it wont be visible on the Internet.   
      
   That way there should be any clashes at the central point, and if there is   
   an address clash - it will be somone misusing your address space   
   >   
   > Best wishes,   
   > --   
   > Michael Salem   
   --   
   Regards   
      
   Stephen Hope - remove xx from email to reply   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)