Skip to content
Thanks a lot!
Search found 24 matches
- by tridy
- Mon Sep 02, 2024 2:06 am
- Forum: Viscosity Support (Windows Version)
- Topic: Edit Connection - Networking
- Replies: 2
- Views: 13384
Thanks!
- by tridy
- Wed Aug 21, 2024 9:16 pm
- Forum: Viscosity Support (Windows Version)
- Topic: Edit Connection - Networking
- Replies: 2
- Views: 13384
One question and two suggestions. The first question is whether in Edit Connections -> Networking it would be possible to specify a wildcard as a part of the IP address, such as 52.146.*.* or possibly a range of IP addresses to be able to route multiple addresses through VPN? Second, a suggestion to ...
- by tridy
- Thu Jan 29, 2015 9:17 am
- Forum: Viscosity Support (Windows Version)
- Topic: [Solved] IPRedator - State changed to Connecting
- Replies: 3
- Views: 7377
Fixed it by using scripting using ViscosityCC.exe commands.
http://www.sparklabs.com/forum/viewtopic.php?f=9&t=1739
http://www.sparklabs.com/forum/viewtopic.php?f=9&t=1739
- by tridy
- Thu Jan 29, 2015 9:14 am
- Forum: Viscosity Support (Windows Version)
- Topic: Request: Command Line Enhancements
- Replies: 2
- Views: 6484
Eric wrote:Please have a look at the following for some more advanced commands - http://www.sparklabs.com/support/viswin_script_control/That's really good! Managed to get a PowerShell script running every 5 minutes and checking if it's not in Connected state and then connecting.
Thanks a lot!
- by tridy
- Fri Jan 23, 2015 8:10 pm
- Forum: Viscosity Support (Windows Version)
- Topic: Request: Command Line Enhancements
- Replies: 2
- Views: 6484
Hello. Here are several things I would like to be improved in Viscocity command line: 1. Besides connect and disconnect commands (http://www.sparklabs.com/support/viswin_command_line/) also have at least status command: "... \Viscosity.exe" status "My Connection" it would be also nice to have these ...
- by tridy
- Wed Dec 31, 2014 10:37 pm
- Forum: Viscosity Support (Windows Version)
- Topic: [Solved] IPRedator - State changed to Connecting
- Replies: 3
- Views: 7377
after I have added 4 dns severs, first OpenDNS ones and then IPRedator ones, 208.67.222.222, 208.67.220.220, 194.132.32.32, 46.246.46.246 It is going back to the looping --ping-restart problem: Dec 31 12:23:18: [UNDEF] Inactivity timeout (--ping-restart), restarting Dec 31 12:23:18: SIGUSR1[soft ...
- by tridy
- Fri Dec 26, 2014 3:24 am
- Forum: Viscosity Support (Windows Version)
- Topic: [Solved] IPRedator - State changed to Connecting
- Replies: 3
- Views: 7377
Hello. I have had several issues with --ping-restart and have contacted the provider ( IPRedator ) who said that this is most likely due to the DNS problems. So, I have assigned their own DNS servers and now instead of looping the ping, the connection hangs on the "State changed to Connecting:" http ...
- by tridy
- Wed Dec 17, 2014 3:34 am
- Forum: Viscosity Support (Windows Version)
- Topic: Log Time Format
- Replies: 1
- Views: 4558
Hello. Not a show stopper but it looks like logging in Viscosity does not match the regional settings time format from the machine. here is the log from 17:16 but the log is using 05:16 http://i57.tinypic.com/osd0uc_th.png So, the best would be to match the time format from regional settings, or at ...
- by tridy
- Sat Oct 05, 2013 6:07 am
- Forum: Viscosity Support (Windows Version)
- Topic: Can't get online with V running since update
- Replies: 22
- Views: 34192
I just tried connecting to iPredator via V and it connected. What's up? Is there a bug? Thanks. I had some problems with IPRedator myself today. It was not accepting the password first, then disconnected and could not connect. Now it seems to work alright. I guess it was the problem on IPRedator ...
- by tridy
- Fri Oct 04, 2013 4:25 pm
- Forum: Viscosity Support (Windows Version)
- Topic: [Workaround] No Graph/Statistics (Hyper-V Virtual Switch)
- Replies: 4
- Views: 10233
Ok, Hyper-V Manager has Virtual Switch Manager where a virtual switch can be added or deleted. I removed Viscosity Virtual Switch and it did uncheck Hyper-V Extensible Virtual Switch and checked in TCP/IPv4 . So, now the Viscosity adapter is back to the original (prior to Hyper-V installation) state ...