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,349 messages   

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

   Message 1,773 of 2,349   
   Simon to Simon   
   Re: VPN connection kills Internet Connec   
   11 Oct 05 18:57:25   
   
   From: simon@not-here.com   
      
   Simon wrote:   
   > Bailey wrote:   
   >   
   >> On Tue, 11 Oct 2005 12:34:23 +0200, Martin Bodenstedt   
   >>  typed:   
   >>   
   >>> Bailey schrieb:   
   >>>   
   >>>> On Tue, 11 Oct 2005 08:44:27 +0200, Martin Bodenstedt   
   >>>>  typed:   
   >>>   
   >>>   
   >>>>> One your VPN tunnel is up and running *all* traffic must go through   
   >>>>> your company's internet connection.   
   >>>   
   >>>   
   >>>> Interesting. I was under the impression that connections remained   
   >>>> separate. Which makes it even more confusing because other   
   >>>> co-workers can use their other applications while connected through   
   >>>> the VPN. I seem to be the exception to the rule.   
   >>>   
   >>>   
   >>> You should be able to use your applications as long as you don't need   
   >>> your own lan.   
   >>>   
   >>> Internet should be accessible through your company's firewall (you   
   >>> might have to set a proxy though).   
   >>   
   >>   
   >>   
   >> Martin; That's the odd thing. I can't access the Internet through the   
   >> company's firewall either. And as far as we can determine a proxy   
   >> isn't necessary, though I will bring that issue up again today.   
   >> Thanks for your ideas.   
   >   
   >   
   >   
   > Windows VPN like pptp or l2tp/ipsec do allow you to go the split route   
   > option (uncheck use default gateway on remote network under   
   > tcpip/advanced properties), so that local lan traffic still stays local,   
   > and only traffic for the subnet that the VPN server has given you an   
   > address on goes down the tunnel. 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.   
   > Simon   
      
   Oh and if you tell us the subnets/addresses you need to get to and the   
   subnet masks involved that would help, 192.x.x.x networks aren't routed   
   on the net so it's not a security problem ;)   
   Simon   
      
   --- 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