
This will temporarily solve your problem. So I just enabled it and issued the under listed command. remote desktop connection will start working without any problem.ġ.In Control Panel, click Administrative Tools, and then double-click Local Security Policy.Ģ.In Local Security Settings, expand Local Policies, and then click Security Options.ģ.Under Policy in the right pane, double-click System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing, and then click Enabled.

Once done with the protocol enable, restart the server and you will be good to connect to your server remotely.

If for any reason (Penetration testing) you have disabled the TLS 1.0, 1.1 and 1.2 to test your server and application, you need to enable it back.

Run the IISCrypto and make sure at least TLS1.2 is enabled.
