Viscosity via RDS (Terminalserver)

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

Umpf

Posts: 2
Joined: Thu Jul 16, 2015 11:41 pm

Post by Umpf » Thu Jul 16, 2015 11:46 pm
Hello there,

we're actually using an 2008 Terminalserver (RDS) for remote connection to our customers.
We've installed OpenVPN/TUN-TAP driver and using ovpn-files to connect.

This is very unconfortable to our employees so we're searching for a better solution.

So i installed viscosity (trial) and can connect wie rdp/rds to a sophos utm firewall (SSL-VPN). Works great.
But if another user will handle a connection to a different customer, the existing (my) one gets dropped.
I've created several "nic"-instances, the option to use one single nic for all connections is not ticked.

So what to do in an multiuser environment?

And how about the license details/ordering?

Thx in advance,

Manuel

Eric

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

Post by Eric » Mon Jul 20, 2015 9:59 am
Hi Umpf,

I'm afraid you're in a trick situation here with a shared box. When you connect for the first time, Viscosity needs to create a new adapter for that connection. This causes any other adapters installed on the system to 'cycle', which will cause any other users connections to drop. Using Single Adapter mode will help alleviate this slightly as there will only be a need to create an adapter once and it will be reused for all other connections for that user, but this will not resolve the issue machine wide.

You can take some control of the adapter away from Viscosity to almost alleviate the issues completely, but this will also remove a lot of monitoring, debuging and failsafe control from Viscosity as it will not know which adapter is in use by the connection all the time. If you would like some more information on this, please send us an email as it could require some back and forth and some testing.
https://www.sparklabs.com/support/#contact

I'm afraid Viscosity was not designed for multiuser environments like this.

In regards to licensing, please see the following - http://www.sparklabs.com/support/using_your_license_on_multiple_computers/

Regards,
Eric
Eric Thorpe
Viscosity Developer

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

Umpf

Posts: 2
Joined: Thu Jul 16, 2015 11:41 pm

Post by Umpf » Mon Jul 20, 2015 6:31 pm
Hello Eric,

thanks for the infos.
I've hoped, that we can resolve our current rds issues with the native OpenVPN-Client/GUI and the AddTAP.bat file with a more comfortable solution.
Sometimes Viscosity works flawlessly but then theres some issues where a new user connects and existing users (with an already enabled vpn) are dropped. They're "stealing" each others connection/adapter. I cannot resolve this, even when i add a new adapter for each connection and each user.

But i'll buy a license for my own notebook because working in more than one tunnel (customer LANs) at a time is a big enhancement over the native client, Thx.
3 posts Page 1 of 1