I don't get it. :?

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

Sphalerite

Posts: 2
Joined: Mon Feb 01, 2021 5:43 am

Post by Sphalerite » Mon Feb 01, 2021 6:39 am
Hi.

At first Viscosity worked fine for me. :)
But after not using it for about four month, I can't connect to any
of my VPN servers anymore. (The same profiles are working when using the official
OpenVPN community client within the same Windows 10 installation.) :(

I've tried reinstalling Viscosity. (v1.9 and alternatively also latest v1.9.1 (1704) Beta8)
Tried deactivating Kaspersky.
Switched adapter type back and forth.
Tried using a single adapter instead of one for each connection.
De- and reactivated .NET 3.5 and 4.8.

Nothing really changed the behaviour of Viscosity.

Logs with anonymized server IPs.

Using Viscosity Virtual Adapter:
Jan 31 7:49:59 : Status auf Verbinde geändert
Jan 31 7:49:59 : Viscosity Windows 1.9 (1695)
Jan 31 7:49:59 : Betriebsystem ist Windows 10 2004 (19041) 64 bit
Jan 31 7:49:59 : Betriebsystem ist .NET Framework Version 4.8.04084.528372
Jan 31 7:49:59 : Checking reachability status of connection...
Jan 31 7:49:59 : Connection is reachable. Starting connection attempt.
Jan 31 7:49:59 : Aktivieren des Netzwerkadapters...
Jan 31 7:49:59 : OpenVPN 2.4.9 Windows-MSVC [SSL (OpenSSL)] [LZO] [LZ4] [AEAD] built on Oct 6 2020
Jan 31 7:49:59 : library versions: OpenSSL 1.1.1h 22 Sep 2020, LZO 2.10
Jan 31 7:50:00 : Valid endpoint found: 185.xxx.xxx.xx:xxxx:udp
Jan 31 7:50:00 : Outgoing Control Channel Encryption: Cipher 'AES-256-CTR' initialized with 256 bit key
Jan 31 7:50:00 : Outgoing Control Channel Encryption: Using 256 bit message hash 'SHA256' for HMAC authentication
Jan 31 7:50:00 : Incoming Control Channel Encryption: Cipher 'AES-256-CTR' initialized with 256 bit key
Jan 31 7:50:00 : Incoming Control Channel Encryption: Using 256 bit message hash 'SHA256' for HMAC authentication
Jan 31 7:50:00 : TCP/UDP: Preserving recently used remote address: [AF_INET]185.xxx.xxx.xx:xxxx
Jan 31 7:50:00 : Socket Buffers: R=[65536->65536] S=[65536->65536]
Jan 31 7:50:00 : UDP link local: (not bound)
Jan 31 7:50:00 : UDP link remote: [AF_INET]185.xxx.xxx.xx:xxxx
Jan 31 7:50:00 : Status auf Authenticating geändert
Jan 31 7:50:00 : TLS: Initial packet from [AF_INET]185.xxx.xxx.xx:xxxx, sid=63d4228c 2343da7d
Jan 31 7:50:00 : VERIFY KU OK
Jan 31 7:50:00 : Validating certificate extended key usage
Jan 31 7:50:00 : ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
Jan 31 7:50:00 : VERIFY EKU OK
Jan 31 7:50:00 : VERIFY X509NAME OK: CN=server_TFXu2vFUjOJL30Xd
Jan 31 7:50:00 : VERIFY OK: depth=0, CN=server_TFXu2vFUjOJL30Xd
Jan 31 7:50:00 : Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, 256 bit EC, curve: prime256v1
Jan 31 7:50:00 : [server_TFXu2vFUjOJL30Xd] Peer Connection Initiated with [AF_INET]185.xxx.xxx.xx:xxxx
Jan 31 7:50:00 : Status auf Verbinde geändert
Jan 31 7:50:00 : SENT CONTROL [server_TFXu2vFUjOJL30Xd]: 'PUSH_REQUEST' (status=1)
Jan 31 7:50:00 : PUSH: Received control message: 'PUSH_REPLY,dhcp-option DNS 1.0.0.1,dhcp-option DNS 1.1.1.1,redirect-gateway def1 bypass-dhcp,tun-ipv6,route-ipv6 2000::/3,redirect-gateway ipv6,tun-ipv6,route-gateway 10.8.0.1,topology subnet,ping 10,ping-restart 120,ifconfig-ipv6 fd42:42:42:42::1001/112 fd42:42:42:42::1,ifconfig 10.8.0.3 255.255.255.0,peer-id 0,cipher AES-128-GCM'
Jan 31 7:50:00 : OPTIONS IMPORT: timers and/or timeouts modified
Jan 31 7:50:00 : OPTIONS IMPORT: --ifconfig/up options modified
Jan 31 7:50:00 : OPTIONS IMPORT: route options modified
Jan 31 7:50:00 : OPTIONS IMPORT: route-related options modified
Jan 31 7:50:00 : OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Jan 31 7:50:00 : OPTIONS IMPORT: peer-id set
Jan 31 7:50:00 : OPTIONS IMPORT: adjusting link_mtu to 1624
Jan 31 7:50:00 : OPTIONS IMPORT: data channel crypto options modified
Jan 31 7:50:00 : Outgoing Data Channel: Cipher 'AES-128-GCM' initialized with 128 bit key
Jan 31 7:50:00 : Incoming Data Channel: Cipher 'AES-128-GCM' initialized with 128 bit key
Jan 31 7:50:00 : interactive service msg_channel=0
Jan 31 7:50:00 : ROUTE_GATEWAY 192.168.0.100/255.255.255.0 I=27 HWADDR=70:85:c2:3e:e2:67
Jan 31 7:50:00 : GDG6: remote_host_ipv6=n/a
Jan 31 7:50:00 : NOTE: GetBestInterfaceEx returned error: Element nicht gefunden. (code=1168)
Jan 31 7:50:00 : ROUTE6: default_gateway=UNDEF
Jan 31 7:50:00 : Awaiting adapter to come up...
Jan 31 7:50:00 : WARNING: Failed to get IPv4 interface information for MTU. This warning can be ignored if this stack is disabled. Element nicht gefunden
Jan 31 7:50:00 : WARNING: Failed to get IPv6 interface information for MTU. This warning can be ignored if this stack is disabled. Element nicht gefunden
Jan 31 7:50:00 : TAP-WIN32 device [] opened: \\?\root#net#0000#{adda4c48-c32e-4ef6-9602-b3252f082583}, index: -1
Jan 31 7:50:00 : Netsh method failed. Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
Jan 31 7:50:00 : Failed to process command >DO_IPCONFIG6:fd42:42:42:42::1001,(null). Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
Jan 31 7:50:00 : NOTE: FlushIpNetTable failed on interface [8] {2312875A-7532-4E40-B9E3-88ADF361E566} (status=1168) : Element nicht gefunden.
Jan 31 7:50:01 : add_route_ipv6(fd42:42:42:42::/112 -> fd42:42:42:42::1001 metric 0) dev benpc_denise
Jan 31 7:50:01 : Route addition via IPAPI failed. Fallback to netsh.exe
Jan 31 7:50:01 : ROUTE: IPv6 route addition failed using management: Element nicht gefunden. [status=1168 if_index=8]
Jan 31 7:50:06 : TEST ROUTES: 0/1 succeeded len=0 ret=0 a=0 u/d=up
Jan 31 7:50:06 : Route: Waiting for TUN/TAP interface to come up...
Jan 31 7:50:11 : TEST ROUTES: 0/1 succeeded len=0 ret=0 a=0 u/d=up
Jan 31 7:50:11 : Route: Waiting for TUN/TAP interface to come up...
Jan 31 7:50:12 : TEST ROUTES: 0/1 succeeded len=0 ret=0 a=0 u/d=up
Jan 31 7:50:12 : Route: Waiting for TUN/TAP interface to come up...
Jan 31 7:50:13 : TEST ROUTES: 0/1 succeeded len=0 ret=0 a=0 u/d=up
Jan 31 7:50:13 : Route: Waiting for TUN/TAP interface to come up...
Jan 31 7:50:14 : TEST ROUTES: 0/1 succeeded len=0 ret=0 a=0 u/d=up
Jan 31 7:50:14 : Route: Waiting for TUN/TAP interface to come up...
Jan 31 7:50:15 : TEST ROUTES: 0/1 succeeded len=0 ret=0 a=0 u/d=up
Jan 31 7:50:15 : Route: Waiting for TUN/TAP interface to come up...
Jan 31 7:50:16 : TEST ROUTES: 0/1 succeeded len=0 ret=0 a=0 u/d=up
Jan 31 7:50:16 : Route: Waiting for TUN/TAP interface to come up...
Jan 31 7:50:18 : TEST ROUTES: 0/1 succeeded len=0 ret=0 a=0 u/d=up
Jan 31 7:50:18 : Route: Waiting for TUN/TAP interface to come up...
Jan 31 7:50:19 : TEST ROUTES: 0/1 succeeded len=0 ret=0 a=0 u/d=up
Jan 31 7:50:19 : Route: Waiting for TUN/TAP interface to come up...
Jan 31 7:50:20 : TEST ROUTES: 0/1 succeeded len=0 ret=0 a=0 u/d=up
Jan 31 7:50:20 : Route: Waiting for TUN/TAP interface to come up...
Jan 31 7:50:20 : TEST ROUTES: 0/1 succeeded len=0 ret=0 a=0 u/d=up
Jan 31 7:50:20 : Route: Waiting for TUN/TAP interface to come up...
Jan 31 7:50:21 : TEST ROUTES: 0/1 succeeded len=0 ret=0 a=0 u/d=up
Jan 31 7:50:21 : Route: Waiting for TUN/TAP interface to come up...
Jan 31 7:50:23 : TEST ROUTES: 0/1 succeeded len=0 ret=0 a=0 u/d=up
Jan 31 7:50:23 : Route: Waiting for TUN/TAP interface to come up...
Jan 31 7:50:24 : TEST ROUTES: 0/1 succeeded len=0 ret=0 a=0 u/d=up
Jan 31 7:50:24 : Route: Waiting for TUN/TAP interface to come up...
Jan 31 7:50:25 : TEST ROUTES: 0/1 succeeded len=0 ret=0 a=0 u/d=up
Jan 31 7:50:25 : Route: Waiting for TUN/TAP interface to come up...
Jan 31 7:50:26 : TEST ROUTES: 0/1 succeeded len=0 ret=0 a=0 u/d=up
Jan 31 7:50:26 : Route: Waiting for TUN/TAP interface to come up...
Jan 31 7:50:28 : TEST ROUTES: 0/1 succeeded len=0 ret=0 a=0 u/d=up
Jan 31 7:50:28 : Route: Waiting for TUN/TAP interface to come up...
Jan 31 7:50:29 : TEST ROUTES: 0/1 succeeded len=0 ret=0 a=0 u/d=up
Jan 31 7:50:29 : Route: Waiting for TUN/TAP interface to come up...
Jan 31 7:50:30 : TEST ROUTES: 0/1 succeeded len=0 ret=0 a=0 u/d=up
Jan 31 7:50:30 : Route: Waiting for TUN/TAP interface to come up...
Jan 31 7:50:31 : TEST ROUTES: 0/1 succeeded len=0 ret=0 a=0 u/d=up
Jan 31 7:50:31 : Route: Waiting for TUN/TAP interface to come up...
Jan 31 7:50:32 : TEST ROUTES: 0/1 succeeded len=0 ret=0 a=0 u/d=up
Jan 31 7:50:32 : Route: Waiting for TUN/TAP interface to come up...
Jan 31 7:50:33 : TEST ROUTES: 0/1 succeeded len=0 ret=0 a=0 u/d=up
Jan 31 7:50:33 : Route: Waiting for TUN/TAP interface to come up...
Jan 31 7:50:34 : TEST ROUTES: 0/1 succeeded len=0 ret=0 a=0 u/d=up
Jan 31 7:50:34 : Route: Waiting for TUN/TAP interface to come up...
Jan 31 7:50:35 : TEST ROUTES: 0/1 succeeded len=0 ret=0 a=0 u/d=up
Jan 31 7:50:35 : C:\WINDOWS\system32\route.exe ADD 185.xxx.xxx.xx MASK 255.255.255.255 192.168.0.100
Jan 31 7:50:35 : IPv4 Route addition via management succeeded
Jan 31 7:50:35 : C:\WINDOWS\system32\route.exe ADD 0.0.0.0 MASK 128.0.0.0 10.8.0.1
Jan 31 7:50:35 : Warning: route gateway is not reachable on any active network adapters: 10.8.0.1
Jan 31 7:50:35 : C:\WINDOWS\system32\route.exe ADD 128.0.0.0 MASK 128.0.0.0 10.8.0.1
Jan 31 7:50:35 : Warning: route gateway is not reachable on any active network adapters: 10.8.0.1
Jan 31 7:50:35 : add_route_ipv6(2000::/3 -> fd42:42:42:42::1 metric -1) dev benpc_denise
Jan 31 7:50:35 : Route addition via IPAPI failed. Fallback to netsh.exe
Jan 31 7:50:35 : ROUTE: IPv6 route addition failed using management: Element nicht gefunden. [status=1168 if_index=8]
Jan 31 7:50:35 : add_route_ipv6(::/3 -> fd42:42:42:42::1 metric -1) dev benpc_denise
Jan 31 7:50:35 : Route addition via IPAPI failed. Fallback to netsh.exe
Jan 31 7:50:36 : ROUTE: IPv6 route addition failed using management: Element nicht gefunden. [status=1168 if_index=8]
Jan 31 7:50:36 : add_route_ipv6(2000::/4 -> fd42:42:42:42::1 metric -1) dev benpc_denise
Jan 31 7:50:36 : Route addition via IPAPI failed. Fallback to netsh.exe
Jan 31 7:50:36 : ROUTE: IPv6 route addition failed using management: Element nicht gefunden. [status=1168 if_index=8]
Jan 31 7:50:36 : add_route_ipv6(3000::/4 -> fd42:42:42:42::1 metric -1) dev benpc_denise
Jan 31 7:50:36 : Route addition via IPAPI failed. Fallback to netsh.exe
Jan 31 7:50:36 : ROUTE: IPv6 route addition failed using management: Element nicht gefunden. [status=1168 if_index=8]
Jan 31 7:50:36 : add_route_ipv6(fc00::/7 -> fd42:42:42:42::1 metric -1) dev benpc_denise
Jan 31 7:50:36 : Route addition via IPAPI failed. Fallback to netsh.exe
Jan 31 7:50:36 : ROUTE: IPv6 route addition failed using management: Element nicht gefunden. [status=1168 if_index=8]
Jan 31 7:50:36 : SYSTEM ROUTING TABLE
Jan 31 7:50:36 : 0.0.0.0 0.0.0.0 192.168.0.100 p=0 i=27 t=4 pr=3 a=1133 h=0 m=281/0/0/0/0
Jan 31 7:50:36 : 127.0.0.0 255.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=2 a=1134 h=0 m=331/0/0/0/0
Jan 31 7:50:36 : 127.0.0.1 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=2 a=1134 h=0 m=331/0/0/0/0
Jan 31 7:50:36 : 127.255.255.255 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=2 a=1134 h=0 m=331/0/0/0/0
Jan 31 7:50:36 : 185.xxx.xxx.xx 255.255.255.255 192.168.0.100 p=0 i=27 t=4 pr=3 a=0 h=0 m=50/0/0/0/0
Jan 31 7:50:36 : 192.168.0.0 255.255.255.0 192.168.0.1 p=0 i=27 t=3 pr=2 a=1123 h=0 m=281/0/0/0/0
Jan 31 7:50:36 : 192.168.0.1 255.255.255.255 192.168.0.1 p=0 i=27 t=3 pr=2 a=1123 h=0 m=281/0/0/0/0
Jan 31 7:50:36 : 192.168.0.255 255.255.255.255 192.168.0.1 p=0 i=27 t=3 pr=2 a=1123 h=0 m=281/0/0/0/0
Jan 31 7:50:36 : 192.168.1.0 255.255.255.0 192.168.0.1 p=0 i=27 t=3 pr=2 a=1123 h=0 m=281/0/0/0/0
Jan 31 7:50:36 : 192.168.1.10 255.255.255.255 192.168.0.1 p=0 i=27 t=3 pr=2 a=1123 h=0 m=281/0/0/0/0
Jan 31 7:50:36 : 192.168.1.255 255.255.255.255 192.168.0.1 p=0 i=27 t=3 pr=2 a=1123 h=0 m=281/0/0/0/0
Jan 31 7:50:36 : 192.168.10.0 255.255.255.0 192.168.0.1 p=0 i=27 t=3 pr=2 a=1123 h=0 m=281/0/0/0/0
Jan 31 7:50:36 : 192.168.10.10 255.255.255.255 192.168.0.1 p=0 i=27 t=3 pr=2 a=1123 h=0 m=281/0/0/0/0
Jan 31 7:50:36 : 192.168.10.255 255.255.255.255 192.168.0.1 p=0 i=27 t=3 pr=2 a=1123 h=0 m=281/0/0/0/0
Jan 31 7:50:36 : 192.168.11.0 255.255.255.0 192.168.0.1 p=0 i=27 t=3 pr=2 a=1123 h=0 m=281/0/0/0/0
Jan 31 7:50:36 : 192.168.11.10 255.255.255.255 192.168.0.1 p=0 i=27 t=3 pr=2 a=1123 h=0 m=281/0/0/0/0
Jan 31 7:50:36 : 192.168.11.255 255.255.255.255 192.168.0.1 p=0 i=27 t=3 pr=2 a=1123 h=0 m=281/0/0/0/0
Jan 31 7:50:36 : 192.168.56.0 255.255.255.0 192.168.56.1 p=0 i=30 t=3 pr=2 a=1129 h=0 m=281/0/0/0/0
Jan 31 7:50:36 : 192.168.56.1 255.255.255.255 192.168.56.1 p=0 i=30 t=3 pr=2 a=1129 h=0 m=281/0/0/0/0
Jan 31 7:50:36 : 192.168.56.255 255.255.255.255 192.168.56.1 p=0 i=30 t=3 pr=2 a=1129 h=0 m=281/0/0/0/0
Jan 31 7:50:36 : 192.168.100.0 255.255.255.0 192.168.0.1 p=0 i=27 t=3 pr=2 a=1123 h=0 m=281/0/0/0/0
Jan 31 7:50:36 : 192.168.100.10 255.255.255.255 192.168.0.1 p=0 i=27 t=3 pr=2 a=1123 h=0 m=281/0/0/0/0
Jan 31 7:50:36 : 192.168.100.255 255.255.255.255 192.168.0.1 p=0 i=27 t=3 pr=2 a=1123 h=0 m=281/0/0/0/0
Jan 31 7:50:36 : 224.0.0.0 240.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=2 a=1134 h=0 m=331/0/0/0/0
Jan 31 7:50:36 : 224.0.0.0 240.0.0.0 192.168.56.1 p=0 i=30 t=3 pr=2 a=1133 h=0 m=281/0/0/0/0
Jan 31 7:50:36 : 224.0.0.0 240.0.0.0 192.168.0.1 p=0 i=27 t=3 pr=2 a=1133 h=0 m=281/0/0/0/0
Jan 31 7:50:36 : 255.255.255.255 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=2 a=1134 h=0 m=331/0/0/0/0
Jan 31 7:50:36 : 255.255.255.255 255.255.255.255 192.168.56.1 p=0 i=30 t=3 pr=2 a=1133 h=0 m=281/0/0/0/0
Jan 31 7:50:36 : 255.255.255.255 255.255.255.255 192.168.0.1 p=0 i=27 t=3 pr=2 a=1133 h=0 m=281/0/0/0/0
Jan 31 7:50:36 : SYSTEM ADAPTER LIST
Jan 31 7:50:36 : Intel(R) I211 Gigabit Network Connection
Jan 31 7:50:36 : Index = 27
Jan 31 7:50:36 : GUID = {BDE92278-539B-40C3-A799-EA865EDEA3CA}
Jan 31 7:50:36 : IP = 192.168.0.1/255.255.255.0 192.168.1.10/255.255.255.0 192.168.10.10/255.255.255.0 192.168.11.10/255.255.255.0 192.168.100.10/255.255.255.0
Jan 31 7:50:36 : MAC = 70:85:c2:3e:e2:67
Jan 31 7:50:36 : GATEWAY = 192.168.0.100/255.255.255.255
Jan 31 7:50:36 : DNS SERV = 194.150.168.168/255.255.255.255 91.239.100.100/255.255.255.255
Jan 31 7:50:36 : Bluetooth Device (Personal Area Network) #6
Jan 31 7:50:36 : Index = 11
Jan 31 7:50:36 : GUID = {3197DFA0-4C4B-4480-831C-D6327854DF1A}
Jan 31 7:50:36 : IP = 0.0.0.0/0.0.0.0
Jan 31 7:50:36 : MAC = 00:1a:7d:da:71:13
Jan 31 7:50:36 : GATEWAY = 0.0.0.0/255.255.255.255
Jan 31 7:50:36 : DHCP SERV =
Jan 31 7:50:36 : DHCP LEASE OBTAINED = Sun Jan 31 19:50:36 2021
Jan 31 7:50:36 : DHCP LEASE EXPIRES = Sun Jan 31 19:50:36 2021
Jan 31 7:50:36 : DNS SERV =
Jan 31 7:50:36 : Kaspersky Security Data Escort Adapter
Jan 31 7:50:36 : Index = 32
Jan 31 7:50:36 : GUID = {EC6D3E66-1615-45C4-AAB0-A46B0C5EF726}
Jan 31 7:50:36 : IP = 0.0.0.0/0.0.0.0
Jan 31 7:50:36 : MAC = 00:ff:ec:6d:3e:66
Jan 31 7:50:36 : GATEWAY = 0.0.0.0/255.255.255.255
Jan 31 7:50:36 : DHCP SERV =
Jan 31 7:50:36 : DHCP LEASE OBTAINED = Sun Jan 31 19:50:36 2021
Jan 31 7:50:36 : DHCP LEASE EXPIRES = Sun Jan 31 19:50:36 2021
Jan 31 7:50:36 : DNS SERV =
Jan 31 7:50:36 : VirtualBox Host-Only Ethernet Adapter
Jan 31 7:50:36 : Index = 30
Jan 31 7:50:36 : GUID = {E116766D-CFE4-4B91-A96D-526FBF240DA3}
Jan 31 7:50:36 : IP = 192.168.56.1/255.255.255.0
Jan 31 7:50:36 : MAC = 0a:00:27:00:00:1e
Jan 31 7:50:36 : GATEWAY = 0.0.0.0/255.255.255.255
Jan 31 7:50:36 : DNS SERV =
Jan 31 7:50:36 : Wintun Userspace Tunnel
Jan 31 7:50:36 : Index = 33
Jan 31 7:50:36 : GUID = {F5937CA2-71CC-4022-9025-0AF36FF57471}
Jan 31 7:50:36 : IP = 0.0.0.0/0.0.0.0
Jan 31 7:50:36 : MAC =
Jan 31 7:50:36 : GATEWAY = 0.0.0.0/255.255.255.255
Jan 31 7:50:36 : DNS SERV =
Jan 31 7:50:36 : TAP-Windows Adapter V9
Jan 31 7:50:36 : Index = 22
Jan 31 7:50:36 : GUID = {A0D04C0E-8CC4-463D-B2E5-8823033DCF40}
Jan 31 7:50:36 : IP = 0.0.0.0/0.0.0.0
Jan 31 7:50:36 : MAC = 00:ff:a0:d0:4c:0e
Jan 31 7:50:36 : GATEWAY = 0.0.0.0/255.255.255.255
Jan 31 7:50:36 : DHCP SERV =
Jan 31 7:50:36 : DHCP LEASE OBTAINED = Sun Jan 31 19:50:36 2021
Jan 31 7:50:36 : DHCP LEASE EXPIRES = Sun Jan 31 19:50:36 2021
Jan 31 7:50:36 : DNS SERV =
Jan 31 7:50:36 : Initialization Sequence Completed With Errors ( see http://openvpn.net/faq.html#dhcpclientserv )
Jan 31 7:50:44 : Unable to locate adapter used for this connection.
Jan 31 7:50:44 : Unable to locate adapter used for this connection.
Jan 31 7:50:44 : Status auf Verbunden geändert
the outcome of this is:
Viscosity is "connected" - No active VPN, still using my normal internet connection.

Using OpenVPN TAP Adapter (Legacy):
Jan 31 7:53:12 : Status auf Verbinde geändert
Jan 31 7:53:12 : Viscosity Windows 1.9 (1695)
Jan 31 7:53:12 : Betriebsystem ist Windows 10 2004 (19041) 64 bit
Jan 31 7:53:12 : Betriebsystem ist .NET Framework Version 4.8.04084.528372
Jan 31 7:53:12 : Checking reachability status of connection...
Jan 31 7:53:12 : Connection is reachable. Starting connection attempt.
Jan 31 7:53:12 : Aktivieren des Netzwerkadapters...
Jan 31 7:53:12 : There was a problem activing the interface, Viscosity will attempt to repair it. This process may take a minute or two.
Jan 31 7:53:12 : Please try the following if this problem persists: https://www.sparklabs.com/support/kb/ar ... s-windows/
Jan 31 7:53:12 : OpenVPN 2.4.9 Windows-MSVC [SSL (OpenSSL)] [LZO] [LZ4] [AEAD] built on Oct 6 2020
Jan 31 7:53:12 : library versions: OpenSSL 1.1.1h 22 Sep 2020, LZO 2.10
Jan 31 7:53:13 : Valid endpoint found: 185.xxx.xxx.xx:xxxx:udp
Jan 31 7:53:13 : Outgoing Control Channel Encryption: Cipher 'AES-256-CTR' initialized with 256 bit key
Jan 31 7:53:13 : Outgoing Control Channel Encryption: Using 256 bit message hash 'SHA256' for HMAC authentication
Jan 31 7:53:13 : Incoming Control Channel Encryption: Cipher 'AES-256-CTR' initialized with 256 bit key
Jan 31 7:53:13 : Incoming Control Channel Encryption: Using 256 bit message hash 'SHA256' for HMAC authentication
Jan 31 7:53:13 : TCP/UDP: Preserving recently used remote address: [AF_INET]185.xxx.xxx.xx:xxxx
Jan 31 7:53:13 : Socket Buffers: R=[65536->65536] S=[65536->65536]
Jan 31 7:53:13 : UDP link local: (not bound)
Jan 31 7:53:13 : UDP link remote: [AF_INET]185.xxx.xxx.xx:xxxx
Jan 31 7:53:13 : Status auf Authenticating geändert
Jan 31 7:53:13 : TLS: Initial packet from [AF_INET]185.xxx.xxx.xx:xxxx, sid=40ee8ffb 0be53d1a
Jan 31 7:53:13 : VERIFY KU OK
Jan 31 7:53:13 : Validating certificate extended key usage
Jan 31 7:53:13 : ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
Jan 31 7:53:13 : VERIFY EKU OK
Jan 31 7:53:13 : VERIFY X509NAME OK: CN=server_TFXu2vFUjOJL30Xd
Jan 31 7:53:13 : VERIFY OK: depth=0, CN=server_TFXu2vFUjOJL30Xd
Jan 31 7:53:13 : Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, 256 bit EC, curve: prime256v1
Jan 31 7:53:13 : [server_TFXu2vFUjOJL30Xd] Peer Connection Initiated with [AF_INET]185.xxx.xxx.xx:xxxx
Jan 31 7:53:13 : Status auf Verbinde geändert
Jan 31 7:53:13 : SENT CONTROL [server_TFXu2vFUjOJL30Xd]: 'PUSH_REQUEST' (status=1)
Jan 31 7:53:13 : PUSH: Received control message: 'PUSH_REPLY,dhcp-option DNS 1.0.0.1,dhcp-option DNS 1.1.1.1,redirect-gateway def1 bypass-dhcp,tun-ipv6,route-ipv6 2000::/3,redirect-gateway ipv6,tun-ipv6,route-gateway 10.8.0.1,topology subnet,ping 10,ping-restart 120,ifconfig-ipv6 fd42:42:42:42::1001/112 fd42:42:42:42::1,ifconfig 10.8.0.3 255.255.255.0,peer-id 1,cipher AES-128-GCM'
Jan 31 7:53:13 : OPTIONS IMPORT: timers and/or timeouts modified
Jan 31 7:53:13 : OPTIONS IMPORT: --ifconfig/up options modified
Jan 31 7:53:13 : OPTIONS IMPORT: route options modified
Jan 31 7:53:13 : OPTIONS IMPORT: route-related options modified
Jan 31 7:53:13 : OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Jan 31 7:53:13 : OPTIONS IMPORT: peer-id set
Jan 31 7:53:13 : OPTIONS IMPORT: adjusting link_mtu to 1624
Jan 31 7:53:13 : OPTIONS IMPORT: data channel crypto options modified
Jan 31 7:53:13 : Outgoing Data Channel: Cipher 'AES-128-GCM' initialized with 128 bit key
Jan 31 7:53:13 : Incoming Data Channel: Cipher 'AES-128-GCM' initialized with 128 bit key
Jan 31 7:53:13 : interactive service msg_channel=0
Jan 31 7:53:13 : ROUTE_GATEWAY 192.168.0.100/255.255.255.0 I=27 HWADDR=70:85:c2:3e:e2:67
Jan 31 7:53:13 : GDG6: remote_host_ipv6=n/a
Jan 31 7:53:13 : NOTE: GetBestInterfaceEx returned error: Element nicht gefunden. (code=1168)
Jan 31 7:53:13 : ROUTE6: default_gateway=UNDEF
Jan 31 7:53:13 : Awaiting adapter to come up...
Jan 31 7:53:14 : The interface is now responding, proceeding with connection attempt.
Jan 31 7:53:14 : TAP-WIN32 device [benpc_denise] opened: \\.\Global\{42EB5402-2435-4ABD-813E-E6F1B7BC243E}.tap, index: 8
Jan 31 7:53:14 : Set TAP-Windows TUN subnet mode network/local/netmask = 10.8.0.0/10.8.0.3/255.255.255.0 [SUCCEEDED]
Jan 31 7:53:15 : Waiting for DNS Setup to complete...
Jan 31 7:53:15 : Successful ARP Flush on interface [8] {42EB5402-2435-4ABD-813E-E6F1B7BC243E}
Jan 31 7:53:15 : add_route_ipv6(fd42:42:42:42::/112 -> fd42:42:42:42::1001 metric 0) dev benpc_denise
Jan 31 7:53:15 : IPv6 Route addition via management succeeded
Jan 31 7:53:16 : TEST ROUTES: 1/1 succeeded len=0 ret=1 a=0 u/d=up
Jan 31 7:53:16 : C:\WINDOWS\system32\route.exe ADD 185.xxx.xxx.xx MASK 255.255.255.255 192.168.0.100
Jan 31 7:53:16 : IPv4 Route addition via management succeeded
Jan 31 7:53:16 : C:\WINDOWS\system32\route.exe ADD 0.0.0.0 MASK 128.0.0.0 10.8.0.1
Jan 31 7:53:16 : IPv4 Route addition via management succeeded
Jan 31 7:53:16 : C:\WINDOWS\system32\route.exe ADD 128.0.0.0 MASK 128.0.0.0 10.8.0.1
Jan 31 7:53:16 : IPv4 Route addition via management succeeded
Jan 31 7:53:16 : add_route_ipv6(2000::/3 -> fd42:42:42:42::1 metric -1) dev benpc_denise
Jan 31 7:53:16 : IPv6 Route addition via management succeeded
Jan 31 7:53:16 : add_route_ipv6(::/3 -> fd42:42:42:42::1 metric -1) dev benpc_denise
Jan 31 7:53:16 : IPv6 Route addition via management succeeded
Jan 31 7:53:16 : add_route_ipv6(2000::/4 -> fd42:42:42:42::1 metric -1) dev benpc_denise
Jan 31 7:53:16 : IPv6 Route addition via management succeeded
Jan 31 7:53:16 : add_route_ipv6(3000::/4 -> fd42:42:42:42::1 metric -1) dev benpc_denise
Jan 31 7:53:16 : IPv6 Route addition via management succeeded
Jan 31 7:53:16 : add_route_ipv6(fc00::/7 -> fd42:42:42:42::1 metric -1) dev benpc_denise
Jan 31 7:53:16 : IPv6 Route addition via management succeeded
Jan 31 7:53:16 : Initialization Sequence Completed
Jan 31 7:53:17 : DNS ist auf 'Vollständig' eingestellt:
Server - 1.0.0.1:53; Lookup Type - Any; Domains - None
Server - 1.1.1.1:53; Lookup Type - Any; Domains - None

Jan 31 7:53:17 : Status auf Verbunden geändert
the outcome of this is:
Viscosity is "connected" - Only DNS doesn't seem to work. And it keeps that way until I restart the whole
system. - Disconnecting Viscosity isn't enough. Altough my systems DNS servers (194.150.168.168 and
91.239.100.100) are set.

Any tips are welcome. :)

Eric

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

Post by Eric » Mon Feb 01, 2021 9:15 am
Hi Sphalerite,

It looks like calls to system APIs are being blocked by something and Viscosity can't setup your VPN connection. I know you mentioned deactivating Kaspersky but I'm afraid this is the most likely culprit here. I'm afraid we're not familiar with Kaspersky but we have seen AV software still active when disabled before causing issues.

Can you please try the following:

- Uninstall Viscosity
- Cold boot your PC (shut it down, then start it up again. This does more than a restart so it is important its done)
- Disable Kaspersky
- Reinstall Viscosity
- With Kaspersky still disabled, whitelist ViscosityService.exe and Viscosity.exe at C:\Program Files\Viscosity and openvpn.exe at C:\Program Files\Viscosity\Resources\OpenVPN
- Try connecting again.

Please also note that Windows 10 2004 has a lot of networking issues, which may be the cause of your DNS not working when disconnecting. We highly recommend updating to Windows 10 20H2.

Regards,
Eric
Eric Thorpe
Viscosity Developer

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

asdffdsa6131

Posts: 28
Joined: Sat Feb 23, 2019 12:15 pm

Post by asdffdsa6131 » Tue Feb 02, 2021 3:07 am
hi Sphalerite,

i hope you do not mind me jumping into this post.
i just went thru a similar problem.
viewtopic.php?f=9&t=2965

Eric wrote, this, i wonder if he was thinking of my recent post
"we have seen AV software still active when disabled before causing issues."

tl;dr, comodo security software was the problem, tho i have been using it for close to 10 years on dozens of machines.
in fact, because i have trusted comodo for so long, never a problem, that i tried so many other possible fixes.

once i thought it might be comodo, i disabled all the features, blocking the services and rebooted.
still problem persisted.
i have to totally uninstall all the components, then viscosity worked.

about 2004, i have used it for a long time with viscosity, never a problem.
i have since updated to 20h2, but really, for me, not worth the update.

hope that helps

Sphalerite

Posts: 2
Joined: Mon Feb 01, 2021 5:43 am

Post by Sphalerite » Tue Feb 02, 2021 8:25 am
Thanks guys.

Today I've upgraded to Windows 10 20H2.

Uninstalled Viscosity, did a coldboot right after that.
Disabled Kaspersky and reinstalled Viscosity.
With Kaspersky still disabled, I whitelisted ViscosityService.exe and Viscosity.exe at C:\Program Files\Viscosity and openvpn.exe at C:\Program Files\Viscosity\Resources\OpenVPN
Did another cold boot.

Nothing changed.

After that I tried the same again, but with completely removing Kaspersky from my system instead.

Unfortunately, nothing changed.

After that I've tried the OpenVPN client again which then also couldn't open TUN/TAP anymore. :shock:
Resolved that by adding new WinTUN and TAP devices. - Reinstalled Viscosity, but still get the exact same
problems. - OpenVPN client is still working (again). (I've also tried removing the OpenVPN client, but that
neither changed the behavior of Viscosity.)

I think I'll temporary stick to that client. :cry:

Eric

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

Post by Eric » Tue Feb 02, 2021 9:07 am
Hi Sphalerite,

I'm sorry to hear this didn't work. From here we would recommend reinstalling Windows, something is definitely not right on this system.

Regards,
Eric
Eric Thorpe
Viscosity Developer

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