Share via


Your Remote Desktop Services seesion has ended, I keep getting kicked out and unable to connect

Question

Wednesday, August 7, 2019 2:27 PM

Hello everyone,

For the past two weeks I have been having trouble connecting to my machine via RDP. I keep getting these two errors:

-Your Remote Desktop Services session has ended, possible for one of the following reasons:

The admin has ended the session

An error occurred while the connection was being established.

A network problem occurred.

-The number of connections to this computer is limited and all connections are in use right now.

Both machines have Windows 10 Pro 1903 with the latest updates and drivers. Would should I try?

Thank you,

All replies (9)

Thursday, August 8, 2019 3:15 AM | 1 vote

HI

1 are both win10(1903)computers in the same AD domain?
2 can you enter gpresult /h rdp.html in command prompt on problematical win10 then look if there is domain policy or local policy about "Limit number of connections ".
Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\ Remote Desktop Session Host\Connections\ Limit number of connections 

3 are you using RDP wrapper on win10 computer ?

4 there is a document for your reference

Cannot log into Windows 10 the number of connections to this computer is limited and all connections are in use right now
https://answers.microsoft.com/en-us/windows/forum/all/cannot-log-into-windows-10-the-number-of/b100ba40-cb98-4ca9-9230-9d04de02f197

5 can you use virus software to scan your problematical win10 ?
https://community.spiceworks.com/topic/2189609-the-number-of-connections-to-this-computer-is-limited-2016-rd-services

6 is there DNS problem for this issue ?
How to troubleshoot “The number of connections to this computer is limited and all connections are in use right now. Try connecting later or contact your system administrator.” warning message
http://www.kuskaya.info/2014/05/23/how-to-troubleshoot-the-number-of-connections-to-this-computer-is-limited-and-all-connections-are-in-use-right-now-try-connecting-later-or-contact-your-system-administrator-warning-message/

Best Regards
Andy YOU
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].


Thursday, August 8, 2019 2:08 PM

Hi Andy,

1. The computer being remoted into is in the AD, the other computer is from home.

2. There is no policy of limited connections

3. I am using the regular Remote Desktop Connections application

4. On which computer should I follow these steps for?

5. Where can I view who is trying to remote in? Where is the log?

6. I tried this and it didn't work.

When remoting from a laptop, I get kicked out and multiple log in errors, but when I remote from a desktop I am able to stay connected.


Thursday, August 8, 2019 2:32 PM

Is TCP3389 wide open? Two things are likely happening here...

1) Your firewall \ PC is dropping the connection because...

2) Somebody has identified RDP is an open port on the LAN and is brute force attacking it!

RDP should NOT be used or opened up for external access unless secured behind an RDP Server / Gateway.

If you only need direct access to one or a few machines and you can't afford the costs of RDP Server / Gateway setup then setup a VPN. Block external access via TCP3389 and VPN into the network to get RDP access via the private tunnel.


Thursday, August 8, 2019 2:59 PM

We do have a RDP Server/Gateway with a firewall in place. Could it possibly be the laptop? Since the issue happened on two laptops already and not on the desktops.


Monday, August 12, 2019 9:48 AM

Does it work successfully inside your LAN with both source and destination computers AD domain joined?


Friday, August 16, 2019 10:31 AM

HI

7 "When remoting from a laptop, I get kicked out and multiple log in errors, but when I remote from a desktop I am able to stay connected."
  7.1 Are your win10 laptop and desktop in the same workgroup in your home and in the same network segment now ?
  7.2 when you try to rdp to AD jioned win10 on both laptop and desktop ,if you enter netstat -ano both laptop and desktop ,is there any difference about established remote connection to  AD jioned win10pro.

8 did you do network trouble shoot tool on your laptop like picture ?
9 is there normal backup of win10 on your laptop then we can use it to recover to normal state ? 
10  backup win10 system of laptop first then check below method on your laptop
https://answers.microsoft.com/en-us/windows/forum/all/cannot-log-into-windows-10-the-number-of/b100ba40-cb98-4ca9-9230-9d04de02f197

Best Regards
Andy YOU
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].


Wednesday, August 21, 2019 3:13 AM

HI
Is there any progress on your question?

Best Regards
Andy YOU
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].


Wednesday, August 21, 2019 2:23 PM

Hello,

No, it's still the same after following your steps. I am still trying to figure it out. Thanks for your suggestions.


Monday, September 2, 2019 2:47 PM

HI

11 "We do have a RDP Server/Gateway with a firewall in place. Could it possibly be the laptop? Since the issue happened on two laptops already and not on the desktops."
I'd like to clarify your problem so that there are IT friends here who can help you. is your environment the same as below ??
your environment:
home pc: win10(1903) in workgroup, but I am not sure laptop or desktop
company computers: win10(1903) in AD ,they are desktop and laptop
you can use home pc remote access to company computer(desktop).
you can not use home pc remote access to company computer(laptop).

12 if you only use wireless adapter of your company laptop ,will the problem persist ?
     if you only use Wired LAN adapter of your company laptop ,will the problem persist ?

Best Regards
Andy YOU
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].