wesupport

25% off on first invoice for all services*

SPRING SALE

Use coupon

*Offer valid for new customers only

25% off on first invoice for all services*

SPRING SALE

Use coupon

*Offer valid for new customers only

Need help?

Our experts have had an average response time of 11.43 minutes in March 2024 to fix urgent issues.

We will keep your servers stable, secure, and fast at all times for one fixed price.

Remote Desktop client disconnects and cannot reconnect to the same session

by | Nov 11, 2020

Remote Desktop client after it loses connection and disconnects cannot reconnect to the same session.

As a part of our Server Management Services, we help our Customers to fix Windows related errors regularly.

Let us today discuss the possible causes and fixes for this error.

Remote Desktop client disconnects and users cannot reconnect to the same session

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:

  • The client couldn’t connect to the terminal server because of a security error. Make sure you are signed in to the network, then try connecting again.
  • 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.
    Remote Desktop client disconnects and cannot reconnect to the same session

 

When the Remote Desktop client reconnects, the RDSH server reconnects the client to a new session instead of the original session.

However, when we check the RDSH server, it says that the original session is still active and did not enter a disconnected state.

A work around for this issue would be to configure keep-alive connection interval policy.

Resolution

We can enable the 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.

Once we enable this policy, we must enter a keep-alive interval. The keep-alive interval determines how often, in minutes, the server checks the session state.

This issue can also be fixed by reconfiguring the authentication and configuration settings. We can reconfigure these settings at either the server level or by using group policy objects (GPOs).

Here is how to reconfigure the settings: Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Security group policy folder.

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

[Need any further assistance in fixing Windows errors? – We’re available 24*7]

Conclusion

In short, Remote Desktop client after it loses connection and disconnects cannot reconnect to the same session.A work around in this case is to configure keep-alive connection interval policy. Today, we saw how our Support Engineers performs this task.

 

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Categories

Tags