Routing for remote gateway over VPN in Vista/7 broken?
- by Raymond
Hi,
Situation is as follows.
Home computer running Windows 7, sets up VPN connection (LT2P + IPSec, "use remote gateway" disabled) to office. Subnet is 192.168.64.x
Office has Draytek Vigor 2920 router, subnet is 192.168.32.x
What happens?
- VPN connection itself works fine
- Can ping any machine on the remote network
- When trying to open a webpage from a host in the remote network, the remote server logs the incoming request, but the browser hangs on "waiting for..." and eventually times out.
I have observed this problem on Windows Vista and Windows 7. On Windows XP however there is no problem like described above.
The only clue I have is that there is a difference in the routing between XP and Vista/7.
The output of "route print" on Windows XP looks like this:
(See www.latunyi.com/routing_xp.png)
So here the gateway for the 192.168.32.x subnet is the IP address that the local computer has in the remote network.
The output of "route print" on Windows 7 (and Windows Vista) looks like this:
(See www.latunyi.com/routing_win7.png")
Now the gateway for the 192.168.32.x subnet is the IP address of the VPN router (32.1). I don't know if that causes this trouble, but it seems a bit strange.
Enabling "use default gateway on remote network" doesn't make a difference. Using the new option "Disable class based route addition" in Windows 7 only makes the route to the VPN router disappear.
I am really puzzled here. I assume the VPN routing can't be broken in both Vista and Windows 7, and this should just work without manually adding routes.
I hope someone has a solution for this problem :-).
Thanks!
