Well, I noticed that Vista using the same configuration that my XP has is still unable to
apply the new routing table entries. connect to the remote network.
To be more specific I used the latest Openvpn package (2.1.1) from openvpn site, because the GUI is already included into the newer packages.
It has everything to install right on a Vista or Win7 client. My routing table shows the new routes, but still no ping, no nothing to remote network.
The only address to reach is 0.223 which is the GREEN IP of the vpn gateway.
I'm trying to modify automatic metric calculation to manual and give higher priority to TAP adapter's routes.
172.20.0.0 255.255.255.0 On-link 172.20.0.82 286
172.20.0.0 255.255.255.0 172.20.0.223 172.20.0.82 30
172.20.0.82 255.255.255.255 On-link 172.20.0.82 286
172.20.0.255 255.255.255.255 On-link 172.20.0.82 286
So the above tables are failing, mostly because there are two gateways set for remote vpn network.
On-link means default gw for the client machine.
I decided to manually get rid of everything and build-up a new table which is far less sophisticated, but works. I will not change server side configuration just because of this vista issue (=win 7 issue)
1, create a file named "
profilename_up.bat" next to your ovpn configuration
2, add the following contents:
route delete "target_network_address"
route add "target_network_address" mask "target_network_mask" remote_ip_of_TAP IF NN
where NN is the TAP adapter's id as listed after route print command, I have (24):
Interface List
24...00 ff bf e2 ed 95 ......TAP-Win32 Adapter V9
11...00 0c f1 87 3a a5 ......Intel(R) PRO/100 VE Network Connection
That's it.