Re: VPN client adds wrong route to local route table
- From: "Bill Grant" <not.available@online>
- Date: Mon, 31 Oct 2005 17:24:07 +1100
The client usually gets the DNS and WINS addresses which are configured
on the RRAS server. Does your RRAS server point to its 192.168.10.10 address
for these?
snowdog_2112 wrote:
> The problem I have is that the DNS and WINS settings that get assigned
> on the PPP connection are the 192.168.10.10 address of the VPN server,
> so any nslookups or WINS lookups fail because those requests are
> directed out the client's LAN gateway.
>
> What you're suggesting is that any traffic from the VPN client to the
> VPN server is sent outside the tunnel. Since only the VPN ports are
> open on the router, those operations fail. Yet if I direct an
> nslookup to another server on the network (on the same segment as the
> VPN server), the lookups work.
>
> I think I'm missing something.
>
> Also, as I mentioned, I made a VPN connection from another client to a
> different VPN server and did not get a route for the VPN server --
> just the route for the private network with a gateway of the PPP ip.
>
> Please let me know if I'm missing something here.
.
- 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
- Re: VPN client adds wrong route to local route table
- From: Bill Grant
- 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: Persistent Bi-Di VPN problems
- Next by Date: Re: After VPN conn. i am not able to ping local comp by NAME
- 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
|
|