[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
Re: OT Windows Home Server
--- In ukha_d@xxxxxxx, "Paul Bendall" <paul@...>
wrote:
>
> When you authenticate with a VPN client it will change the routing
> table (which you can view before and after with "route
print" at
> the command-line). The default route then becomes a virtual NIC
> controlled via the VPN. Some times it is possible to add a static
> route for your internal network. But again most coprporate VPN
> clients would drop the VPN if the routing table changed.
This is (AFAIK) not a feature of the VPN client but rather an issue of
how the VPN server that the other end is configured.
In a previous job I had to do a lot of remote access to various
customer systems using VPN clients such as Ciscos. Some customers' VPN
servers announced just a default route when you connected which meant
that all traffic was sent to them, other customers' VPN servers only
announced routes for the IP address ranges that their network used as
so the existing default route on the local PC remained as it (which
was useful when needing to access both a customer site and also my own
companies servers at the same time).
------------------------------------
********************************************
Limited Time Offer - Free iPhone VAT Calculator
http://berble.com/index.php/component/content/article/109
********************************************
UKHA_D Main Index |
UKHA_D Thread Index |
UKHA_D Home |
Archives Home
|