Re: VPN client adds wrong route to local route table
- From: "Bill Grant" <not.available@online>
- Date: Sun, 30 Oct 2005 11:59:20 +1100
That looks correct to me. The client should have a host route to the VPN
server's "external" IP through the LAN gateway. That is where the encrypted
and encapsulated data has to go for the VPN tunnel to work. You should be
able to ping the server through the tunnel using its "virtual" IP. You can
see what that is from the client. If you click on the connection icon it
will show you both the client and server "virtual" IP addresses.
The routing table you gave was probably made with the "use default
gateway.." box cleared. Exactly what that setting does is explained in
KB254231 .
snowdog_2112 wrote:
> Also thought I'd mention that changing Use Default Gateway on Remote
> Network in the VPN client config makes no difference to the route
> table.
.
- Follow-Ups:
- Re: VPN client adds wrong route to local route table
- From: snowdog_2112
- Re: VPN client adds wrong route to local route table
- References:
- VPN client adds wrong route to local route table
- From: snowdog_2112
- Re: VPN client adds wrong route to local route table
- From: snowdog_2112
- VPN client adds wrong route to local route table
- Prev by Date: Re: After VPN conn. i am not able to ping local comp by NAME
- Next by Date: Setting Up DNS Entry for Multiple Network Segments
- Previous by thread: Re: VPN client adds wrong route to local route table
- Next by thread: Re: VPN client adds wrong route to local route table
- Index(es):
Relevant Pages
|
|
