Strange routing problem on VPN

[Unimatrix02]

Hi,
Situation is as follows.

• Home computer running Windows 7 Ultimate x64, 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

The VPN connection is established, but Windows 7 says "no network access" and indeed, I cannot ping anything on the remote network or open a website hosted on a remote server.

On Windows XP however there is no problem like described above. I can ping remote hosts and open sites hosted on remote servers. So it seems like there is a difference in the routing between XP and Windows 7 (maybe only on x64?).

The output of "route print" on Windows XP (32 bit) looks like what you see in 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 looks like what you see in 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 Windows 7, and this should just work without manually adding routes.

I also tried using the Draytek SmartVPN client, but that just adds a VPN connection in Windows and gets no further than "unknown error" when connecting .

I really hope someone has a solution for this problem .

Thanks!

 

[erikdobbel]

Exact same problem

Hi,

After several weeks in which VPN's worked great between my Win7 Ultimate 64bit EN HP laptop and vigor 2920, it stopped working since this (or maybe last) week.
I'm having the exact same problem.
I noticed that the home or VPN gateway address (my home network is 192.168.1.x and the address range at my holiday network is 192.168.2.x) is not in the IP settings obtained by DHCP over the VPN. Also no route for 0.0.0.0/0.0.0.0 is in my route list.
I manually added the home gateway (192.168.1.1) but that did not help, though a route was added for 0.0.0.0/0.0.0.0 through this gateway. A traceroute doesn't even get to the first hop.

I'll check if any Windows updates my be causing troubles. I haven't upgraded my Vigor in the meantime and I'm not aware of the exact firmware version. Help is appreciated.


Erik Dobbelsteijn

 

[chev65]

Did you open the port for the incoming connection?

Important: Configure your firewall to allow access to TCP port 1723 to allow incoming Point-to-Point Tunneling Protocol (PPTP) connection for VPN.

Router Configuration: Enable PPTP and Generic Route Encapsulation (GRE) on the Router. Depending on the type of router, you need to either enable PPTP or create a port forward to port 1723. If you’re router has an additional setting for PPTP or VPN, make sure it’s enabled. It’s usually called a “pass-through” setting (i.e. PPTP pass-through or VPN pass-through)

http://www.sevenforums.com/tutorial...work-vpn-enable-incoming-vpn-connections.html

http://www.sevenforums.com/tutorial...n-enable-outgoing-vpn-connections.html?filter

 

[erikdobbel]

Sure

Hi,

Thanks for getting back to the issue. Yes, all ports are open and were open. Like I said: the VPN had been working allright.

Update: after a reboot yesterday, I was able to route traffic over the VPN. However, it seems that intermittently, TCP connections get lost. Haven't sniffed yet to see where the traffic goes and what happens to it.

Erik