Windows Server 2016 OpenVPN error

This forum is for all inquiries relating to the installation of OpenVPN from source and with binaries.

Moderators: TinCanTech, TinCanTech, TinCanTech, TinCanTech, TinCanTech, TinCanTech

Forum rules
Please visit (and READ) the OpenVPN HowTo http://openvpn.net/howto prior to asking any questions in here!
Post Reply
omni
OpenVpn Newbie
Posts: 2
Joined: Wed Oct 05, 2016 4:10 pm

Windows Server 2016 OpenVPN error

Post by omni » Wed Oct 05, 2016 4:20 pm

I am running into a problem when testing OpenVPN in Windows Server 2016. I am aware that this is an unreleased OS for now, but I hope there will be a fix for this problem. The setup is a simple OpenVPN configuration with a static key, the configuration works on a non-Windows Server 2016.

After installing OpenVPN on ANY OpenVPN configuration the following error appears in the logs:
Wed Oct 05 18:10:15 2016 GetAdaptersInfo #1 failed (status=127) : The specified procedure could not be found.

For reference below the full connect log (verbosity level 3):
Wed Oct 05 18:15:37 2016 OpenVPN 2.3.12 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [PKCS11] [IPv6] built on Oct 3 2016
Wed Oct 05 18:15:37 2016 Windows version 6.2 (Windows 8 or greater) 64bit
Wed Oct 05 18:15:37 2016 library versions: OpenSSL 1.0.1u 22 Sep 2016, LZO 2.09
Wed Oct 05 18:15:37 2016 Static Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Wed Oct 05 18:15:37 2016 WARNING: this cipher's block size is less than 128 bit (64 bit). Consider using a --cipher with a larger block size.
Wed Oct 05 18:15:37 2016 Static Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Wed Oct 05 18:15:37 2016 Static Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Wed Oct 05 18:15:37 2016 WARNING: this cipher's block size is less than 128 bit (64 bit). Consider using a --cipher with a larger block size.
Wed Oct 05 18:15:37 2016 Static Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Wed Oct 05 18:15:37 2016 Socket Buffers: R=[65536->65536] S=[65536->65536]
Wed Oct 05 18:15:37 2016 GetAdaptersInfo #1 failed (status=127) : The specified procedure could not be found.
Wed Oct 05 18:15:37 2016 ROUTE_GATEWAY 10.10.0.1
Wed Oct 05 18:15:37 2016 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
Wed Oct 05 18:15:37 2016 open_tun, tt->ipv6=0
Wed Oct 05 18:15:37 2016 TAP-WIN32 device [Ethernet 2] opened: \\.\Global\{C3E7C39F-31CB-4B1E-A6A0-F506118CD957}.tap
Wed Oct 05 18:15:37 2016 TAP-Windows Driver Version 9.21
Wed Oct 05 18:15:37 2016 GetAdaptersInfo #1 failed (status=127) : The specified procedure could not be found.
Wed Oct 05 18:15:37 2016 Notified TAP-Windows driver to set a DHCP IP/netmask of 10.8.0.6/255.255.255.252 on interface {C3E7C39F-31CB-4B1E-A6A0-F506118CD957} [DHCP-serv: 10.8.0.5, lease-time: 31536000]
Wed Oct 05 18:15:37 2016 Successful ARP Flush on interface [19] {C3E7C39F-31CB-4B1E-A6A0-F506118CD957}
Wed Oct 05 18:15:37 2016 GetAdaptersInfo #1 failed (status=127) : The specified procedure could not be found.
Wed Oct 05 18:15:38 2016 UDPv4 link local (bound): [undef]
Wed Oct 05 18:15:38 2016 UDPv4 link remote: [AF_INET]89.200.112.55:1194
Wed Oct 05 18:15:46 2016 Peer Connection Initiated with [AF_INET]89.200.112.55:1194
Wed Oct 05 18:15:52 2016 GetAdaptersInfo #1 failed (status=127) : The specified procedure could not be found.
Wed Oct 05 18:15:52 2016 TEST ROUTES: 0/1 succeeded len=1 ret=0 a=0 u/d=up
Wed Oct 05 18:15:52 2016 Route: Waiting for TUN/TAP interface to come up...

After waiting for some time it does connect and gives me the ability to connect to the remote endpoint, however the route addition fails. I can't reach the network behind the OpenVPN server, only the VPN server IP itself.

Does anyone have a clue what might be wrong?

omni
OpenVpn Newbie
Posts: 2
Joined: Wed Oct 05, 2016 4:10 pm

Re: Windows Server 2016 OpenVPN error

Post by omni » Wed Oct 05, 2016 4:25 pm

UPDATE: after modifying the configuration to include:
route-delay 20 120

The following happens:
Wed Oct 05 18:20:48 2016 GetAdaptersInfo #1 failed (status=127) : The specified procedure could not be found.
Wed Oct 05 18:20:48 2016 TEST ROUTES: 0/1 succeeded len=1 ret=0 a=0 u/d=up
Wed Oct 05 18:20:48 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Oct 05 18:20:53 2016 GetAdaptersInfo #1 failed (status=127) : The specified procedure could not be found.
Wed Oct 05 18:20:53 2016 TEST ROUTES: 0/1 succeeded len=1 ret=0 a=0 u/d=up
Wed Oct 05 18:20:53 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Oct 05 18:20:54 2016 GetAdaptersInfo #1 failed (status=127) : The specified procedure could not be found.
Wed Oct 05 18:20:54 2016 TEST ROUTES: 0/1 succeeded len=1 ret=0 a=0 u/d=up
Wed Oct 05 18:20:54 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Oct 05 18:20:55 2016 GetAdaptersInfo #1 failed (status=127) : The specified procedure could not be found.
Wed Oct 05 18:20:55 2016 TEST ROUTES: 0/1 succeeded len=1 ret=0 a=0 u/d=up
Wed Oct 05 18:20:55 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Oct 05 18:20:56 2016 GetAdaptersInfo #1 failed (status=127) : The specified procedure could not be found.
Wed Oct 05 18:20:56 2016 TEST ROUTES: 0/1 succeeded len=1 ret=0 a=0 u/d=up
Wed Oct 05 18:20:56 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Oct 05 18:20:57 2016 GetAdaptersInfo #1 failed (status=127) : The specified procedure could not be found.
Wed Oct 05 18:20:57 2016 TEST ROUTES: 0/1 succeeded len=1 ret=0 a=0 u/d=up
Wed Oct 05 18:20:57 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Oct 05 18:20:58 2016 GetAdaptersInfo #1 failed (status=127) : The specified procedure could not be found.
Wed Oct 05 18:20:58 2016 TEST ROUTES: 0/1 succeeded len=1 ret=0 a=0 u/d=up
Wed Oct 05 18:20:58 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Oct 05 18:20:59 2016 GetAdaptersInfo #1 failed (status=127) : The specified procedure could not be found.
Wed Oct 05 18:20:59 2016 TEST ROUTES: 0/1 succeeded len=1 ret=0 a=0 u/d=up
Wed Oct 05 18:20:59 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Oct 05 18:21:01 2016 GetAdaptersInfo #1 failed (status=127) : The specified procedure could not be found.
Wed Oct 05 18:21:01 2016 TEST ROUTES: 0/1 succeeded len=1 ret=0 a=0 u/d=up
Wed Oct 05 18:21:01 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Oct 05 18:21:02 2016 GetAdaptersInfo #1 failed (status=127) : The specified procedure could not be found.
Wed Oct 05 18:21:02 2016 TEST ROUTES: 0/1 succeeded len=1 ret=0 a=0 u/d=up
Wed Oct 05 18:21:02 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Oct 05 18:21:03 2016 GetAdaptersInfo #1 failed (status=127) : The specified procedure could not be found.
Wed Oct 05 18:21:03 2016 TEST ROUTES: 0/1 succeeded len=1 ret=0 a=0 u/d=up
Wed Oct 05 18:21:03 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Oct 05 18:21:04 2016 GetAdaptersInfo #1 failed (status=127) : The specified procedure could not be found.
Wed Oct 05 18:21:04 2016 TEST ROUTES: 0/1 succeeded len=1 ret=0 a=0 u/d=up
Wed Oct 05 18:21:04 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Oct 05 18:21:05 2016 GetAdaptersInfo #1 failed (status=127) : The specified procedure could not be found.
Wed Oct 05 18:21:05 2016 TEST ROUTES: 0/1 succeeded len=1 ret=0 a=0 u/d=up
Wed Oct 05 18:21:05 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Oct 05 18:21:06 2016 GetAdaptersInfo #1 failed (status=127) : The specified procedure could not be found.
Wed Oct 05 18:21:06 2016 TEST ROUTES: 0/1 succeeded len=1 ret=0 a=0 u/d=up
Wed Oct 05 18:21:06 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Oct 05 18:21:07 2016 GetAdaptersInfo #1 failed (status=127) : The specified procedure could not be found.
Wed Oct 05 18:21:07 2016 TEST ROUTES: 0/1 succeeded len=1 ret=0 a=0 u/d=up
Wed Oct 05 18:21:07 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Oct 05 18:21:08 2016 GetAdaptersInfo #1 failed (status=127) : The specified procedure could not be found.
Wed Oct 05 18:21:08 2016 TEST ROUTES: 0/1 succeeded len=1 ret=0 a=0 u/d=up
Wed Oct 05 18:21:08 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Oct 05 18:21:09 2016 GetAdaptersInfo #1 failed (status=127) : The specified procedure could not be found.
Wed Oct 05 18:21:09 2016 TEST ROUTES: 0/1 succeeded len=1 ret=0 a=0 u/d=up
Wed Oct 05 18:21:09 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Oct 05 18:21:10 2016 GetAdaptersInfo #1 failed (status=127) : The specified procedure could not be found.
Wed Oct 05 18:21:10 2016 TEST ROUTES: 0/1 succeeded len=1 ret=0 a=0 u/d=up
Wed Oct 05 18:21:10 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Oct 05 18:21:11 2016 GetAdaptersInfo #1 failed (status=127) : The specified procedure could not be found.
Wed Oct 05 18:21:11 2016 TEST ROUTES: 0/1 succeeded len=1 ret=0 a=0 u/d=up
Wed Oct 05 18:21:11 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Oct 05 18:21:12 2016 GetAdaptersInfo #1 failed (status=127) : The specified procedure could not be found.
Wed Oct 05 18:21:12 2016 TEST ROUTES: 0/1 succeeded len=1 ret=0 a=0 u/d=up
Wed Oct 05 18:21:12 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Oct 05 18:21:13 2016 GetAdaptersInfo #1 failed (status=127) : The specified procedure could not be found.
Wed Oct 05 18:21:13 2016 TEST ROUTES: 0/1 succeeded len=1 ret=0 a=0 u/d=up
Wed Oct 05 18:21:13 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Oct 05 18:21:14 2016 GetAdaptersInfo #1 failed (status=127) : The specified procedure could not be found.
Wed Oct 05 18:21:14 2016 TEST ROUTES: 0/1 succeeded len=1 ret=0 a=0 u/d=up
Wed Oct 05 18:21:14 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Oct 05 18:21:16 2016 GetAdaptersInfo #1 failed (status=127) : The specified procedure could not be found.
Wed Oct 05 18:21:16 2016 TEST ROUTES: 0/1 succeeded len=1 ret=0 a=0 u/d=up
Wed Oct 05 18:21:16 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Oct 05 18:21:17 2016 GetAdaptersInfo #1 failed (status=127) : The specified procedure could not be found.
Wed Oct 05 18:21:17 2016 TEST ROUTES: 0/1 succeeded len=1 ret=0 a=0 u/d=up
Wed Oct 05 18:21:17 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Oct 05 18:21:18 2016 GetAdaptersInfo #1 failed (status=127) : The specified procedure could not be found.
Wed Oct 05 18:21:18 2016 TEST ROUTES: 0/1 succeeded len=1 ret=0 a=0 u/d=up
Wed Oct 05 18:21:18 2016 C:\Windows\system32\route.exe ADD 192.168.123.0 MASK 255.255.255.0 10.8.0.5
Wed Oct 05 18:21:18 2016 GetAdaptersInfo #1 failed (status=127) : The specified procedure could not be found.
Wed Oct 05 18:21:18 2016 Warning: route gateway is not reachable on any active network adapters: 10.8.0.5
Wed Oct 05 18:21:18 2016 Route addition via IPAPI failed [adaptive]
Wed Oct 05 18:21:18 2016 Route addition fallback to route.exe
Wed Oct 05 18:21:18 2016 env_block: add PATH=C:\Windows\System32;C:\Windows;C:\Windows\System32\Wbem
SYSTEM ROUTING TABLE
0.0.0.0 0.0.0.0 10.10.0.1 p=0 i=12 t=4 pr=3 a=2838 h=0 m=281/0/0/0/0
10.8.0.4 255.255.255.252 10.8.0.6 p=0 i=19 t=3 pr=2 a=43 h=0 m=291/0/0/0/0
10.8.0.6 255.255.255.255 10.8.0.6 p=0 i=19 t=3 pr=2 a=43 h=0 m=291/0/0/0/0
10.8.0.7 255.255.255.255 10.8.0.6 p=0 i=19 t=3 pr=2 a=43 h=0 m=291/0/0/0/0
10.10.0.0 255.255.255.0 10.10.0.102 p=0 i=12 t=3 pr=2 a=2835 h=0 m=281/0/0/0/0
10.10.0.102 255.255.255.255 10.10.0.102 p=0 i=12 t=3 pr=2 a=2835 h=0 m=281/0/0/0/0
10.10.0.255 255.255.255.255 10.10.0.102 p=0 i=12 t=3 pr=2 a=2835 h=0 m=281/0/0/0/0
127.0.0.0 255.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=2 a=2839 h=0 m=331/0/0/0/0
127.0.0.1 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=2 a=2839 h=0 m=331/0/0/0/0
127.255.255.255 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=2 a=2839 h=0 m=331/0/0/0/0
192.168.123.0 255.255.255.0 10.8.0.5 p=0 i=19 t=4 pr=3 a=295 h=0 m=36/0/0/0/0
224.0.0.0 240.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=2 a=2839 h=0 m=331/0/0/0/0
224.0.0.0 240.0.0.0 10.10.0.102 p=0 i=12 t=3 pr=2 a=2838 h=0 m=281/0/0/0/0
224.0.0.0 240.0.0.0 10.8.0.6 p=0 i=19 t=3 pr=2 a=1418 h=0 m=291/0/0/0/0
255.255.255.255 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=2 a=2839 h=0 m=331/0/0/0/0
255.255.255.255 255.255.255.255 10.10.0.102 p=0 i=12 t=3 pr=2 a=2838 h=0 m=281/0/0/0/0
255.255.255.255 255.255.255.255 10.8.0.6 p=0 i=19 t=3 pr=2 a=1418 h=0 m=291/0/0/0/0
Wed Oct 05 18:21:18 2016 GetAdaptersInfo #1 failed (status=127) : The specified procedure could not be found.
SYSTEM ADAPTER LIST
Wed Oct 05 18:21:18 2016 Initialization Sequence Completed With Errors ( see http://openvpn.net/faq.html#dhcpclientserv )

I am now able to connect to the network behind the OpenVPN server, but it does not feel right/reliable because of the error messages.

TinCanTech
OpenVPN Protagonist
Posts: 11137
Joined: Fri Jun 03, 2016 1:17 pm

Re: Windows Server 2016 OpenVPN error

Post by TinCanTech » Wed Oct 05, 2016 6:02 pm

Please ensure the Windows DHCP Client Service is enabled and started.

Post Reply