unable to authenticate connection

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

Flagonslayer

Posts: 1
Joined: Wed Aug 22, 2018 9:40 am

Post by Flagonslayer » Wed Aug 22, 2018 9:46 am
Hello,

I have two computers with Viscosity. One works, the other connects but now fails to authenticate. Attached is the log from the troubled computer:

Aug 21 6:23:32 PM: State changed to Connecting
Aug 21 6:23:32 PM: Viscosity Windows 1.7.7 (1549)
Aug 21 6:23:32 PM: Running on Microsoft Windows 8
Aug 21 6:23:32 PM: Running on .NET Framework Version 4.6.01590.394806
Aug 21 6:23:32 PM: Bringing up interface...
Aug 21 6:23:32 PM: WARNING: The block-outside-dns option has been ignored as it is not required under Viscosity's DNS management system. For more information please see the following article: https://www.sparklabs.com/support/kb/ar ... n-ignored/
Aug 21 6:23:33 PM: Note: option tun-ipv6 is ignored because modern operating systems do not need special IPv6 tun handling anymore.
Aug 21 6:23:33 PM: OpenVPN 2.4.4 Windows-MSVC [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Dec 18 2017
Aug 21 6:23:33 PM: library versions: OpenSSL 1.0.2n 7 Dec 2017, LZO 2.09
Aug 21 6:23:33 PM: Checking remote host "vpngatev4.cryptohippie.net" is reachable...
Aug 21 6:23:33 PM: Server reachable. Connecting to 46.19.136.180.
Aug 21 6:23:34 PM: Initializing OpenSSL support for engine 'dynamic'
Aug 21 6:23:34 PM: WARNING: ignoring --remote-random-hostname because the hostname is an IP address
Aug 21 6:23:34 PM: TCP/UDP: Preserving recently used remote address: [AF_INET]46.19.136.180:1194
Aug 21 6:23:34 PM: UDP link local: (not bound)
Aug 21 6:23:34 PM: UDP link remote: [AF_INET]46.19.136.180:1194
Aug 21 6:23:34 PM: State changed to Authenticating
Aug 21 6:23:36 PM: [server-001-20180629.vpngatev4.cryptohippie.net] Peer Connection Initiated with [AF_INET]46.19.136.180:1194
Aug 21 6:23:37 PM: State changed to Connecting
Aug 21 6:23:37 PM: Options error: Unrecognized option or missing or extra parameter(s) in [PUSH-OPTIONS]:7: redirect-gateway-ipv6 (2.4.4)
Aug 21 6:23:37 PM: Note: option tun-ipv6 is ignored because modern operating systems do not need special IPv6 tun handling anymore.
Aug 21 6:23:37 PM: Note: option tun-ipv6 is ignored because modern operating systems do not need special IPv6 tun handling anymore.
Aug 21 6:23:37 PM: open_tun
Aug 21 6:23:37 PM: TAP-WIN32 device [Cryptohippie4 Fast v4 (beta)] opened: \\.\Global\{823E8D4A-9FD0-4303-8AA4-67C869AF656D}.tap
Aug 21 6:23:37 PM: Notified TAP-Windows driver to set a DHCP IP/netmask of 7.3.7.6/255.255.255.252 on interface {823E8D4A-9FD0-4303-8AA4-67C869AF656D} [DHCP-serv: 7.3.7.5, lease-time: 31536000]
Aug 21 6:23:37 PM: Successful ARP Flush on interface [30] {823E8D4A-9FD0-4303-8AA4-67C869AF656D}
Aug 21 6:23:37 PM: do_ifconfig, tt->did_ifconfig_ipv6_setup=1
Aug 21 6:23:38 PM: NETSH: C:\Windows\system32\netsh.exe interface ipv6 set address interface=30 fd9e:4849:97af:3::11c1 store=active
Aug 21 6:23:38 PM: add_route_ipv6(fd9e:4849:97af:3::/64 -> fd9e:4849:97af:3::11c1 metric 0) dev Cryptohippie4 Fast v4 (beta)
Aug 21 6:23:38 PM: env_block: add PATH=C:\Windows\System32;C:\Windows;C:\Windows\System32\Wbem
Aug 21 6:23:41 PM: add_route_ipv6(2000::/3 -> fd9e:4849:97af:3::2 metric -1) dev Cryptohippie4 Fast v4 (beta)
Aug 21 6:23:41 PM: env_block: add PATH=C:\Windows\System32;C:\Windows;C:\Windows\System32\Wbem
Aug 21 6:23:41 PM: add_route_ipv6(fd9e:4849:97af::/48 -> fd9e:4849:97af:3::2 metric -1) dev Cryptohippie4 Fast v4 (beta)
Aug 21 6:23:41 PM: env_block: add PATH=C:\Windows\System32;C:\Windows;C:\Windows\System32\Wbem
Aug 21 6:23:41 PM: WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Aug 21 6:23:41 PM: Initialization Sequence Completed
Aug 21 6:23:50 PM: DNS set to Full:
Server - 7.0.0.1:53; Lookup Type - Any; Domains - cryptohippie.net.
Server - 7.0.0.2:53; Lookup Type - Any; Domains - cryptohippie.net.

Aug 21 6:23:50 PM: State changed to Connected

Eric

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

Post by Eric » Wed Aug 22, 2018 12:47 pm
Hi Flagonslayer,

Most VPN Providers only allow you to connect to one server, or with one device at a time. You will need to contact your VPN Provider for more information and assistance with this - https://sparklabs.com/support/kb/articl ... ovider-is/

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