home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   comp.dcom.vpn      VPN protocols, clients, awesomeness      2,348 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 1,193 of 2,348   
   Mike Drechsler - SPAM PROTECTED EMA to jp@nospam.com   
   Re: Question: same network addr. range o   
   13 Sep 04 16:48:35   
   
   From: mike-newsgroup@-DELETETHISPART-.upcraft.com   
      
   jp@nospam.com wrote:   
   > Hello   
   >   
   > With the first configuration below, I cannot connect to workstations on the   
   office network through VPN. I do see the workstations in the network   
   neighborhood, but I can't ping   
   > any of them. If I change my local Lan IP to a range different than the one   
   used on the office LAN, everything works fine.   
   >   
   > Could someone tell me if this is just normal behavior, or is it a bad   
   configuration or a bad routing or a bad something else? If it's normal, I will   
   resignate, but if there is something to   
   > do to correct it, I would gladly welcome some hints.   
   >   
   >   
   > 1) This doesn't work.   
   >   
   > The network at the office is set up with 192.168.0.*   
   > The vnp server (windows server) delivers addresses through DHCP in the range   
   10.1.0.*   
   > My LAN at home also uses IP addresses like 192.168.0.*   
   >   
   >   
   > 2) This works fine   
   >   
   > Same setup as above but my LAN at home uses IP addresses like 192.168.1.* or   
   any other address range.   
   >   
   >   
   > Thanks   
   >   
   > JP Tanguay   
   > jp.keinspam.tanguay@sympatico.ca (drop .keinspam)   
   >   
   >   
      
   This is the correct behaviour.  If you use the same IP's on the local   
   and remote subnet then you either have to renumber one of the subnets or   
   use NAT to translate the IP's of the remote subnet to hide the numbering   
   collision.   
      
   Because the defaults of most routers are set to 192.168.0.x or   
   192.168.1.x I suggest that renumbering the work subnet to anything else   
   would be a good long term plan.  Perhaps renumbering to the 10.1.0.x is   
   a good idea, very few home routers give out IP's using this range of   
   private addresses.   
      
      
      
   --   
   WARNING!  Email address has been altered for spam resistance.   
   Please remove the -deletethispart-. section before replying directly.   
   Mike Drechsler (mike-newsgroup@-deletethispart-.upcraft.com)   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca