question

adamj999 avatar image
0 Votes"
adamj999 asked LouisTang-4441 answered

Remote Desktop Error "You have been disconnected because another connection was made to the remote computer"

After applying the March 2021 updates to my Windows 10 20H2 home computer, I am unable to reconnect to my office computer which is also running Windows 10 20H2 and also received the March 2021 updates. I get the Remote Desktop Error "You have been disconnected because another connection was made to the remote computer"

This problem started yesterday morning. I generally connect to my office computer in the morning and disconnect in the evening. This has been working flawlessly for a year now. The problem only just started.

Yesterday, I found that I could reconnect sometime in the afternoon. I completed some work and disconnected again in the evening. This morning, when I tried to reconnect, I got the same error. Based on the message, it seems like part of the session is being held until it times out. I will see if I can reconnect again this afternoon.

My office PC is an AD Domain participant. My home PC is not. I typically use the Remote Desktop MS Store App to connect, which is up to date. However, I also tried connecting with the built-in Remote Desktop application and could not connect either.

I rebooted my home PC before attempting to reconnect. I also rebooted my remote PC yesterday, after I was able to reconnect in the afternoon. (I reconnected, rebooted, and reconnected again. Later that evening, I disconnected. This morning, I could not reconnect.)

windows-10-generalremote-desktop-servicesremote-desktop-client
· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

This has been happening to me, too.
There are two computers I connect to regularly, on different networks and with different configurations.
It happens with both. Until recently, it happened with neither.
It occurs when the connection is dropped due to an unreliable connection.
Normally, I get the "Attempting to reconnect to your session" message, attempts are made to reconnect, and after a few seconds everything is fine.
Not any more!
With this new issue, when a reconnection attempt is successful, it is usually followed by the "You have been disconnected because another connection was made..." message.

I checked the event log, and the only remote desktop logins have been from me.

This is definitely a new Microsoft bug.

0 Votes 0 ·

I had this same error when trying to RDP to a newly installed Windows Server 2019. It turned out error "You have been disconnected because another connection was made to the remote computer"" can be very misleading.........in my case it was generated not because of an existing session but because I had not yet set the IPv4 address, etc. on the network adapter, i.e. the server was not connected to the outside world. Even at my age I seem to live and learn!

0 Votes 0 ·
KarlieWeng-MSFT avatar image
3 Votes"
KarlieWeng-MSFT answered adamj999 commented

Hello@adamj999

This prompt means either someone else has forcefully knocked you out of your remote session (Desktop OS remote session only allow 1 session cocurrent) or you mistakenly remoted twice into the same computer and forcefully closed your original remote session.
If you continue to encounter this error, you can check to see who is attempting to login and override your remote session in the remote machines using a command line command.


  1. Type the following command into Windows Command Prompt : quser


  2. This outputs the current logged in users.
    You can also search event viewer to find out the last logged in user.
    Open Event Viewer (Start -> type Event Viewer). Expand Windows Logs -> Security and search for Event ID 4624.
    This will display all login events on the machine. You can identify who is logging (Windows user ID) in around the time you are being kicked out.

  3. Check logs for remote desktop: Event Viewer - Applications and Services Logs, Microsoft, Windows, TerminalServices-RemoteConnectionManager, Operational


  4. A workaround I found online:
    Disable the "Restrict each user to a single session" setting on the remote machine via 'gpedit.msc', and go to the following location
    Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Connections
    Here you will need to change a setting called ‘Restrict Remote Desktop Services users to a single Remote Desktop Services session’ – set it to disabled.


Best Regards
Karlie


If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.






· 5
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Thank you, @KarlieWeng-MSFT I will try this when I am allowed back on the device later this afternoon. It is definitely not another user. The event log shows only me logging-in. After I disconnect, there are no events registered until I am allowed to reconnect later the following afternoon. My habit for the past year has been to Disconnect from my session at the end of the day and reconnect the following morning. This apparently no longer works as of one week ago.

It does seem as though my disconnected session is not truly being let-go, which forces me to wait until it times out several hours later. Has something changes with the March 2021 update that causes this behavior? I presume it is allowed to disconnect from and resume one's session via Remote Desktop. Is this no longer allowed? Right now, the only solution appears to be rebooting my remote computer at the end of every RDP session.

0 Votes 0 ·

Just an update. Have not tried the GP setting yet. I disabled the Power Management energy saving properties of the NIC in Device management to see if this improved the situation. It had no effect. I am going to try the GP setting suggested above tonight. I will know tomorrow morning if it worked or not.

0 Votes 0 ·

Looks like enabling simultaneous connections has done the trick. Thanks, @KarlieWeng-MSFT .

1 Vote 1 ·
Show more comments
susannec-7084 avatar image
0 Votes"
susannec-7084 answered

I had the same problem, running client on Windows 10. It was solved when adding my changed IP address to allowed connections on the server. Looks like the event description was out of range for me.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

767piloto-8448 avatar image
0 Votes"
767piloto-8448 answered

Same problem suddenly appeared. Turns out the Netgear router (where port-forwarding was set up) reassigned the IP used by the Windows machine I was remote connecting to. After changing the port-forwarding IP to the one matching the Windows machine, it was back to working.

Also, with most routers, you can assign which IP a given connection will use. This may prevent future problems...

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

GlenEdwards-9679 avatar image
0 Votes"
GlenEdwards-9679 answered

"This prompt means either someone else has forcefully knocked you out of your remote session..."

As it turns out the "other user" that locked me out was the firewall on the server computer. DHCP changed my local IP address, so my server slammed the door in my face. I updated the firewall; problem solved.






5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

LouisTang-4441 avatar image
0 Votes"
LouisTang-4441 answered

I had this problem before.

Method 1:
Contact Microsoft.

Method 2:
I can connect and use the RDP. It necessary to use the RDP app on a phone and with a PC. When the RDP app is connecting fist, I press the connect button of RDP on the PC simultaneously and kick out the current user. It works for me.

Method 3:
The RDP becomes normal after I removed the auto login values in regedit.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.