Upgrade to 1.4.4: A valid network does not exist.

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

thebithead

Posts: 4
Joined: Wed Apr 24, 2013 4:33 am

Post by thebithead » Wed Apr 24, 2013 4:38 am
I upgraded my copy of Viscosity to 1.4.4. Now when I try to connect, I get the message:

A valid network to the remote server does not exist.

This has happened on two different machines. My previous install of Viscosity worked fine.

Apr 23 02:31:03: State changed to Connecting
Apr 23 02:31:03: Viscosity 1.4.4 (1191)
Apr 23 02:31:03: Running on Microsoft Windows 7 Ultimate
Apr 23 02:31:03: Bringing up interface...
Apr 23 02:31:04: Checking reachability status of connection...
Apr 23 02:31:04: Reachability check failed for vpn.nimbusdb.com
Apr 23 02:31:04: Connection is not reachable. Disconnecting.
Apr 23 02:31:04: State changed to Disconnected
Apr 23 02:33:45: State changed to Connecting
Apr 23 02:33:45: Viscosity 1.4.4 (1191)
Apr 23 02:33:45: Running on Microsoft Windows 7 Ultimate
Apr 23 02:33:45: Bringing up interface...
Apr 23 02:33:45: Checking reachability status of connection...
Apr 23 02:33:46: Reachability check failed for vpn.nimbusdb.com
Apr 23 02:33:46: Connection is not reachable. Disconnecting.
Apr 23 02:33:46: State changed to Disconnected

-tom

Eric

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

Post by Eric » Wed Apr 24, 2013 6:00 pm
Hi Tom,

I seem to be getting some weird results off different DNS repositories for that address. Could you please try the following for us and post your results:

Open a command prompt by pressing start, type cmd then select cmd.exe that appears in the search list.

Type 'nslookup vpn.nimbusdb.com' without quotes into the command window and press Enter
Once that is finished, type 'ping vpn.nimbusdb.com' into the command window and press Enter

Once that is finished, can you please post the results that appear in that command window.

Regards,

Eric
Eric Thorpe
Viscosity Developer

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

thebithead

Posts: 4
Joined: Wed Apr 24, 2013 4:33 am

Post by thebithead » Wed May 08, 2013 11:11 pm
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\tgates>nslookup vpn.nimbusdb.com
Server: UnKnown
Address: 192.168.11.2

Non-authoritative answer:
Name: gateway.nimbusdb.com
Address: 173.9.45.73
Aliases: vpn.nimbusdb.com


C:\Users\tgates>ping vpn.nimbusdb.com

Pinging gateway.nimbusdb.com [173.9.45.73] with 32 bytes of data:
Reply from 173.9.45.73: Destination host unreachable.
Reply from 173.9.45.73: Destination host unreachable.
Reply from 173.9.45.73: Destination host unreachable.
Reply from 173.9.45.73: Destination host unreachable.

Ping statistics for 173.9.45.73:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

C:\Users\tgates>

Eric

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

Post by Eric » Thu May 09, 2013 3:11 pm
Hi Tom,

The data you posted above means there is no route for data to reach your VPN Provider, which is why Viscosity can't connect. Either the DNS Name is resolving to multiple IP address and is pulling an incorrect one, or there are multiple servers in your configuration that are failing to find a route.

If neither of these are the case, you will need to contact your VPN Provider and see if they can provide a server address for you that can be reached - http://sparklabs.com/support/how_do_i_f ... _my_vpn_p/

Regards,

Eric
Eric Thorpe
Viscosity Developer

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

thebithead

Posts: 4
Joined: Wed Apr 24, 2013 4:33 am

Post by thebithead » Sat May 11, 2013 10:14 pm
If there was no route, then why does Viscosity 1.4.2 work fine?

May 11 08:16:10: State changed to Connecting
May 11 08:16:10: Viscosity 1.4.2 (1178)
May 11 08:16:10: Running on Microsoft Windows 7 Ultimate
May 11 08:16:10: Bringing up interface...
May 11 08:16:10: Checking reachability status of connection...
May 11 08:16:11: Connection is reachable. Starting connection attempt.
May 11 08:16:11: OpenVPN 2.2.2 Win32-MSVC++ [SSL] [LZO2] [PKCS11] built on Jan 4 2012
May 11 08:16:14: WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
May 11 08:16:14: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
May 11 08:16:14: WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
May 11 08:16:14: Control Channel Authentication: using 'ta.key' as a OpenVPN static key file
May 11 08:16:14: LZO compression initialized
May 11 08:16:14: UDPv4 link local: [undef]
May 11 08:16:14: UDPv4 link remote: 173.9.45.73:1194
May 11 08:16:15: [server] Peer Connection Initiated with 173.9.45.73:1194
May 11 08:16:17: TAP-WIN32 device [NuoDB] opened: \\.\Global\{E68FDD80-7283-4BE7-A15A-614DBE70CAC2}.tap
May 11 08:16:17: Notified TAP-Win32 driver to set a DHCP IP/netmask of 10.1.37.220/255.255.255.0 on interface {E68FDD80-7283-4BE7-A15A-614DBE70CAC2} [DHCP-serv: 10.1.37.0, lease-time: 31536000]
May 11 08:16:17: Successful ARP Flush on interface [15] {E68FDD80-7283-4BE7-A15A-614DBE70CAC2}
May 11 08:16:22: Initialization Sequence Completed
May 11 08:16:22: State changed to Connected

-tom

Eric

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

Post by Eric » Mon May 13, 2013 2:29 pm
Hi Tom,

It looks like your server must be blocking ICMP packets which is throwing a false positive for Viscosity when checking for a valid path to the server. We will get this looked at and get a beta up with a fix as soon as we can.

Regards,

Eric
Eric Thorpe
Viscosity Developer

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

Eric

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

Post by Eric » Mon May 13, 2013 8:05 pm
Hi Tom,

We've just uploaded a new beta that should resolve the issue you are experiencing if you would like to trial it. Many thanks for your feedback so far!

http://www.sparklabs.com/forum/viewtopic.php?f=7&t=482

Regards,

Eric
Eric Thorpe
Viscosity Developer

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

thebithead

Posts: 4
Joined: Wed Apr 24, 2013 4:33 am

Post by thebithead » Tue May 14, 2013 9:49 am
I confirmed that new beta, Viscosity 1.4.5 (1195), fixed this issue.

-tom

Eric

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

Post by Eric » Tue May 14, 2013 10:18 pm
Thank you for the feedback, Tom!

Regards,

Eric
Eric Thorpe
Viscosity Developer

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