SparkLabs Forum.

Community Help.

Unable to Connect

We are unable establish a VPN connection on a machine running Viscosity 1.6.1 where we have verified that multiple VPN configurations, which able to connect successfully from other computers, are unable to connect successfully. We are receiving an error in the VPN log stating that there is a problem activating the interface.

The full log is attached here:

Feb 24 12:19:21 PM: State changed to Creating...
Feb 24 12:19:56 PM: State changed to Disconnected
Feb 24 12:20:36 PM: State changed to Connecting
Feb 24 12:20:36 PM: Viscosity Windows 1.6.1 (1419)
Feb 24 12:20:36 PM: Running on Microsoft Windows 7 Home Premium
Feb 24 12:20:36 PM: Bringing up interface...
Feb 24 12:20:36 PM: There was a problem activing the interface, Viscosity will attempt to repair it. This process may take a minute or two.
Feb 24 12:20:36 PM: Please try the following if this problem persists: ... s-windows/
Feb 24 12:20:36 PM: State changed to Creating...
Feb 24 12:20:40 PM: Unable to repair interface, cancelling connection attempt.
Feb 24 12:20:40 PM: Please try the following if this problem persists: ... s-windows/
Feb 24 12:20:40 PM: State changed to Disconnected

I have reviewed the knowledgebase article on troubleshooting VPN problems and have been unable to resolve the issue. Steps taken so far have been to uninstall the antivirus software (AVG) and reinstall Viscosity.

Any help that you can provide would be greatly appreciated. The user of this particular machine will be out of the office tomorrow and was counting on being able to utilize the VPN while away,
Hi inBlue_SDA,

Please go to the Device Manager -> Network Adapters. Are there Unknown Devices or Viscosity Virtual Adapters listed here? If Viscosity Virtual Adapters, right click one and select properties. Enable the device and please post what the Device Status is.

There are two Viscosity Virtual Adapters, listed as follows:

Viscosity Virtual Adapter V9.1
Viscosity Virtual Adapter V9.1 #2

Upon enabling either one, the following device status is displayed:

Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)

I then performed an "Update Driver" and determined that by browsing for the Viscosity Virtual Adapter V9.1 and reinstalling it, the issue seems to be resolved.

Thank you for your assistance,

Hi Scott,

Please see the following: ... tap-device

4 posts Page 1 of 1

Copyright © 2016 SparkLabs Pty Ltd. All Rights Reserved. Privacy Policy