On 7/14/11 5:47 AM, Ted Roche wrote: > One of our machines in the office is often used for remote VPN work > into many clients machines. If we're not careful to turn off all of > the software we used to access the remote client (each has their own > scheme/VPN provider), we'll get weird name resolution issues, like not > being able to find local resources, because the VPN is acting like a > network overlaid on top of the actual one, hence, Virtual Private > Network.
Seems that lots of VPN's by default modify the default route on the client to go over the VPN. I could see reasoning behind that in some cases (home office wanting to maintain a strong tether to the road warrior) but most times it makes no sense at all, and just causes confusion. The only thing a VPN should modify in a client's routing table, IMO, is to add a route to the VPN over the tunnel interface. Don't mess with anything else! Paul _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
