Thủ Thuật về Troubleshoot Remote Desktop Connection Broker Chi Tiết
Quý khách đang tìm kiếm từ khóa Troubleshoot Remote Desktop Connection Broker được Update vào lúc : 2022-02-26 10:00:07 . Với phương châm chia sẻ Bí kíp về trong nội dung bài viết một cách Chi Tiết Mới Nhất. Nếu sau khi đọc nội dung bài viết vẫn ko hiểu thì hoàn toàn có thể lại phản hồi ở cuối bài để Admin lý giải và hướng dẫn lại nha.
General Remote Desktop connection troubleshooting
Is this page helpful?
Yes
No
Nội dung chính
- General Remote Desktop connection troubleshooting
- Is this page helpful?
- In this article
- Troubleshoot Remote desktop disconnected errors
- Is this page helpful?
- In this article
- How to fix ‘remote desktop can’t connect to the remote computer’
- Top reasons for ‘remote desktop can’t connect to the remote computer’ error
- Windows update
- Public network profile
- Remote Desktop Services failed to join the Connection Broker on server
- Some Background
- Troubleshooting
- How to resolve common problems with Windows Remote Desktop
- RDS Connection Broker or RDMS fails after you disable TLS 1.0 in Windows Server
- Removed DNS RR record of the second broker node
- Removed the second gateway
- Removed the RD Web Access of the second node
The Remote Desktop service (RDS) may fail.
An existing RDS deployment that uses Remote Desktop Connection Broker and WID may fail.
The Remote Desktop Management service (RDMS) doesn’t start.
You receive the following error message when you try to start the RDMS:
The Remote Desktop Management service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs.
The Remote Desktop Connection Broker role can’t be installed.
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.
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
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.
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 tư vấn agents and IT professionals.
How to fix ‘remote desktop can’t connect to the remote computer’
Shutterstock
In today’s world, connecting to a remote computer has become commonplace, given that many companies have adopted a work-from-home culture. However, this can bring up many technical issues, including common errors such as “remote desktop can’t connect to the remote computer.”
So, how to fix this error? Well, let’s get a bit into the basics first.
Remote desktop is a convenient feature that allows you to virtually connect to other computers running the Windows operating system. With this feature, you can connect to computers located in any part of the world, provided you have the right credentials (username and password) to connect. Also, a good Internet connection is absolutely essential!
If you have the right credentials and the Internet connection and still face this issue, let’s address them.
Top reasons for ‘remote desktop can’t connect to the remote computer’ error
Before you read this section, check if your Internet connection is working fine and if you’re using the right credentials to log in because these are two of the most common causes of this error. Besides these two causes, there are also other reasons for this error.
Windows update
Many times, the Remote Desktop (RDP) functionality may get corrupted after a Windows update or upgrade as one of the newly installed files can interfere with the working of the RDP. You’ll have to manually identify the exact cause and fix it.
Antivirus
Sometimes, antivirus software can block RDP completely or partially, and this leads to the “remote desktop can’t connect to the remote computer” error. The good news about this error is it is easy to identify. Disable your antivirus and see if you can connect now. If you can, you’ve found the root cause of the problem!
Public network profile
If you have a public network profile or a network group, your computer can block the remote desktop functionality as a protective measure. While this is not an exhaustive list of reasons, these are the most common ones. Now comes the big question — how to fix the “remote desktop can’t connect to the remote computer” error.
Remote Desktop Services failed to join the Connection Broker on server
Recently I ran into a problem with an existing Remote Desktop Services 2012 R2 a client site. The error occurred intermittently and after a number of retries, client could establish connection normally making the issue not always reproducible. This blog summarises the process of identifying the symptoms, possible causes, and the resolution steps.
Some Background
The RDS farm consisted of two connection broker servers and two session hosts. The Remote Desktop Connection Broker is configured in HA mode using two DNS records pointing to two broker nodes for round robin. The session hosts are 2012 R2 based machines. The broker nodes also host the RD Web Access and RD gateway with one of the nodes assuming the RD Licensing role.
Troubleshooting
The end user encountered the following error when trying to connect:
Your computer cant connect to the remote computer because the Connection Broker couldnt validate the settings specified in your RDP file. Contact your network administrator for assistance.
After further digging, I found the error below [Event ID 802] on the second broker node:
RD Connection Broker failed to process the connection request for user <userID>.
Farm name specified in users RDP file [hints] could not be found.
Error: The farm specified for the connection is not present.
Additional errors encountered were:
Remote Desktop Connection Broker Client failed while getting redirection packet from Connection Broker.
User : <userID>
Error: Element not found.
Remote Desktop Connection Broker Client failed to redirect the user <userID>
Error: NULL
One aspect I discovered was that the same error didnt occur on the other broker server. This led me to investigate the RDS configuration: the RDCB was setup in HA mode with a SQL backend however it only has one node configured. We got somewhere. To isolate the issue, we had decided to operate the RDS on a one node configuration to confirm suspicion that whenever a user gets redirected to the broker thats not configured it would cause a redirection failure [RDCB uses Round Robin DNS for HA].
In the server manager console, the following tasks were done:
Connecting to the remote desktop farm from internal network worked fine after we have made this change tested this multiple times and from different machines to confirm that its stable. However we received a different error when connecting from external network but this time the end users error was different:
Remote Desktop cant connect to the remote computer for one of these reasons:
1] Remote access to the server is not enabled
2] The remote computer is turned off
3] The remote computer is not available on the network
Make sure the remote computer is turned on and connected to the network, and that remote access is enabled.
The next port of call was to check RD gateway and we found that the second gateway was still part of the RD gateway farm. From Windows Server 2012, RDS is administered in the Server Manager console which included configuration for Session Collections, RD Web Access, Broker Deployment, and RD Licensing. One aspect that is not fully managed via the console is Remote Desktop Gateway. One key takeaway is after adding or removing RD gateway from the server manager console check if the RD gateway server has been removed from the RD gateway manager.
*Further investigation showed that the configuration had Bypass RD Gateway server for local addresses checked resulting in a different outcome when connectingfrom localnetworks as it bypasses the RD gateway. Unhecking this enforces all connections through the RD gateway.
Category:
Technology
Tags:
RDS, troubleshooting, Windows Server 2012
Previous Post: Why You Should Move Your IT to the Cloud
Next Post: Protect Your Identity in the Cloud With Multi-Factor Authentication
How to resolve common problems with Windows Remote Desktop
Janne Ruostemaa
staff
Troubleshooting Updated on 2022-03-30 72
If you have problems using Remote Desktop (RDP) with your Windows server, there are a couple of things you can fix. This troubleshooting guide aims to help rule out some of the most common causes for poor functionality.
Try UpCloud for không lấy phí! Deploy a server in just 45 seconds
RDS Connection Broker or RDMS fails after you disable TLS 1.0 in Windows Server
This article provides methods to make sure Remote Desktop service (RDS) Connection Broker and Remote Desktop Management service (RDMS) can work as expected.
Applies to: Windows Server 2022, Windows Server 2012 R2
Original KB number: 4036954
Symptoms
Assume that you use the inbox Windows Internal Database (WID) in Windows Server. If you disable Transport Layer Security (TLS) 1.0 when you configure security settings, you experience the following issues:
5 Replies
· · ·
Jalapeno
OP
MSC
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.
Feb 20, 2022 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
davidfesliyan
Feb 20, 2022 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 (2022 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
davidfesliyan
Feb 20, 2022 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 sự kiện.
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
davidfesliyan
Feb 22, 2022 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
davidfesliyan
Feb 22, 2022 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 help
0
This topic has been locked by an administrator and is no longer open for commenting.
To continue this discussion, please
ask a new question.
Reply
4
0
Chia sẻ
Chia Sẻ Link Tải Troubleshoot Remote Desktop Connection Broker miễn phí
Bạn vừa tìm hiểu thêm nội dung bài viết Với Một số hướng dẫn một cách rõ ràng hơn về Video Troubleshoot Remote Desktop Connection Broker tiên tiến và phát triển nhất và ShareLink Tải Troubleshoot Remote Desktop Connection Broker Free.
Giải đáp vướng mắc về Troubleshoot Remote Desktop Connection Broker
Nếu sau khi đọc nội dung bài viết Troubleshoot Remote Desktop Connection Broker vẫn chưa hiểu thì hoàn toàn có thể lại Comments ở cuối bài để Admin lý giải và hướng dẫn lại nha
#Troubleshoot #Remote #Desktop #Connection #Broker