Skip to content
need to run as administrator?
Got a problem with Viscosity or need help? Ask here!
Hi. We just started using licensed Viscosity on our Thinkpads running Windows 8.1.1 x64 Pro. I checked Advanced -> Network -> Use single ..., stopped and exited V, then uninstalled under DM extra taps not usually used. When I clicked on the desktop icon to restart V I noticed I did not have Run As Administrator. However, my VPN came up fine.
Should I Run As Administrator to be able to simply auto update V? E.g., I could go to the desktop icon -> Properties -> Compatibility -> Settings -> Run this program as an administrator. Is this at all useful to running V?
I started using V because the OVPN Gui that comes with 2.3.6 fails once in a while under 8.1 (now a "known" problem). I hope V works out.
Thanks.
Should I Run As Administrator to be able to simply auto update V? E.g., I could go to the desktop icon -> Properties -> Compatibility -> Settings -> Run this program as an administrator. Is this at all useful to running V?
I started using V because the OVPN Gui that comes with 2.3.6 fails once in a while under 8.1 (now a "known" problem). I hope V works out.
Thanks.
Looking at this forum, it seems others running Windows 8.1 might be having similar problems as I had with OpenVPN GUI version 2.3.6 and privatetunnel version 2.4 which also uses OVPN-2.3.6 (same authors).
I had tried securepoint.sf.net and did not have this problem, but a simple test in their `.../bin/openvpn.exe --version` showed they are still on version 2.3.3, which had not addressed the security issues fixed by later versions. Also, there forum is quite sparse, so they are not gathering as much feedback as other versions of the GUI.
I'm guessing this is a problem caused by version 2.3.6. I have not yet had a problem with Viscosity, but now I would not be surprised to see the problems arise.
I had tried securepoint.sf.net and did not have this problem, but a simple test in their `.../bin/openvpn.exe --version` showed they are still on version 2.3.3, which had not addressed the security issues fixed by later versions. Also, there forum is quite sparse, so they are not gathering as much feedback as other versions of the GUI.
I'm guessing this is a problem caused by version 2.3.6. I have not yet had a problem with Viscosity, but now I would not be surprised to see the problems arise.
Hi ingber,
Viscosity is designed so it does not need to be run with Administrator privileges.
The major known bug with Windows 8.1 is it can occasional have problems automatically configuration the TAP adapter when connecting. Viscosity detects this and sets up the adapter if this occurs itself to prevent a problem arising.
Regards,
Eric
Viscosity is designed so it does not need to be run with Administrator privileges.
The major known bug with Windows 8.1 is it can occasional have problems automatically configuration the TAP adapter when connecting. Viscosity detects this and sets up the adapter if this occurs itself to prevent a problem arising.
Regards,
Eric
Eric Thorpe
Viscosity Developer
Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs
Viscosity Developer
Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs
Hi ingber,
Viscosity will disconnect any active connections itself when you reboot or exit Viscosity.
Regards,
Eric
Viscosity will disconnect any active connections itself when you reboot or exit Viscosity.
Regards,
Eric
Eric Thorpe
Viscosity Developer
Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs
Viscosity Developer
Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs
5 posts
Page 1 of 1