windows: ipconfig failing to execute during VPN connection

[VisualCSharp]

This issue was reported at ​http://community.openvpn.net/openvpn/ticket/399, but for some reason it was resolved as notabug. This is quite clearly a bug with the script that the OpenVPN client runs, no? I suspect that, because of this problem, I frequently see DNS resolution failures after connecting to the VPN for domains that are subdomains of the VPN connection's DNS suffix. For example, if my VPN's DNS suffix is corp.mycompany.com and I try to resolve myserver.corp.mycompany.com, the resolution will fail sometimes and succeed others. Reconnecting to the VPN oftentimes does not solve the problem, but it does seem to intermittently resolve itself.

Ideally, we should not be modifying configuration files (on every one of our Windows clients) ourselves to fix this problem. The OpenVPN client should be fixed such that it calls ipconfig.exe with elevated permissions.

Here is a sample of my log file. The error shown repeats itself during every connection attempt.

Fri Jan 23 12:34:21 2015 Start net commands...
Fri Jan 23 12:34:21 2015 C:\Windows\system32\net.exe stop dnscache
Fri Jan 23 12:34:26 2015 C:\Windows\system32\net.exe start dnscache
Fri Jan 23 12:34:26 2015 ERROR: Windows ipconfig command failed: returned error code 2
Fri Jan 23 12:34:26 2015 C:\Windows\system32\ipconfig.exe /flushdns
Fri Jan 23 12:34:26 2015 C:\Windows\system32\ipconfig.exe /registerdns
Fri Jan 23 12:34:29 2015 End net commands...

[Samuli Seppänen]

Reopened ticket 399. As this ticket is about OpenVPN Connect (a commercial client) and the other ticket about OpenVPN 2.3.4 (open source client), I'm not closing this one even though technically these two are almost duplicates.

[Gert Döring]

OpenVPN Inc does not want to receive any feedback for the "Connect"
OpenVPN clients via the community bug trackers (here and in GH issues).

Please resubmit - if still relevant - via ​https://support.openvpn.net/