Re: VPN client adds wrong route to local route table
- From: "snowdog_2112" <dkiernan@xxxxxxxxxxxxxxxxxxx>
- Date: 31 Oct 2005 09:32:55 -0800
That's correct. The VPN server is the AD server and acts as DNS/WINS.
There is another DC on 192.168.10.9 that is running DNS and WINS.
>>From the VPN connection on the client, I can:
nslookup 192.168.10.10 192.168.10.9
....and get a valid response, but
nslookup 1921.68.10.10 192.168.10.10
....fails. I'm assuming because the traffic is going to 10.30.0.1 over
the client's 10.30.0.11 interface because of that route on the client.
10.30.0.1 is blocking all but 1723, GRE and ICMP (I can, incidentally,
ping 192.168.10.10 with the VPN connected).
As a test, I denied ICMP at the router and pings to 192.168.10.10
failed.
Incidentally, there is only one router between these segments -- in
fact, the 10.30.0.1 is one ethernet on the router and 192.168.10.1 is a
different ethernet on that same router. I don't see how that would
cause this, but it occurred to me that it is worth mentioning.
.
- 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
- Re: VPN client adds wrong route to local route table
- From: Bill Grant
- VPN client adds wrong route to local route table
- Prev by Date: Re: VPN client behind Windows 2003 NAT problem
- Previous by thread: Re: VPN client adds wrong route to local route table
- Next by thread: After VPN conn. i am not able to ping local comp by NAME
- Index(es):
Relevant Pages
|
|
