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
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:


Potential reasons

  • The server determined that it did not support any of the ciphers that the client offered, and then it resorted to closing the connection. This will be shown fairly clearly in the InControl server logs if this is the case.
    • Was the default allowed ciphers in Windows (client side) changed or disabled? If the default ciphers was changed it could cause compatibility issues (not just with InControl but other programs as well).
    • For names of the cipher suites in Windows, there's no standard. The MS documentation needs to be carefully be consulted for what they are named in order to configure it in Windows. Additionally, there is a chance that MS have renamed some of the ciphers between some versions of Windows. It's quite complex to setup up correctly. If these settings/ciphers are changed, the MS documentation must be carefully consulted.
  • Very unstable network connection
    • Unlikely, but possible.

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.


For more information about how a TLS connection works, this page illustrates it very good with every byte explained and reproduced:

Related articles

Brian Smart Search (Beta)
15 Jan, 2024 dictionary troubleshoot core stream incontrol incenter oneconnect cloudservice
Getting totals for triggering cOS Core IP rule set entries
16 Mar, 2023 core incontrol statistics rules
Automatic scheduled backup of InControl server database
5 Feb, 2021 incontrol howto backup windows
Certificate update in InControl global domain on certificate that is used on firewall(s)
18 Mar, 2024 core incontrol certificate oneconnect ipsec vpn
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