Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have setup a tunneling VPN between two machine. One end is (server), the other end is ( The network mask of the distant site is, ie the server has two network interfaces :

On linux, I have access to the address if I do the following in the config file:

#ifconfig directive

On Windows 7, the same config file, launched as administrator is also establishing the route according to openvpn log :

Tue Oct 12 09:24:16 2010 Peer Connection Initiated with xx.xx.xx.xx:yyyy
Tue Oct 12 09:24:22 2010 TEST ROUTES: 1/1 succeeded len=1 ret=1 a=0 u/d=up
Tue Oct 12 09:24:22 2010 C:\WINDOWS\system32\route.exe ADD MASK
Tue Oct 12 09:24:22 2010 ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=30 and dwForwardType=4
Tue Oct 12 09:24:22 2010 Route addition via IPAPI succeeded [adaptive]
Tue Oct 12 09:24:22 2010 Initialization Sequence Completed

But when I try to ping, it does not work, and if I try http://192.168.1123.114/ it does not work either, but it works with

How can I make the routing directive effective ?

share|improve this question
up vote 2 down vote accepted

you've run into a routing quirk when using windows compared to using Linux ; try


i.e. change the remote endpoint; windows seems to want to have the actual remote endpoint for a route to work, whereas Linux/UNIX want the IP address of the interface.



share|improve this answer
You are right, Thank you ! – shodanex Oct 12 '10 at 9:02

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.