Why can't the client connect to the server or is the line offline?

Cause 1:

The system time between the client machine and the server machine does not match

If the time does not match, the following error may occur:

Cause 2:

Check the following registry entry on the affected client machine:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Cryptography\Configuration\Local\SSL\00010003

Here the following values should be stored in the key "Functions":

RSA/SHA512
ECDSA/SHA512
RSA/SHA256
RSA/SHA384
RSA/SHA1
ECDSA/SHA256
ECDSA/SHA384
ECDSA/SHA1
DSA/SHA1

Add the missing values and restart the computer. Afterwards you can log in again.

Cause 3:

Check whether the firewall you are using is blocking port 2230. To test this you can use the PortTester provided by us or, if the Windows feature Telnet-Client is installed, check the connection via Telnet.

For example, using the command line call: "telnet <server IP or address> <port>"

Cause 4:

The Connect Client may already be unable to connect to the local UCSingleSignOn via named pipes. As a result, it does not receive login credentials and cannot log in to the server.

The two test programs host.exe and guest.exe can be used to check whether Named Pipes work properly on the client computer. This must work without admin rights! If this is not the case, it is a XPhone-external problem and the administrator of the system must look for the cause elsewhere.

Download: https://github.com/C4BCSMORG/tmp/raw/main/Tools/NamesPipesTest/NamesPipesTest.zip 

For the test, proceed exactly according to the instructions in the ReadMe.

As a counter test you can also check whether the result of the Named Pipes test differs when you start the tool as admin. The same applies to the Connect Client. In this way, you can determine whether the problem is simply due to a lack of permissions.