Probe failed, did not get a result

Last modified on 8 Sep, 2022. Revision 7
When attempting to connect with the InControl client to the InControl server, this message appears.
Up to date for
InControl 3.13.00
Not valid for
InControl 3.03.00 and older
Status OK
Author
Peter Nilsson

Message meaning

This is a fairly generic message that originates from a communication problem between InControl client and server. The message is generic because the client does not know what went wrong as the connection attempt was abruptly closed, but the client does not know why the connection was closed. Then this fairly generic message is shown to to the administrator in the InControl client.

The InControl server log may contain more information about what the connection problem is/was. The default path to the InControl server log is the following:

"%programdata%\Clavister\InControl\Server\logs\ics_log.txt"

Potential reasons

There may be other reasons as well, a good starting point would be to check the InControl server log if you see anything about the failed connection attempt. If the log is blank or does not contain any entry that matches the connection attempt (time wise) it is most likely one of the two first points.

Reference

For more information about how a TLS connection works, this page illustrates it very good with every byte explained and reproduced: https://tls12.xargs.org/



Related articles

Automatic scheduled backup of InControl server database
5 Feb, 2021 incontrol howto backup windows
Device initiated InControl management of NetWall HA clusters with a single public IP
31 Mar, 2022 incontrol core netcon netwall ha cluster coscore
How to perform an offline installation of InControl
26 Jan, 2022 howto incontrol installation