- Viscosity vpn failed to create adapter. driver#
- Viscosity vpn failed to create adapter. windows 10#
- Viscosity vpn failed to create adapter. android#
- Viscosity vpn failed to create adapter. windows 7#
Warning: Event 219, Kernel-PnP - The driver \Driver\ViscTunTap failed to load for the device ROOT\NET\0000 Relevant event in Windows System event log: Object reference not set to an instance of an object.ĭec 30 2:02:33 PM: WARNING: The TAP-Windows driver rejected a TAP_WIN_IOCTL_SET_MEDIA_STATUS DeviceIoControl call. The handle is invalidĭec 30 2:02:33 PM: Netsh method failed. Viscosity works fine with OpenVPN TAP adapter.ĭec 30 2:02:33 PM: Awaiting adapter to come up.ĭec 30 2:02:33 PM: Failed to process command >OPENTUN:HANDLE. When selecting Viscosity Virtual Adapter as the Adapter Type under Advanced options, VPN connection fails.
Viscosity vpn failed to create adapter. windows 10#
The first bold could be unimportant, though the second is interesting because it says timed out instead of inactivity.Running Viscosity 1.9.1 (1703) Beta 7 on Windows 10 Buld 21277.rs_prerelease.201207-1443 Jan 01 01:10:50: State changed to Connecting Jan 1 01:10:50: SIGUSR1 received, process restarting Jan 1 01:10:50: Connection reset, restarting Jan 1 01:10:50: read TCPv4_CLIENT: Connection timed out (WSAETIMEDOUT) (code=10060) Jan 01 01:08:02: State changed to Connected Jan 1 01:08:02: Initialization Sequence Completed Jan 1 01:07:56: Options error: unknown -redirect-gateway flag: def Jan 1 01:07:49: WARNING: this configuration may cache passwords in memory - use the auth-nocache option to prevent this
Jan 1 01:07:49: TCPv4_CLIENT link local: Jan 01 01:07:45: Connection is reachable. Jan 01 01:07:45: Checking reachability status of connection.
Viscosity vpn failed to create adapter. windows 7#
Jan 01 01:07:39: Running on Microsoft Windows 7 Ultimate Jan 01 01:07:39: State changed to Connecting
Here is log from this morning's attempt : Yes, reinstalled them anyways - no change.
Viscosity vpn failed to create adapter. android#
Might be on to something, but the first computer and the Android device are never affected by the status of the second computer. I then (foolishly) left that computer trying to use the VPN when I went back to the first computer, so now the problem had mysteriously appeared there too. When I then tried to connect to the VPN from the other computer I would see this behaviour. I have two computers I use, and I’d left one idle running the VPN client. This seems to happen when you’re running two openvpn clients with the same profile from different computers. I thought I’d put this here in case other people had the same issue. I was unable to find anything on the internet about this (possibly my google fu was weak), but we’ve finally managed to track down the problem. I saw these problems when I tried my profile on several different computers. Tue May 22 13:19:43 2012 Inactivity timeout (-ping-restart), restarting It would connect, and I could access the network, but the VPN would regularly restart itself and connections would be closed, seeing messages like I’ve been seeing bizarre problems with my openvpn client (on linux) over the last couple of days. Will send a ping every 10 seconds, but only restart if a ping hasn't been OpenVPN less sensitive to network outages by using a large keepalive This usually happens because of short-term network outages. The restart is occuring because a keepalive ping was not received during