Remote Desktop client disconnects and can’t reconnect to the same session. How we fix it ?

Today, we will discuss possible causes and fixes to this error.

After Remote Desktop client loses its connection to the remote desktop, the client cannot immediately reconnect.

The user receives one of the following error messages:

2. The client couldn’t connect to the terminal server because of a security error:
   Make sure you are signed in to the network, try connecting again.
3. Remote Desktop disconnected. Because of a security error, the client could not connect to the remote computer:
   Verify that you are logged onto the network and then try connecting again.

When the Remote Desktop client reconnects, the RDSH server reconnects the client to a new session instead of the original session. However, if you check, the original session is still active and did not enter into a disconnected state.

You need to enable Configure keep-alive connection interval policy in the Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Connections group policy folder.

Reconfigure the settings

You can also fix this issue by reconfiguring the authentication and configuration settings.

Steps to Reconfigure the settings:

Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Security group policy folder.

• Open Remote Desktop Session Host Configuration.
• Under Connections, right-click the name of the connection, then select Properties.
• In the Properties dialog box for the connection, on the General tab, in Security layer, select a security method.
• Go to Encryption level and select the level you want. You can select Low, Client Compatible, High, or FIPS Compliant.