2008R2 Support

Got a problem with Viscosity or need help? Ask here!

tbv

Posts: 3
Joined: Wed Dec 12, 2012 9:35 pm

Post by tbv » Wed Dec 12, 2012 9:37 pm
Hi Guys

I would like to use your client on a 2008R2 server however it appears it doesnt work too well (cant connect)
Works fine on my Win7 box on the same network.
Is 2008R2 supported?

Eric

User avatar
Posts: 905
Joined: Sun Jan 03, 2010 3:27 am

Post by Eric » Wed Dec 12, 2012 9:42 pm
Hi tbv,

While not officially reported, it should work fine as it has a very similar back end to Win7. Are you able to post a copy of your OpenVPN log and we can see where it is going wrong. You can find the OpenVPN log in the Details Window.

Regards,

Eric
Eric Thorpe
Viscosity Developer

Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs

tbv

Posts: 3
Joined: Wed Dec 12, 2012 9:35 pm

Post by tbv » Wed Dec 12, 2012 11:10 pm
Sure I get

Dec 12 11:07:27: State changed to Creating...
Dec 12 11:07:32: Failed to create adapter
Dec 12 11:07:32: State changed to Disconnected

Eric

User avatar
Posts: 905
Joined: Sun Jan 03, 2010 3:27 am

Post by Eric » Thu Dec 13, 2012 12:08 am
Hi tgv,

It looks like the service may not be running. Are you using the latest version 1.4.2? Can you check in the service manager to make sure Viscosity Service (Start->Run, type 'services.msc' without quotes, then right click ViscosityService and select Start).

Regards,

Eric
Eric Thorpe
Viscosity Developer

Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs

tbv

Posts: 3
Joined: Wed Dec 12, 2012 9:35 pm

Post by tbv » Sun Dec 16, 2012 10:21 pm
Yup did that it's running still nothing (I'm using the same configuration file I used on Win7) - I dont seem to be able to get the popup to appear asking for my login credentrials.

Dec 16 10:17:59: Viscosity 1.4.2 (1178)
Dec 16 10:17:59: Running on Microsoft Windows Server 2008 R2 Standard
Dec 16 10:17:59: No associated network adapter was found, creating one. This process may take up to a minute or two.
Dec 16 10:17:59: State changed to Creating...
Dec 16 10:17:59: Failed to create adapter
Dec 16 10:17:59: Network adapter created. Proceeding with connection attempt
Dec 16 10:17:59: State changed to Connecting
Dec 16 10:17:59: Bringing up interface...
Dec 16 10:17:59: A dev-node for this connection was not found in the configuration file. Viscosity will attempt to connect without one.
Dec 16 10:17:59: Checking reachability status of connection...
Dec 16 10:17:59: Connection is reachable. Starting connection attempt.
Dec 16 10:17:59: OpenVPN executable was not issued by SparkLabs and may be dangerous. Aborting.
The OpenVPN subsystem could not be started. Please check the following:
- Check for any error messages above this notification.
- Ensure Viscosity is running.
- Make sure the configuration is valid if this is a Custom Gateway.

Dec 16 10:18:10: State changed to Disconnected

Eric

User avatar
Posts: 905
Joined: Sun Jan 03, 2010 3:27 am

Post by Eric » Mon Dec 17, 2012 10:40 pm
HI tbv,

We've run up a couple of 2008R2 VMs to see if we can replicate the issue and we haven't been able to. From the logs you've posted, it looks like certificate validation on all the executables and drivers is failing. Unfortunately validation can't be turned off for security reasons. I have a faint memory of there being some problems with root CAs in Win2k8, I know a Windows Update fixed this, is you machine up to date? Also, you will need to make sure the time and date is correct (If it was incorrect at install time, you may need to Uninstall and Reinstall Viscosity).

A simple way to maybe see what is going on, go to C:\Program Files\Viscosity\Resources, right click openvpn.exe and go to the Digital Signatures tab, select Sparklabs in the list and click Details, it should say "The digital signature is OK." at the top of this window. Hopefully this will point straight away to what is failing certification (if that is the problem), otherwise a screenshot of this window would be helpful to see if anything sticks out.

Installing our certificate may also alleviate the problem (In the previous window, select View Certificate then Install Certificate) if the certificate is being verified as existent OK.

Let us know if any of this helps.

Regards,

Eric
Eric Thorpe
Viscosity Developer

Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs

daehnomel

Posts: 1
Joined: Wed Feb 27, 2013 6:22 am

Post by daehnomel » Wed Feb 27, 2013 6:32 am
I am having the same issue with my recent install of Viscosity. I'm running the latest version for windws, jsut downloaded it again today from sparklabs website. I'm running Windows 7 Enterprise and I have tried different config files, uninstalling and reinstalling and even allowing visc. to run unsafe commands, also checked the signatures in the prog files directory and all signatures, even those for .exe's in subdirectories are ok. I tried installing all of those dignatures as well, this didn't help. I've tried running openvpn 2.2 and 2.3, neither worked. Tried running program, even installing as administrator, no dice. No matter what I get the "OpenVPN executable was not issued by SparkLabs and may be dangerous" line. What's going on? Here is a copy of my logs:


Feb 26 12:51:07: State changed to Disconnected
Feb 26 12:52:09: State changed to Connecting
Feb 26 12:52:09: Viscosity 1.4.2 (1178)
Feb 26 12:52:09: Running on Microsoft Windows 7 Enterprise
Feb 26 12:52:09: No associated network adapter was found, creating one. This process may take up to a minute or two.
Feb 26 12:52:09: State changed to Creating...
Feb 26 12:52:09: Failed to create adapter
Feb 26 12:52:09: Network adapter created. Proceeding with connection attempt
Feb 26 12:52:09: State changed to Connecting
Feb 26 12:52:09: Bringing up interface...
Feb 26 12:52:09: A dev-node for this connection was not found in the configuration file. Viscosity will attempt to connect without one.
Feb 26 12:52:09: Checking reachability status of connection...
Feb 26 12:52:10: Connection is reachable. Starting connection attempt.
Feb 26 12:52:10: OpenVPN executable was not issued by SparkLabs and may be dangerous. Aborting.

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

Feb 26 12:52:20: State changed to Disconnected

Eric

User avatar
Posts: 905
Joined: Sun Jan 03, 2010 3:27 am

Post by Eric » Wed Feb 27, 2013 6:57 pm
Hi daehnomel,

Only being the second time we've seen this now, I can't say for sure. Could you please lodge a support request to [email protected] and we will send you a tool so we can try to confirm why Windows is telling Viscosity that the binaries are not signed correctly.

Regards,

Eric
Eric Thorpe
Viscosity Developer

Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs
8 posts Page 1 of 1