This error occurs when the Ion Desktop Client cannot establish a TCP socket connection to the server, which indicates that there is no network route to the server (i.e. messages from your machine are not reaching the machine running Ignision SE). This can happen when:
(Note: The following examples use “ion://mycompany.com” as a placeholder for your own URL, which can be either a name or IP address, e.g. “ion://aquaconnect.net” (name) or “ion://192.168.0.100” (IP).)
Port forwarding in the remote network router is not configured or is configured incorrectly.
Double check your Internet router/firewall settings and make sure that TCP connections using the port configured in Ignision SE (default is 310) are being forwarded to the IP address (on your internal LAN) of the machine running Ignision SE.
You can also forward a different external (Internet side) port to any internal (LAN side) port. For example, you can configure your router/firewall to forward Internet facing TCP port 12345 to LAN facing TCP port 310 and the IP of the machine on your LAN running Ignision SE. With this configuration, You would configure the Ion Desktop Client to connect to “ion://mycompany.com:12345”. When you click connect, the Ion Desktop Client will connect to mycompany.com on TCP port 12345, which is your router/firewall. Your router/firewall will then relay all Ignision traffic that it receives on TCP port 12345 to TCP port 310 and the IP address of the machine on your LAN running Ignision SE. You can also configure Ignision SE to use a different port (other than 310). Just remember to synchronize the configuration in your router/firewall to match.
The [remote] machine running Ignision SE is not running.
Verify that the URL entered into the Ion Desktop Client is free of typo's and superfluous spacing and punctuation, etc. If the machine running Ignision SE is using a TCP port other than the default (310) or if you're connecting through a router/firewall that configured to forward (NAT) a TCP port other than 310 to the machine running Ignision SE, then it is necessary to specify the [non default] port in the Ion Desktop Client configuration. For example, a typical connection may specify the destination as “ion://mycompany.com”. This implicitly uses the default TCP port 310 (since no port was explicitly specified). If, for example, you have configured Ignision SE to use port 12345, then the Ion Desktop Client connection destination should specify “ion://mycompany.com:12345”. This tells the Ion Desktop Client to connect to Ignision SE using TCP port 12345 instead of 310 (the default).
On rare occasions it will also be caused by a DNS failure.