Viscosity 1.5.3 (or lower) : connection time is very long

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

s.allain

Posts: 4
Joined: Fri Aug 20, 2010 6:45 pm

Post by s.allain » Tue Jan 06, 2015 1:06 am
Hi all@Sparklabs Forum,

I met a main trouble with Viscosity 1.5.3 (or lower also) :
Code: Select all
janv. 05 02:24:08: Running on Microsoft Windows 7 Édition Familiale Premium 
janv. 05 02:24:10: Bringing up interface...
janv. 05 02:26:07: Vérification du statut d'accessibilité de la connexion ...
janv. 05 02:26:48: La connexion est accessible. Tentative de démarrage de la connexion.
janv. 05 02:26:49: OpenVPN 2.3.6 Windows-MSVC [SSL (OpenSSL)] [LZO] [PKCS11] [IPv6] built on Dec  2 2014
janv. 05 02:26:49: library versions: OpenSSL 1.0.1j 15 Oct 2014, LZO 2.06
janv. 5 02:27:00: Control Channel Authentication: using 'C:\Program Files\Common Files\Viscosity\OpenVPNConfig\sa\1\ta.key' as a OpenVPN static key file
janv. 5 02:27:00: UDPv4 link local (bound): [undef]
janv. 5 02:27:00: UDPv4 link remote: [AF_INET]194.X.Z.Y:443
janv. 5 02:27:02: [www.domaintest.fr] Peer Connection Initiated with [AF_INET]194.X.Z.Y:443
janv. 5 02:27:05: do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
janv. 5 02:27:05: open_tun, tt->ipv6=0
janv. 5 02:27:05: TAP-WIN32 device [VPN1_CUSTOMER_NAME] opened: \\.\Global\{A0C95F2F-FB0F-4A21-8947-1085C8B81D92}.tap
janv. 5 02:27:05: Notified TAP-Windows driver to set a DHCP IP/netmask of 10.0.10.150/255.255.255.252 on interface {A0C95F2F-FB0F-4A21-8947-1085C8B81D92} [DHCP-serv: 10.0.10.149, lease-time: 31536000]
janv. 5 02:27:05: Successful ARP Flush on interface [16] {A0C95F2F-FB0F-4A21-8947-1085C8B81D92}
janv. 5 02:27:11: Initialization Sequence Completed
janv. 05 02:28:17: State changed to Connected
4 minutes to complete !!!

The same test under Mac OS X takes only a couple of seconds....

Viscosity Windows is running inside a Parallels Desktop VM : could it be a possible side effect ? As far as I remenber, it wasn't so long a couple of months ago (the last time I used this VPN...)

Thanks a lot for all and replies !

Bye

Eric

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

Post by Eric » Tue Jan 06, 2015 11:26 am
Hi s.allain,

This issue is certainly with Windows or another piece of software. All the time lost is where Windows is required to setup or run a system related function. This shouldn't be a side effect of parallels, but might be a problem with your Windows install (A virus or corrupt system packages for example), or a security suite/program blocking access to the Viscosity adapters.

Please try disabling any other security software you have and see if the problem persists. If it does, I'm afraid the only thing we can recommend is a refresh of Windows.

Regards,
Eric
Eric Thorpe
Viscosity Developer

Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs
2 posts Page 1 of 1