VPN Connection Working on Mac but fails on Windows

[jebentier]

Hey everyone, I've been using viscosity for a while now on my Mac to connect to my work vpn and everything has been working great. Just recently built a new Windows machine and am wanting to connect in to the same vpn with it so I exported the connection and imported it in to my Windows machine but when I try to connect it sits and thinks about it for a second and then disconnects. The connection log looks as follows:

Code: Select all

Aug 19 09:35:28: State changed to Connecting
Aug 19 09:35:28: Viscosity 1.3.7 (1143)
Aug 19 09:35:28: Running on Microsoft Windows 7 Professional
Aug 19 09:35:28: Checking reachability status of connection...
Aug 19 09:35:29: Connection is reachable. Starting connection attempt.
Aug 19 09:35:29: Bringing up interface
Aug 19 09:35:29: OpenVPN 2.2.2 Win32-MSVC++ [SSL] [LZO2] [PKCS11] built on Jan  4 2012
Aug 19 09:35:33: WARNING: Make sure you understand the semantics of --tls-remote before using it (see the man page).
Aug 19 09:35:33: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Aug 19 09:35:33: Control Channel Authentication: using 'ta.key' as a OpenVPN static key file
Aug 19 09:35:33: LZO compression initialized
Aug 19 09:35:33: Attempting to establish TCP connection with 209.234.185.191:443
Aug 19 09:35:33: TCP connection established with 209.234.185.191:443
Aug 19 09:35:33: TCPv4_CLIENT link local: [undef]
Aug 19 09:35:33: TCPv4_CLIENT link remote: 209.234.185.191:443
Aug 19 09:35:36: [office] Peer Connection Initiated with 209.234.185.191:443
Aug 19 09:35:39: WARNING: Make sure you understand the semantics of --tls-remote before using it (see the man page).
Aug 19 09:35:39: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Aug 19 09:35:39: Control Channel Authentication: using 'ta.key' as a OpenVPN static key file
Aug 19 09:35:39: LZO compression initialized
Aug 19 09:35:39: Attempting to establish TCP connection with 209.234.185.191:443
Aug 19 09:35:39: TCP connection established with 209.234.185.191:443
Aug 19 09:35:39: TCPv4_CLIENT link local: [undef]
Aug 19 09:35:39: TCPv4_CLIENT link remote: 209.234.185.191:443
Aug 19 09:35:39: [office] Peer Connection Initiated with 209.234.185.191:443
Aug 19 09:35:39: There is a problem in your selection of --ifconfig endpoints [local=172.17.20.128, remote=172.17.20.129].  The local and remote VPN endpoints cannot use the first or last address within a given 255.255.255.252 subnet.  This is a limitation of --dev tun when used with the TAP-WIN32 driver.  Try 'openvpn --show-valid-subnets' option for more info.
Aug 19 09:35:39: Exiting
Aug 19 09:35:40: State changed to Disconnected


Has anyone come across this before, and if so what configuration changes are needed to be made to resolve the issue?

Thank you in advance for the help.

[Eric]

Hi jebentier,

Unlike Mac's, Windows cannot use every IP address in a range of 0-255. Basically, your VPN server is giving out an IP address that is not valid for Windows. We recommend you contact your VPN Provider for this. If you're not sure who your VPN Provider is, please see - http://thesparklabs.com/support/how_do_ ... _my_vpn_p/

If this is your VPN Server, you will need to widen the subnets you use for Windows.

Regards,

Eric