Re: Routing issue with VPN
From: Daniel (reg_at_removebailin.org)
Date: 10/05/04
- Next message: Sven, MVP-Mobile Devices: "Re: Adobe Acrobat"
- Previous message: Sven, MVP-Mobile Devices: "Re: Best Pocket PC ?"
- In reply to: Jeff Kelley [MS]: "Re: Routing issue with VPN"
- Next in thread: Daniel: "Re: Routing issue with VPN"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 04 Oct 2004 21:28:31 -0600
I think Jeff has described what is happening here. Our exchange
server's address begins with 10.x.x.x. So how do I modify the routing
table? That's what my IT guy wanted to do, but neither of us knows
how to do it for PPC.
Thanks.
On Mon, 4 Oct 2004 19:14:50 -0700, "Jeff Kelley [MS]"
<jeffkel@online.microsoft.com> wrote:
>When the VPN connection is established a new "default route" gets added to
>the TCP/IP routing table. This route causes packets which do not match any
>of the other routes to be sent through the VPN tunnel. However, if a
>packet's destination IP address matches another route table entry, e.g. a
>subnet route for another interface, then that match will be used rather than
>the default route.
>
>I have seen some cases, such as an internet connection with a 10.x.x.x
>address, and the VPN server using the same 10.x.x.x address range, that can
>cause routing problems like Daniel described. Some changes have been made to
>mitigate these, and it is possible to workaround the routing issues by
>directly modifying the routing table using the IP Helper APIs.
- Next message: Sven, MVP-Mobile Devices: "Re: Adobe Acrobat"
- Previous message: Sven, MVP-Mobile Devices: "Re: Best Pocket PC ?"
- In reply to: Jeff Kelley [MS]: "Re: Routing issue with VPN"
- Next in thread: Daniel: "Re: Routing issue with VPN"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|