The route ADD commands in open VPN gui doesn't get executed, even if you run open vpn GUI in administrator mode.
1. Go to C:\Windows\System 32
2. Run cmd.exe in administrator mode (right click on it and select Run as Administrator)
3. Copy all the failed route ADD commands in open VPN gui and run it in this DOS window.
Windows 7 Ultimate beta 1, build 7100
OpenVPN GUI 2.1rc15, Vista build
Installed under 'run as administrator'
Set the program to 'run as administrator'
There are zero error messages in the openVPN gui logs.
All of the routes get added.
From a command prompt 'run as administrator', nslookup gives me the DNS server in the office network. I can type in the name of our file server at the little nslookup prompt, and it gives me the correct IP address of that server. I can ping that server by either the IP address or the hostname, and it responds to the ping.
When I open up a Windows Explorer window and type \\ip.address\ or \\hostname.int.domain.com\ I get an error that "Windows cannot access \\ip.address\".
I have my laptop sitting right next to me. It is running XP Pro and the XP Pro version of Open VPN GUI. It generates the exact same set of routes. And I can use the Windows explorer and type in either \\ip.address\ or \\hostname.int.domain.com\ to browse that file server.
I'm going to post the same question to the good folks at OpenVPN. But I was wondering if anyone here has experienced the same problems or had any ideas.
If you happen to run 64-bit Windows 7:
Compare \program files\openvpn\config and \program files (x86)\openvpn\config. I found that the content of one was different than the other, and the OpenVPN would not connect. After synchronizing the two subdirectories to be identical, Voila!
I did not have to open a firewall port, change the commands in the config file, or do anything else. I hope this helps anyone as exquisitely frustrated as I was.