Kinh Nghiệm về Remote Desktop can t connect to the Remote computer Server 2012 R2 Chi Tiết
You đang tìm kiếm từ khóa Remote Desktop can t connect to the Remote computer Server 2012 R2 được Cập Nhật vào lúc : 2022-02-20 01:23:15 . Với phương châm chia sẻ Kinh Nghiệm về trong nội dung bài viết một cách Chi Tiết 2022. Nếu sau khi Read tài liệu vẫn ko hiểu thì hoàn toàn có thể lại Comment ở cuối bài để Admin lý giải và hướng dẫn lại nha.
Symptoms
When this issue occurs, you receive the following error message that prevents you from accessing the Remote Desktop Services (RDS) server:
Nội dung chính
- Hotfix informationTroubleshoot Remote desktop disconnected errorsIs this page helpful?In this articleHow to fix ‘remote desktop can’t connect to the remote computer’Top reasons for ‘remote desktop can’t connect to the remote computer’ errorWindows updatePublic network profileWindows 2012 R2 Remote Desktop Enabled Cannot RDP ConnectVideo liên quan
Your computer can’t connect to the remote computer because the Remote Desktop Gateway server is temporarily unavailable. Try reconnecting later or contact your network administrator for assistance.
Additionally, you have to restart the RD Gateway service to regain the access.
You may also notice that the Terminal Services Gateway (TSGateway) svchost.exe process is taking excessive CPU time.
Hotfix information
Important Do not install a language pack after you install this hotfix. If you do, the language-specific changes in the hotfix will not be applied, and you will have to reinstall the hotfix. For more information, see Add language packs to Windows.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for tải về, there is a “Hotfix Download Available” section the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual tư vấn costs will apply to additional tư vấn questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:
://tư vấn.microsoft/contactus/?ws=supportNote The “Hotfix Download Available” form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
Prerequisites
To apply this hotfix, you must have April 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 (2919355) installed in Windows Server 2012 R2.
Registry information
To use the hotfix in this package, you do not have to make any changes to the registry.
Restart requirement
You may have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
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.
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 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.
16 Replies
· · ·
Chipotle
OP
CoryHamma
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.
Aug 24, 2022 16:09 UTC
Califorensics is an IT service provider.
Is the time working properly? For example, is the machine you’re connecting from, as well as this server, set to synchronize with a NTP server? I’ve fixed issues before that occurred when time drift left one of the PCs too far off from each other.
0
· · ·
Cayenne
OP
CoreyN
Aug 24, 2022 16:11 UTC
Do you receive any error messages when you attempt to remote to it?
Do the sự kiện logs show anything?
1
· · ·
Habanero
OP
Tim-H
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.
Aug 24, 2022 16:12 UTC
I would just start uninstalling all the updates you recently applied until it starts working again.
Why isn’t this a VM?
1
· · ·
Cayenne
OP
MulieloDan
Aug 24, 2022 16:17 UTC
Are you trying to connect with IP, or DNS name? If DNS name, does it resolve to the proper IP address?
And, I know you said you checked them all (the suggestions in that link…), but did you try to reboot the server after you checked them all?
0
· · ·
Thai Pepper
OP
Dan8422
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.
Aug 24, 2022 16:30 UTC
Is the time working properly? For example, is the machine you’re connecting from, as well as this server, set to synchronize with a NTP server? I’ve fixed issues before that occurred when time drift left one of the PCs too far off from each other.
I checked the time. It was OK. But good one. That one has caught me with some other things.
0
· · ·
Chipotle
OP
Pure Genius
Aug 24, 2022 16:34 UTC
Anything in group policy overriding? Also, I know it’s silly, but did you check you are in the Remote Desktop users group?
0
· · ·
Thai Pepper
OP
Dan8422
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.
Aug 24, 2022 16:35 UTC
The only error message was:
Nothing in the sự kiện log. I could even remote registry, remote computer management – everything seemed to be working.
Tried IP & DNS name.
I fixed it but I don’t understand why this fixed it. But I’m not going to question why. It’s working again.
I went into the Remote tab of computer properties – turned off allow RDC and then turned it back on. That’s it. It’s working now. Don’t know why I didn’t try that before. I’ve been messing around with this for a week or so on and off when I had time.
CRAZY!! Ugh!
1
· · ·
Chipotle
OP
Pure Genius
Aug 24, 2022 16:38 UTC
I had something similar with a Server 2012 box in recent memory, I just can’t remember what fixed it ultimately. I’m happy least it wasn’t too much more than just re-enabling boxes ?
1
· · ·
Tabasco
OP
TravisIT
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.
Aug 24, 2022 19:39 UTC
Same exact thing happened to me.
I found that somehow, the current network got switched to Public Network instead of Private Network. RDP is automatically set to deny connections when it’s set to a Public Network. I switched my network type to Private and it fixed everything.
EDIT: You can test this by going into the Windows Firewall settings > Inbound > Remote Desktop – User Mode (TCP-In) > Advanced Tab > Check the Public box, then try and RDP into the server.
Edited Aug 24, 2022 19:52 UTC
2
· · ·
Thai Pepper
OP
Dan8422
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.
Aug 24, 2022 20:08 UTC
Same exact thing happened to me.
I found that somehow, the current network got switched to Public Network instead of Private Network. RDP is automatically set to deny connections when it’s set to a Public Network. I switched my network type to Private and it fixed everything.
EDIT: You can test this by going into the Windows Firewall settings > Inbound > Remote Desktop – User Mode (TCP-In) > Advanced Tab > Check the Public box, then try and RDP into the server.
I checked that. I’ve had so many issues with Win7, 8, 10 doing screwy things like that I sort of expected it. But it was good. I still can’t believe turning RD off and back on again fixed it. Windoze!
1
· · ·
Serrano
OP
kateswistowicz
Aug 24, 2022 21:23 UTC
I know this sounds crazy, but I’ve been having my 12servers changing from the “domain” network to a work or public network (when you hover over the network icon down by the time). The only way I could force this to recognize that the IP was part of my domain network was to toggle off or on IPv6. I only use IPv4, but I couldn’t figure out any other way. Your firewall settings are probably preventing RDP on non-domain networks.
2
· · ·
Thai Pepper
OP
Dan8422
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.
Aug 25, 2022 15:11 UTC
I’ve had lots of goofiness with IPv6 turned on – on Server 2012 & sometimes on Win10 boxes too. I don’t understand why if you don’t have it turned on anywhere else – switches, etc. No “one” else should be seeing it in a switched environment if the switches aren’t passing the traffic…
Regardless I turn it off on everything that has the option. i hope I’m retired by the time I need IPv6 on the inside of the firewall.
2
· · ·
Pimiento
OP
Mark Cockburn
Feb 2, 2022 14:31 UTC
1st Post
It’s not as crazy as you might think, cause it hit the source of my issue right on the nose! We had a power fluctuation, which caused the server to reboot hard (despite an APC3000RS Smart UPS in place – checking that out now). The hard reset must have resulted in a fault on the network adapter as it was not showing a connection to the domain/private network. I was able to ping the server’s IP address just fine, shared directories were accessible but could not connect via remote desktop.
I disabled and re-enabled the adapter on the server, and it came back up connected to our domain. After that, remote desktop sessions worked as normal.
Thanks katewistowicz!
2
· · ·
· · ·
Pimiento
OP
Theo Quach
Sep 17, 2022 04:01 UTC
1st Post
A GUI way of making this change:
Hit Winkey R to open Run prompt and type gpedit.mscNavigate to: Computer Configuration/Windows Settings/Security Setting /Network List Manager Policies.Choose your Network name in the right panel.
Note: To show networks not currently connected, right-click Network List Manager Policies in the left pane and choose Show All Networks.
Go to Network Location tab and change the Location type from Public to Private.
Close Local Policy Editor.
0
· · ·
Pimiento
OP
DeanMac
Jul 31, 2022 20:10 UTC
1st Post
Thanks Mark Cockburn.
Disabled and Enabled the network device and all is well again. One additional note. In my case, the adapter not being connected to the domain meant that the adapter reverted to using the default Firewall profile of “Guest or Public Network” instead of “Domain Networks”. RDP connections are not allowed in the Public Network profile. Once I disabled and reenabled the adapter, the adapter saw the domain and the Firewall profile automatically flipped back to “Domain”.
Thanks
DMac
0
· · ·
Anaheim
OP
tonyv
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.
Aug 13, 2022 21:24 UTC
Great suggestion! For months I was unable to Remote into one Server 2012r2, and followed your advice to look Windows Firewall, Advanced Settings, and then enable the Remote Desktop rules for User Mode (TCP-in), User Mode (UDP-in) and Shadow (TCP-in). NOW I can Remote into it! Thanks lots!
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.
Windows 2012 R2 Remote Desktop Enabled Cannot RDP Connect
- 34 CommentsServer Tips, Windows 2012
Reply
3
0
Chia sẻ
Clip Remote Desktop can t connect to the Remote computer Server 2012 R2 ?
Bạn vừa đọc tài liệu Với Một số hướng dẫn một cách rõ ràng hơn về Video Remote Desktop can t connect to the Remote computer Server 2012 R2 tiên tiến và phát triển nhất
Share Link Download Remote Desktop can t connect to the Remote computer Server 2012 R2 miễn phí
Heros đang tìm một số trong những Chia SẻLink Download Remote Desktop can t connect to the Remote computer Server 2012 R2 Free.
Thảo Luận vướng mắc về Remote Desktop can t connect to the Remote computer Server 2012 R2
Nếu You sau khi đọc nội dung bài viết Remote Desktop can t connect to the Remote computer Server 2012 R2 , bạn vẫn chưa hiểu thì hoàn toàn có thể lại phản hồi ở cuối bài để Mình lý giải và hướng dẫn lại nha
#Remote #Desktop #connect #Remote #computer #Server