Hi Alexander,
I'm not aware of any issues during smart reconnect. So the first step would be to provide more information so that we can try to reproduce the issue on our side (or rule out any environmental/configuration issue on your side). Once we can reproduce the issue, we can investigate what's going on and find a solution to make it more reliable.
I kindly ask you to open a support ticket and provide as much details about the issue as possible.
Thank you,
Stefan
Alexander K
Hello everyone,
I’d like to propose a new feature for RoyalTS that could improve the handling of smart reconnects for RDP sessions. Currently, when a smart reconnect occurs—for example, when resizing the RDP client window—Windows 11 and some other systems may display an error message saying that "the user is already connected, please wait until the previous session is terminated." This issue likely arises because the previous session did not finished disconnection yet.
My suggestion:
If RoyalTS could detect this specific session state (i.e., when this error appears during connection attempts), it should automatically trigger the auto-reconnect cycle. Although it might be challenging to directly identify this state, it seems possible that certain channels active before the smart reconnect become inactive afterward. Detecting these inactive channels might serve as a heuristic to initiate an automatic reconnection.
I believe this enhancement would help ensure a smoother user experience and reduce manual intervention when such issues occur.
Thank you for considering this idea!