Windows 7 64bit Client to Windows 2008 64bit server
Posted: Tue Apr 05, 2011 2:06 am
I am trying to get Openvpn server running on one of two hosted servers. I have JJK OpenVpn 2 Cookbook and I have read every post possible. I know windows networking pretty well and can usually get openvpn up and running quickly. For this setup I an issue that I cannot solve.
First my network.
Server Windows 2008 64bit Client Windows 7 64bit
173.XXX.80.34 <====> 192.168.1.125
VPN VPN
10.130.243.9 10.130.243.10
All firewalls are turned off. The network comes up fine and 10.130.243.9 pings from the client fine. But I cannot get packets to route to 173.XXX.80.34 over the vpn connection.
I have replicated my setup to a virtual machine. The odd thing is that on the vm everything works fine.
I went ahead and set up client and server config files that are very simplified and the problem still reproduces. This is basically the Routing recipe in Chapter 1 from OpenVPN 2 Cookbook.
Here is my Server Config:
Here is my Client Config:
I went ahead and updated to 2.2RC2 2011.03.25 to see if that was any better, but it did not help. I have tried rout-delay 30, and route-method-exe settings. I have also verifed both client and server are running as administrators (UAC turned off, windows Compatbility setting to run as administrator). I have also tried setting compatbility to Vista SP1 and XP Sp3. With no luck.
I am using the route add command:
Wireshark shows that the icmp packet is never hitting the TAP interface at all. I have ipenablerouter set to true and have verified that in netsh. I have gone through everything in netsh int dump and there are no real differences. Ipenablerouter is enabled on both servers and on the client. I have disabled isatap and ipv6 interfaces.
When connecting to the hosted server, I see that windows is actually sending an ARP request for 173.XXX.80.34. But no one is replying to that ARP request.
When testing on the VM environment the icmp packet never hits the vpn network, but the reply shows up there and ping is happy with that. I have tried everything using netcat/netcapture nc.exe and verfied that the network is not routing packets.
I have gone through the logs in extensive detail and they are identical. I can post them if they would help.
It just seems that windows does not like this route in any way or form.
What can i do to further debug this issue? Any help is greatly appreciated.
Thanks
Brad
route print for the failing hosted server:
===========================================================================
Interface List
18...00 ff a5 b5 91 e9 ......TAP-Win32 Adapter V9
11...6c f0 49 57 68 c8 ......Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC (ND
IS 6.20) #2
10...6c f0 49 56 d0 0c ......Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC (ND
IS 6.20)
1...........................Software Loopback Interface 1
16...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
===========================================================================
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.151 60
10.130.243.8 255.255.255.252 On-link 10.130.243.10 286
10.130.243.10 255.255.255.255 On-link 10.130.243.10 286
10.130.243.11 255.255.255.255 On-link 10.130.243.10 286
127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
169.254.0.0 255.255.0.0 On-link 192.168.1.151 31
169.254.0.0 255.255.0.0 On-link 10.130.243.10 306
169.254.255.255 255.255.255.255 On-link 192.168.1.151 286
169.254.255.255 255.255.255.255 On-link 10.130.243.10 286
173.204.80.0 255.255.255.0 On-link 10.130.243.10 31
173.204.80.255 255.255.255.255 On-link 10.130.243.10 286
192.168.1.0 255.255.255.0 On-link 192.168.1.151 286
192.168.1.151 255.255.255.255 On-link 192.168.1.151 286
192.168.1.255 255.255.255.255 On-link 192.168.1.151 286
224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 192.168.1.151 286
224.0.0.0 240.0.0.0 On-link 10.130.243.10 286
255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
255.255.255.255 255.255.255.255 On-link 192.168.1.151 286
255.255.255.255 255.255.255.255 On-link 10.130.243.10 286
===========================================================================
Persistent Routes:
Network Address Netmask Gateway Address Metric
169.254.0.0 255.255.0.0 192.168.1.151 1
169.254.0.0 255.255.0.0 192.168.96.1 1
169.254.0.0 255.255.0.0 192.168.244.1 1
===========================================================================
IPv6 Route Table
===========================================================================
Active Routes:
If Metric Network Destination Gateway
10 4116 ::/0 fe80::c2c1:c0ff:fe51:4c0
1 306 ::1/128 On-link
16 58 2001::/32 On-link
16 306 2001:0:4137:9e76:813:1ed:b3e3:644a/128
On-link
10 28 2002:4c1c:9bb5::/64 On-link
10 276 2002:4c1c:9bb5:0:2c6c:97b1:b8e2:9a8f/128
On-link
10 276 2002:4c1c:9bb5:0:610c:6890:6e99:50b4/128
On-link
10 276 fe80::/64 On-link
18 286 fe80::/64 On-link
16 306 fe80::/64 On-link
16 306 fe80::813:1ed:b3e3:644a/128
On-link
10 276 fe80::610c:6890:6e99:50b4/128
On-link
18 286 fe80::a8f7:bd93:9e80:998f/128
On-link
1 306 ff00::/8 On-link
16 306 ff00::/8 On-link
10 276 ff00::/8 On-link
18 286 ff00::/8 On-link
===========================================================================
Persistent Routes:
None
route print for the working vm server:
First my network.
Server Windows 2008 64bit Client Windows 7 64bit
173.XXX.80.34 <====> 192.168.1.125
VPN VPN
10.130.243.9 10.130.243.10
All firewalls are turned off. The network comes up fine and 10.130.243.9 pings from the client fine. But I cannot get packets to route to 173.XXX.80.34 over the vpn connection.
Code: Select all
>ping 173.XXX.80.34 /S 10.130.243.10
Pinging 173.XXX.80.34 from 10.130.243.10 with 32 bytes of data:
Request timed out.
Request timed out.
I went ahead and set up client and server config files that are very simplified and the problem still reproduces. This is basically the Routing recipe in Chapter 1 from OpenVPN 2 Cookbook.
Here is my Server Config:
Code: Select all
ifconfig 10.130.243.10 10.130.243.11
dev tun
auth none
Code: Select all
ifconfig 10.130.243.10 10.130.243.9
route-delay 30
dev tun
auth none
remote 173.XXX.80.34
verb 4
I am using the route add command:
Code: Select all
>route add 173.204.80.0 mask 255.255.255.0 10.130.243.10 metric 1
OK!
When connecting to the hosted server, I see that windows is actually sending an ARP request for 173.XXX.80.34. But no one is replying to that ARP request.
When testing on the VM environment the icmp packet never hits the vpn network, but the reply shows up there and ping is happy with that. I have tried everything using netcat/netcapture nc.exe and verfied that the network is not routing packets.
I have gone through the logs in extensive detail and they are identical. I can post them if they would help.
It just seems that windows does not like this route in any way or form.
What can i do to further debug this issue? Any help is greatly appreciated.
Thanks
Brad
route print for the failing hosted server:
===========================================================================
Interface List
18...00 ff a5 b5 91 e9 ......TAP-Win32 Adapter V9
11...6c f0 49 57 68 c8 ......Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC (ND
IS 6.20) #2
10...6c f0 49 56 d0 0c ......Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC (ND
IS 6.20)
1...........................Software Loopback Interface 1
16...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
===========================================================================
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.151 60
10.130.243.8 255.255.255.252 On-link 10.130.243.10 286
10.130.243.10 255.255.255.255 On-link 10.130.243.10 286
10.130.243.11 255.255.255.255 On-link 10.130.243.10 286
127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
169.254.0.0 255.255.0.0 On-link 192.168.1.151 31
169.254.0.0 255.255.0.0 On-link 10.130.243.10 306
169.254.255.255 255.255.255.255 On-link 192.168.1.151 286
169.254.255.255 255.255.255.255 On-link 10.130.243.10 286
173.204.80.0 255.255.255.0 On-link 10.130.243.10 31
173.204.80.255 255.255.255.255 On-link 10.130.243.10 286
192.168.1.0 255.255.255.0 On-link 192.168.1.151 286
192.168.1.151 255.255.255.255 On-link 192.168.1.151 286
192.168.1.255 255.255.255.255 On-link 192.168.1.151 286
224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 192.168.1.151 286
224.0.0.0 240.0.0.0 On-link 10.130.243.10 286
255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
255.255.255.255 255.255.255.255 On-link 192.168.1.151 286
255.255.255.255 255.255.255.255 On-link 10.130.243.10 286
===========================================================================
Persistent Routes:
Network Address Netmask Gateway Address Metric
169.254.0.0 255.255.0.0 192.168.1.151 1
169.254.0.0 255.255.0.0 192.168.96.1 1
169.254.0.0 255.255.0.0 192.168.244.1 1
===========================================================================
IPv6 Route Table
===========================================================================
Active Routes:
If Metric Network Destination Gateway
10 4116 ::/0 fe80::c2c1:c0ff:fe51:4c0
1 306 ::1/128 On-link
16 58 2001::/32 On-link
16 306 2001:0:4137:9e76:813:1ed:b3e3:644a/128
On-link
10 28 2002:4c1c:9bb5::/64 On-link
10 276 2002:4c1c:9bb5:0:2c6c:97b1:b8e2:9a8f/128
On-link
10 276 2002:4c1c:9bb5:0:610c:6890:6e99:50b4/128
On-link
10 276 fe80::/64 On-link
18 286 fe80::/64 On-link
16 306 fe80::/64 On-link
16 306 fe80::813:1ed:b3e3:644a/128
On-link
10 276 fe80::610c:6890:6e99:50b4/128
On-link
18 286 fe80::a8f7:bd93:9e80:998f/128
On-link
1 306 ff00::/8 On-link
16 306 ff00::/8 On-link
10 276 ff00::/8 On-link
18 286 ff00::/8 On-link
===========================================================================
Persistent Routes:
None
route print for the working vm server:
Code: Select all
>route print
===========================================================================
Interface List
18...00 ff a5 b5 91 e9 ......TAP-Win32 Adapter V9
11...6c f0 49 57 68 c8 ......Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC (N
IS 6.20) #2
10...6c f0 49 56 d0 0c ......Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC (N
IS 6.20)
1...........................Software Loopback Interface 1
16...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
===========================================================================
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.151 60
10.130.243.8 255.255.255.252 On-link 10.130.243.10 286
10.130.243.10 255.255.255.255 On-link 10.130.243.10 286
10.130.243.11 255.255.255.255 On-link 10.130.243.10 286
127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
169.254.0.0 255.255.0.0 On-link 192.168.1.151 31
169.254.0.0 255.255.0.0 On-link 10.130.243.10 306
169.254.255.255 255.255.255.255 On-link 192.168.1.151 286
169.254.255.255 255.255.255.255 On-link 10.130.243.10 286
192.168.1.0 255.255.255.0 On-link 192.168.1.151 286
192.168.1.125 255.255.255.255 On-link 10.130.243.10 31
192.168.1.151 255.255.255.255 On-link 192.168.1.151 286
192.168.1.255 255.255.255.255 On-link 192.168.1.151 286
224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 192.168.1.151 286
224.0.0.0 240.0.0.0 On-link 10.130.243.10 286
255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
255.255.255.255 255.255.255.255 On-link 192.168.1.151 286
255.255.255.255 255.255.255.255 On-link 10.130.243.10 286
===========================================================================
Persistent Routes:
Network Address Netmask Gateway Address Metric
169.254.0.0 255.255.0.0 192.168.1.151 1
169.254.0.0 255.255.0.0 192.168.96.1 1
169.254.0.0 255.255.0.0 192.168.244.1 1
===========================================================================
IPv6 Route Table
===========================================================================
Active Routes:
If Metric Network Destination Gateway
10 4116 ::/0 fe80::c2c1:c0ff:fe51:4c0
1 306 ::1/128 On-link
16 58 2001::/32 On-link
16 306 2001:0:4137:9e76:813:1ed:b3e3:644a/128
On-link
10 28 2002:4c1c:9bb5::/64 On-link
10 276 2002:4c1c:9bb5:0:2c6c:97b1:b8e2:9a8f/128
On-link
10 276 2002:4c1c:9bb5:0:610c:6890:6e99:50b4/128
On-link
10 276 fe80::/64 On-link
18 286 fe80::/64 On-link
16 306 fe80::/64 On-link
16 306 fe80::813:1ed:b3e3:644a/128
On-link
10 276 fe80::610c:6890:6e99:50b4/128
On-link
18 286 fe80::a8f7:bd93:9e80:998f/128
On-link
1 306 ff00::/8 On-link
16 306 ff00::/8 On-link
10 276 ff00::/8 On-link
18 286 ff00::/8 On-link
===========================================================================
Persistent Routes:
None