RDS Remote Desktop can t connect to the remote computer for one of these reasons
Khắc phục lỗi "remote desktop can't connect to remote computer" - Hướng dẫn chi tiết nhấtchaupm 1403 24-11-2020 Bên cạnh sự tiện lợi, sự gia tăng nhu cầu làm việc tại nhà cũng thúc đẩy nhu cầu sử dụng các máy tính kết nối từ xa. Tuy nhiên, có thể xảy ra một số lỗi kỹ thuật trong quá trình sử dụng, bao gồm các lỗi phổ biến như "remote desktop không thể kết nối với máy tính từ xa". Show
Vậy, làm thế nào để khắc phục lỗi này? Để trả lời này hãy cùngBizfly Cloud tìm hiểu một số thông tin cơ bản. Remote desktop là một tính năng tiện lợi cho phép kết nối ảo với các máy tính khác chạy hệ điều hành Windows. Với tính năng này, người dùng có thể kết nối với các máy tính ở bất kỳ nơi nào trên thế giới, miễn là họ có thông tin đăng nhập (tên người dùng và mật khẩu) phù hợp để kết nối. Ngoài ra, kết nối mạng khỏe cũng là một yêu cầu quan trọng! Nếu đã có thông tin đăng nhập và kết nối mạng ổn định mà vẫn gặp sự cố này, dưới đây là cách giải quyết: How to fix ‘remote desktop can’t connect to the remote computer’The remote machine connection timed out with PsPing As you can see in the screenshot above, I was unable to ping the remote machine, and the port was not reachable as well. If this works, and you are unable to ping the machine using the FQDN name, check whether DNS resolution is working properly. Sometimes the hostnameis pointingto another machine on DNS that is either offline or not in use. If you can't connect at all, a local firewall (Windows Firewall or third-party security software) or a network firewall might be blocking the port. The PowerShell command below lets you display the Windows Firewall state on the remote machine. Invoke-Command -ComputerName [ComputerName] -ScriptBlock {netsh advfirewall show allprofiles}Remote computer firewall status For testing purposes, you can disable Windows Firewall on the remote computer with this command: Invoke-Command -ComputerName Win7 -ScriptBlock {netsh advfirewall set allprofiles state off}Note that you should enable PSRemoting on the remote computer to execute the above command. If not, you can use PsExec to enable PowerShell remoting with the command below: psexec \\RemoteComputer -u administrator -p PASSWORD netsh advfirewall set allprofiles state offRemote Desktop can't connect to the remote computer for one of these reasons: for some usersGood morning, I have a small farm of 3 Windows 2019 RDS servers with load balancing. They are working quite well, but some users, about 4 now when they log in, it accepts their password, tries to log in, sits at estimating connection speed, then comes up with the can't connect for these reasons message like it can't connect at all. I can log in with a test user with the exact same permissions as the person getting this message and they will log in just fine. This happens internally and externally. image.png (124.4 KiB) Comment Comment Show 0 Comment 5 |1600 characters needed characters left characters exceeded ▼
Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total. JiaYou-MSFT answered • May 26, '21 | JiaYou-MSFT edited • May 26, '21 HI JamesRAtherton-0253, 1.Could you please enter winver in command prompt on both normal user's win10 computer and issue user's win10 computer, then look the OS version and OS version number ?[for example windows 10 enterprise 1809 (OS build 17763.316)] 6.What's type of RDS cal do you use? RDS per user cal or RDS per device cal? Event Viewer – Applications and Services Logs -Microsoft-Windows-RemoteDesktopServices-SessionServices_Operational 15.png (53.5 KiB) Comment Comment Show 0 Comment 5 |1600 characters needed characters left characters exceeded ▼
Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total. JamesRAtherton-0253 answered • May 28, '21 | JiaYou-MSFT commented • Jun 1, '21 I will be experimenting with the above, but I will answer a few items if I can. Working on other troubleshooting, the biggest issue is the randomness of this issue... 2.Are these 4 users account in the "remote desktop users group" of 3 Windows 2019 RDS servers?
3.Did you check the firewall setting block these 4 users' computer?
Did you check if these 4 users can remote access from other normal user's computer to w2019 session host successfully?
Comment Comment · Show 1 Comment 5 |1600 characters needed characters left characters exceeded ▼
Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total. JiaYou-MSFT · Jun 01, 2021 at 05:04 AM HI JamesRAtherton-0253, 1.According to my answer7, when the issue happen, do you find any logs about current issue? 2.When the issue user remote access the target server by using remote desktop connection, which phrase did he fail,can we find it? 0 Votes 0 · 12.png (62.8 KiB) JamesRAtherton-0253 answered • Jun 1, '21 As for the logs, no, actually, I can't seem to find anything remote or local in the logs to point me in the right direction, that is usually my first go to. As for Item #2. it's during the Configuring remote connection and sometimes on Estimating Connection Quality that this seems to happen. More the first than the second. Comment Comment Show 0 Comment 5 |1600 characters needed characters left characters exceeded ▼
Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total. JiaYou-MSFT answered • Jun 3, '21 | JiaYou-MSFT edited • Jun 3, '21 HI JamesRAtherton-0253, . We’ll look at the logs and events on the main stages of an RDP connection, I think your issue fail after authentication. ⦁ Network Connection; Tracking and Analyzing Remote Desktop Activity Logs in Windows client win10 Event Viewer – Applications and Services Logs -Microsoft-Windows-RemoteDesktopServices-SessionServices_Operational RDSH log Event Viewer – Applications and Services Logs – Microsoft – Windows-remoteapp and desktop connection management_admin (* include ============================================ Comment Comment Show 0 Comment 5 |1600 characters needed characters left characters exceeded ▼
Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total. JamesRAtherton-0253 answered • Jun 8, '21 Ok, I think I have the answer to the why, just not the "how to fix" it appears it is related to the load balancing. If you connect to say HQ and the load is low you connect right up, no issue. If you connect to HQ and load is high, it normally redirects you to BT or WP. This is where the failure occurs. Because it seems to be using the internal addresses when redirecting, and in doing so, client machine one is coming in on say 123.123.123.45 from the outside. It's then redirected to 111.111.111.25 which is the inside address for say BT. Fails... Connect to VPN, and do this again, connects to BT without an issue after redirect because now the outside machine can "see" BT. Hope this makes sense. Although the workaround is having everyone log into the VPN, I am trying to avoid that as a solution. I am sure it's the configuration I have in the broker but I am at a loss to what that is. Help is appreciated. Comment Comment Show 0 Comment 5 |1600 characters needed characters left characters exceeded ▼
Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total. JiaYou-MSFT answered • Jun 9, '21 | JiaYou-MSFT rolled back • Jun 9, '21 HI JamesRAtherton-0253, I think that I need a network and system topology so that I can know your current environment clearly. Since it is public forum, the private information can not be posted, I suggest you can open a case to Microsoft telephone support so that they can remote help you. Thanks for your understanding. https://support.microsoft.com/en-us/gp/contactus81?forceorigin=esmc&Audience=Commercial&wa=wsignin1.0 ============================================ Comment Comment Show 0 Comment 5 |1600 characters needed characters left characters exceeded ▼
Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total. General Remote Desktop connection troubleshooting
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 articleUse 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. |