I've been having a routing issue with OpenVPN and Windows 2003 that's
taken me hours to find because I just didn't see it. OpenVPN is up and
running fine, encryption is fine, client and server are happy. However,
I just couldn't ping or get any network traffic through the interface.
To troubleshoot I ran exactly the same OpenVPN configuration as a server
on a Windows XP SP2 machine locally, pointed the client at it and
instant network traffic - working. I re-ran it on the Windows 2003
server and no joy. I began to look long and hard at my routing tables,
as when I pinged my client VPN address it wanted to pass the traffic off
to the default gateway, so it wasn't going through the VPN interface. I
noticed on the XP machine that a route was created for the 192.168.0.0
network (my private VPN network), subnet mask of 255.255.255.0 with a
gateway of 192.168.0.2 (the gateway set by ifconfig 192.168.0.1
192.168.0.2 in the config file) and a metric of 1. The XP machine as a
server worked fine. On Windows 2003 it creates everything else but
doesn't create this route, and no matter how many times I restarted
OpenVPN it would not add it. When I created it manually using 'route
add' the VPN started working absolutely instantly.
Does anyone know why OpenVPN or Windows 2003 would not be creating this
route, but otherwise be up and running fine? The only difference I can
see with this route is that it is created with a metric of 1, whereas
the others are 30. Is there possibly some IPFilters or other weird
Windows setting that may prevent this? I will try and post my full
routing tables from Windows 2003 and XP to illustrate fully what I mean.
Cheers and thanks in advance,
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
Openvpn-users mailing list