Can't Connect to VPN

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

fg592

Posts: 4
Joined: Sat Jan 18, 2014 4:16 am

Post by fg592 » Sat Jan 18, 2014 4:34 am
Hi,

I've never had a problem with Viscosity before, it normally works flawlessly. This new install is a nightmare though. I'm unable to connect to a new connection that I'm importing. It just trys to connect then immediately disconnects.

Here's my log file:
Code: Select all
Jan 17 05:30:31: State changed to Connecting
Jan 17 05:30:31: Viscosity 1.4.7 (1222)
Jan 17 05:30:31: Running on Microsoft Windows 7 Ultimate 
Jan 17 05:30:31: Bringing up interface...
Jan 17 05:30:31: Checking reachability status of connection...
Jan 17 05:30:31: Connection is reachable. Starting connection attempt.
Jan 17 05:30:31: OpenVPN 2.3.2 Windows-MSVC [SSL (OpenSSL)] [LZO] [PKCS11] [eurephia] [IPv6] built on Dec 13 2013
Jan 17 05:30:32: Control Channel Authentication: using 'ta.key' as a OpenVPN static key file
Jan 17 05:30:32: UDPv4 link local: [undef]
Jan 17 05:30:32: UDPv4 link remote: [AF_INET]46.246.49.2:1194
Jan 17 05:30:32: WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Jan 17 05:30:33: [pw.openvpn.ipredator.se] Peer Connection Initiated with [AF_INET]46.246.49.2:1194
Jan 17 05:30:35: WARNING: potential conflict between --remote address [46.246.49.2] and --ifconfig address pair [46.246.49.6, 255.255.255.0] -- this is a warning only that is triggered when local/remote addresses exist within the same /24 subnet as --ifconfig endpoints. (silence this warning with --ifconfig-nowarn)
Jan 17 05:30:35: Control Channel Authentication: using 'ta.key' as a OpenVPN static key file
Jan 17 05:30:35: do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
Jan 17 05:30:35: UDPv4 link local: [undef]
Jan 17 05:30:35: open_tun, tt->ipv6=0
Jan 17 05:30:35: UDPv4 link remote: [AF_INET]46.246.49.2:1194
Jan 17 05:30:35: CreateFile failed on TAP device: \\.\Global\{F4D861D7-67C6-49CB-B550-AE230AD7FB7E}.tap: The system cannot find the file specified.   (errno=2)
Jan 17 05:30:35: WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Jan 17 05:30:35: State changed to Disconnected
Jan 17 05:30:35: [pw.openvpn.ipredator.se] Peer Connection Initiated with [AF_INET]46.246.49.2:1194
Jan 17 05:30:35: WARNING: potential conflict between --remote address [46.246.49.2] and --ifconfig address pair [46.246.49.6, 255.255.255.0] -- this is a warning only that is triggered when local/remote addresses exist within the same /24 subnet as --ifconfig endpoints. (silence this warning with --ifconfig-nowarn)
Jan 17 05:30:35: do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
Jan 17 05:30:35: open_tun, tt->ipv6=0
Jan 17 05:30:35: CreateFile failed on TAP device: \\.\Global\{F4D861D7-67C6-49CB-B550-AE230AD7FB7E}.tap: The system cannot find the file specified.   (errno=2)
Jan 17 05:30:35: Exiting due to fatal error

Eric

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

Post by Eric » Mon Jan 20, 2014 6:18 am
Hi fg592,

Please edit your connect and go to the Advanced tab. In the advanced commands section, you will see a command starting with dev-node. Delete this line, save the connection and then attempt to connect again. This should hopefully resolve the issue.

Regards,

Eric
Eric Thorpe
Viscosity Developer

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

fg592

Posts: 4
Joined: Sat Jan 18, 2014 4:16 am

Post by fg592 » Mon Jan 20, 2014 8:18 pm
Didn't work. I tried reimporting too. Looks like it's getting stuck creating the adaptor.
Code: Select all
Jan 20 09:15:18: State changed to Creating...
Jan 20 09:15:24: State changed to Disconnected
Jan 20 09:15:35: State changed to Connecting
Jan 20 09:15:35: Viscosity 1.4.7 (1222)
Jan 20 09:15:35: Running on Microsoft Windows 7 Ultimate 
Jan 20 09:15:35: No associated network adapter was found, creating one. This process may take up to a minute or two.
Jan 20 09:15:35: State changed to Creating...
Jan 20 09:15:42: Network adapter created. Proceeding with connection attempt
Jan 20 09:15:42: State changed to Connecting
Jan 20 09:15:42: Bringing up interface...
Jan 20 09:15:42: There was a problem activing the interface, Viscosity will attempt to repair it. This process may take a minute or two.
Jan 20 09:15:42: State changed to Creating...

Eric

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

Post by Eric » Mon Jan 20, 2014 8:25 pm
Hi fg592,

It looks like something has happened to the driver. Simply rebooting your computer should clear up the problem, if it doesn't, uninstalling and then reinstalling Viscosity should resolve the issue.

Have you installed any new firewall or anti-virus software in between originally installing Viscosity and updating?

Regards,

Eric
Eric Thorpe
Viscosity Developer

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

fg592

Posts: 4
Joined: Sat Jan 18, 2014 4:16 am

Post by fg592 » Mon Jan 20, 2014 9:01 pm
No dice..
Code: Select all
Jan 20 09:58:38: State changed to Connecting
Jan 20 09:58:38: Viscosity 1.4.7 (1222)
Jan 20 09:58:38: Running on Microsoft Windows 7 Ultimate 
Jan 20 09:58:38: Bringing up interface...
Jan 20 09:58:38: Checking reachability status of connection...
Jan 20 09:58:38: Connection is reachable. Starting connection attempt.
Jan 20 09:58:38: OpenVPN 2.3.2 Windows-MSVC [SSL (OpenSSL)] [LZO] [PKCS11] [eurephia] [IPv6] built on Dec 13 2013
Jan 20 09:58:46: Control Channel Authentication: using 'ta.key' as a OpenVPN static key file
Jan 20 09:58:46: UDPv4 link local: [undef]
Jan 20 09:58:46: UDPv4 link remote: [AF_INET]46.246.47.130:1194
Jan 20 09:58:46: WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Jan 20 09:58:46: [pw.openvpn.ipredator.se] Peer Connection Initiated with [AF_INET]46.246.47.130:1194
Jan 20 09:58:48: WARNING: potential conflict between --remote address [46.246.47.130] and --ifconfig address pair [46.246.47.169, 255.255.255.0] -- this is a warning only that is triggered when local/remote addresses exist within the same /24 subnet as --ifconfig endpoints. (silence this warning with --ifconfig-nowarn)
Jan 20 09:58:48: Control Channel Authentication: using 'ta.key' as a OpenVPN static key file
Jan 20 09:58:48: do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
Jan 20 09:58:48: UDPv4 link local: [undef]
Jan 20 09:58:48: open_tun, tt->ipv6=0
Jan 20 09:58:48: UDPv4 link remote: [AF_INET]46.246.47.130:1194
Jan 20 09:58:48: CreateFile failed on TAP device: \\.\Global\{681D4E56-6DFA-4B7C-AAB5-B23B775738FB}.tap: The system cannot find the file specified.   (errno=2)
Jan 20 09:58:48: WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Jan 20 09:58:48: [pw.openvpn.ipredator.se] Peer Connection Initiated with [AF_INET]46.246.47.130:1194
Jan 20 09:58:48: WARNING: potential conflict between --remote address [46.246.47.130] and --ifconfig address pair [46.246.47.169, 255.255.255.0] -- this is a warning only that is triggered when local/remote addresses exist within the same /24 subnet as --ifconfig endpoints. (silence this warning with --ifconfig-nowarn)
Jan 20 09:58:48: do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
Jan 20 09:58:48: State changed to Disconnected
Jan 20 09:58:48: open_tun, tt->ipv6=0
Jan 20 09:58:48: CreateFile failed on TAP device: \\.\Global\{681D4E56-6DFA-4B7C-AAB5-B23B775738FB}.tap: The system cannot find the file specified.   (errno=2)
Jan 20 09:58:48: Exiting due to fatal errorJan 20 09:59:04: State changed to Connecting
Jan 20 09:59:04: Viscosity 1.4.7 (1222)
Jan 20 09:59:04: Running on Microsoft Windows 7 Ultimate 
Jan 20 09:59:04: No associated network adapter was found, creating one. This process may take up to a minute or two.
Jan 20 09:59:04: State changed to Creating...
Jan 20 09:59:08: Network adapter created. Proceeding with connection attempt
Jan 20 09:59:08: State changed to Connecting
Jan 20 09:59:08: Bringing up interface...
Jan 20 09:59:08: There was a problem activing the interface, Viscosity will attempt to repair it. This process may take a minute or two.
Jan 20 09:59:08: State changed to Creating...
Jan 20 09:59:12: Unable to repair interface, cancelling connection attempt.
Jan 20 09:59:12: State changed to Disconnected
And no it's a fresh install on my dedicated server. I can give you remote desktop access if you wanted to debug.

Eric

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

Post by Eric » Mon Jan 20, 2014 9:21 pm
Hi fg592,

Are you able to confirm that there are Viscosity adapters appearing in Device Manager and that they are reporting as having no problems. You will need to enable them to confirm Windows is not reporting any errors.

We are happy to take a look if we can't find a solution. Please shoot us an email to https://www.sparklabs.com/support/#contact.

Regards,
Eric
Eric Thorpe
Viscosity Developer

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

fg592

Posts: 4
Joined: Sat Jan 18, 2014 4:16 am

Post by fg592 » Mon Jan 20, 2014 9:34 pm
Looks like drivers weren't installed properly.

I uninstalled everything. Deleted and uninstalled the adapters in device manager. Then started fresh.

Seems to be working fine now. Cheers for the help!
7 posts Page 1 of 1