Search found 995 matches

Search found 995 matches Page 5 of 100
by Eric
Sat Apr 25, 2020 12:48 am
Forum: Viscosity Support (Windows Version)
Topic: Internet Connection drops when Viscosity tries to connect
Replies: 3
Views: 6033

Hi ranlan, Please refer to the troubleshooting guide in my previous post in this case. It's also possible that something is wrong with the server you're connecting to and it's not allowing any traffic to flow. We would recommend contacting your VPN Provider for assistance - https://sparklabs.com/sup...
by Eric
Fri Apr 24, 2020 9:25 pm
Forum: Viscosity Support (Windows Version)
Topic: Internet Connection drops when Viscosity tries to connect
Replies: 3
Views: 6033

Hi ranlan, Could you clarify if your connection drops as soon as you click connect, or when Viscosity completes it's connection? Please first check if you have any scripts attached to this connection by editing your connection and going to Advanced. If not, I would advise trying to line up an event ...
by Eric
Tue Apr 21, 2020 5:47 pm
Forum: Viscosity Support (Windows Version)
Topic: DNS gets messed up sometimes
Replies: 7
Views: 7047

Hi nsumner, It sounds like 127.0.0.1 is still lingering in the system from an old version of Viscosity. Please refer to my previous instructions for users who experience this to reset their network settings if other users experience this. As of version 1.8.5, Viscosity no longer uses 127.0.0.1. As a...
by Eric
Fri Apr 17, 2020 11:13 am
Forum: Viscosity Feedback
Topic: Request: Split tunneling based on Application
Replies: 7
Views: 27604

Hi crimple,

We still do have plans to add this feature eventually. Please see the following in the mean time:
https://sparklabs.com/support/kb/articl ... s-for-this

Regards,
Eric
by Eric
Thu Apr 16, 2020 12:01 pm
Forum: Viscosity Support (Windows Version)
Topic: Kill switch?
Replies: 6
Views: 7686

Hi Aybee, Unless your PC is setup to ignore services and applications shutting down gracefully, these scripts should still be run when the PC is shut down. The exception to this is if you forcefully shutdown/power off or bluescreen, of which case a kill script/switch will never work, I'd recommend l...
by Eric
Thu Apr 16, 2020 11:57 am
Forum: Viscosity Support (Windows Version)
Topic: Script Problem
Replies: 10
Views: 8175

Hi Aybee, Please ensure that "Automatically reconnect if disconnected" is ticked in Edit Connection -> General. A part from this, if you want a much more aggressive connection policy, you may with to look at scripting this yourself - https://sparklabs.com/support/kb/article/controlling-viscosity-wit...
by Eric
Wed Apr 15, 2020 11:47 am
Forum: Viscosity Support (Windows Version)
Topic: DNS Issues
Replies: 1
Views: 4144

Hi Alexalex, We have some information here which I recommend running through to ensure your connections are configured correctly - https://sparklabs.com/support/kb/article/preventing-network-and-dns-traffic-leaks/#preventing-dns-leaks If you're still noticing leaks, I recommend trying to narrow down...
by Eric
Wed Apr 15, 2020 11:44 am
Forum: Viscosity Support (Windows Version)
Topic: Script Problem
Replies: 10
Views: 8175

Hi Aybee, Did you try the example ping script I posted earlier? As I have mentioned, I'm afraid the issue here is most likely with your script or lack of elevation. If your script is using a task host to elevate itself and then exit immediately, Viscosity will also think that the script has finished...
by Eric
Tue Apr 14, 2020 4:42 pm
Forum: Viscosity Support (Windows Version)
Topic: Script Problem
Replies: 10
Views: 8175

Hi Aybee, These commands require Admin rights to execute and Viscosity does not run elevated. This is most likely why they appear to not be waiting and then your adapter appears to be disabled again, when instead what is happening is both commands are failing to run. You have a couple of options. Yo...
by Eric
Tue Apr 14, 2020 4:26 pm
Forum: Viscosity Support (Windows Version)
Topic: Script Problem
Replies: 10
Views: 8175

Hi Aybee, If you would like to confirm Viscosity is waiting, please try setting the following script as your Before Connect script: ping 127.0.0.1 -n 6 > nul echo ViscosityNoConnect You should see the following in your log, note the 5 second delay between the .NET Framework version and the disconnec...
Search found 995 matches Page 5 of 100