Page 1 of 1

Cannot connect to any VPN

Posted: Wed Feb 13, 2019 4:04 am
by jmartin
I've been having an issue connecting since the last major release. I'm running on Windows Server 2012 R2 64 bit. This is what comes up in the logs when I try to connect to any network:
Code: Select all
Feb 12 11:52:01 AM: State changed to Connecting
Feb 12 11:52:01 AM: Viscosity Windows 1.7.15 (1598) Beta3
Feb 12 11:52:01 AM: Running on Microsoft Windows Server 2012 R2 Standard
Feb 12 11:52:01 AM: Running on .NET Framework Version 4.7.03062.461814
Feb 12 11:52:01 AM: Bringing up interface...
Feb 12 11:52:02 AM: Tue Feb 12 11:52:02 2019 WSAStartup failed: No such device or address (errno=6)
Feb 12 11:52:02 AM: Tue Feb 12 11:52:02 2019 Exiting due to fatal error

The OpenVPN subsystem could not be started. Please check the following:
- Check for any error messages above this notification.
- Ensure ViscosityService is running.
- Make sure the configuration is valid

Feb 12 11:52:03 AM: State changed to Disconnecting
Feb 12 11:52:03 AM: State changed to Disconnected
I tried installing the latest beta, 1.7.15 (1598) and it's the same result as on 1.7.14 (1595).

Re: Cannot connect to any VPN

Posted: Wed Feb 13, 2019 9:42 am
by Eric
Hi jmartin,

Please note we don't officially support Windows Server.

It looks like you have a problem with WinSock. The only major change here is that OpenVPN is now running natively as an x64 binary. I'd recommend running a repair on Windows as a first step.

Regards,
Eric

Re: Cannot connect to any VPN

Posted: Fri Apr 26, 2019 6:40 pm
by Bart
@jmartin

We have the same issue.


How did you resolve this?

Re: Cannot connect to any VPN

Posted: Tue Nov 19, 2019 11:40 pm
by davep
Is there any way to make this work? Or can anyone recommend another OpenVPN client?

I'd be happy to pay for a Server upgrade if there was some way to make Viscosity work. @jmartin?

Re: Cannot connect to any VPN

Posted: Fri Dec 20, 2019 10:39 pm
by Eric
Hi All,

With the help of another user we've managed to narrow this issue down to Windows Server setup as Domain Controllers and implemented a fix in Viscosity 1.8.4 Beta 3. Please give it a go and let us know if you continue to experience this problem:

https://sparklabs.com/support/kb/article/using-viscosity-beta-versions/

Regards,
Eric