General Remote Desktop connection troubleshooting
- Article
- 12/23/2021
- 8 minutes to read
- 8 contributors
Is this page helpful?
Yes No
Any additional feedback?
Feedback will be sent to Microsoft: By pressing the submit button, your feedback will be used to improve Microsoft products and services. Privacy policy.
Submit
Thank you.
In this article
Use these steps when a Remote Desktop client can't connect to a remote desktop but doesn't provide messages or other symptoms that would help identify the cause.
Troubleshoot Remote desktop disconnected errors
- Article
- 12/09/2021
- 19 minutes to read
- 4 contributors
Is this page helpful?
Yes No
Any additional feedback?
Feedback will be sent to Microsoft: By pressing the submit button, your feedback will be used to improve Microsoft products and services. Privacy policy.
Submit
Thank you.
In this article
This article helps you understand the most common settings that are used to establish a Remote Desktop session in an enterprise environment, and provides troubleshooting information for Remote desktop disconnected errors.
Applies to: Windows Server 2012 R2
Original KB number: 2477176
Note
This article is intended for use by support agents and IT professionals.
How to fix ‘remote desktop can’t connect to the remote computer’
Jalapeno
OP
Feb 20, 2019 at 14:57 UTC
Do the logs on the host server show anything? Check the Terminal Services or Remote desktop logs.
Also, if you have a gateway server setup check the logs there so you can figure out why they are getting disconnected.
Is your host server RDSH or RDVH?
How many host servers do you have an what are the specs?
0
· · ·
Pimiento
OP
Feb 20, 2019 at 19:24 UTC
So first of all, I'm no expert on Windows servers. I had someone help w/ the setup a year ago, but I've been reading and learning a lot of stuff.
We have TWO servers [2016 windows]. Both are Session Hosts. The first one is the DC and has Active Directory. The second one is just a session host server. The idea is that we connect to the second server and use our database driven applications. The database itself is on the first server.
My understanding is that the set up 100% correctly configured because:
a] I don't see any certificates setup when I go to Server Manager > Remote Desktop Deployment Properties. I don't want to touch this and create any new issues. I'm not sure if this is causing any issues.
b] Also, up until yesterday, there were no servers which were RD Gateways in the Gateway Manager GUI. However, today I just set up the AD DC server to be the RD gateway.
Give these two things, I was, and still am, able to remote into the servers by IP address. However......
1]The only issue is that I just can't get Windows to create new users anymore on the second server.
2] I can create users in AD on the domain controller [the first server]
3] I can login to the DC [first server] and it creates users perfectly fine.
4] On the second server, windows fails to create their profile in the Registry, and also fails to create their user folders in the C:\Users directory
So the issue isn't connecting to the servers. It's really the creation of users on the second server.
0
· · ·
Pimiento
OP
Feb 20, 2019 at 19:33 UTC
Also, the only logs I can find that pertain to anything are logs on the second server where I try to login. When i try to login with the new created user account, it says Login success by the user, and then about 5 events of login failures [from the first server], and then it has a logout event.
It looks like the first server is trying to do something but is unable to. That's my best guess with all these failure events occurring. It seems windows is trying to create the profile in registry and the user folders, but can't do it for w/e reason, as it pertains to the first server [The DC] is unable to login to the second one.
It might be a configuration issue because when I log into the first server and then try to RDP into the second server, it gives me an error such as "can't verify servers are apart of the farm"
0
· · ·
Pimiento
OP
Feb 22, 2019 at 06:14 UTC
Some new information. Logs in the DC server are showing the following:
This connection request has timed out. User could not log on to the end point within the alloted time. Remote Desktop Connection Broker will stop monitoring this connection request.
0
· · ·
Pimiento
OP
Best Answer
Feb 22, 2019 at 06:29 UTC
SOLUTION FINALLY FOUND!!!! I was able to look in the Logs under TS connection broker [or something like this] and found that the message:
To fix it, following text has been found on another web site:
This connection request has timed out. User could not log on to the end point within the alloted time. Remote Desktop Connection Broker will stop monitoring this connection request.
In group policy – configure FQDN for the RD Connection Broker. [you will also need to enable ‘join rd connection broker]
my working config as below.
Local Computer Policy/Computer Configuration/Administrative Templates/Windows Components/Remote Desktop Services/Remote Desktop Session Host/RD Connection Broker/
Join RD Connection Broker – enabled
Configure RD Connection Broker farm name – not configured
Use Ip Adress redirection – not configured
Configure RD Connection Broker server name – enabled [put you FQDN here of the RD Connection Server or servers].
Use RD Connection Broker load balancing – not configured. [I have only one server]
I hope this maybe can help
Text
This connection request has timed out. User could not log on to the end point within the alloted time. Remote Desktop Connection Broker will stop monitoring this connection request. In group policy – configure FQDN for the RD Connection Broker. [you will also need to enable ‘join rd connection broker] my working config as below. Local Computer Policy/Computer Configuration/Administrative Templates/Windows Components/Remote Desktop Services/Remote Desktop Session Host/RD Connection Broker/ Join RD Connection Broker – enabled Configure RD Connection Broker farm name – not configured Use Ip Adress redirection – not configured Configure RD Connection Broker server name – enabled [put you FQDN here of the RD Connection Server or servers]. Use RD Connection Broker load balancing – not configured. [I have only one server] I hope this maybe can help0
This topic has been locked by an administrator and is no longer open for commenting.
To continue this discussion, please ask a new question.