An internal error has occurred Remote Desktop server 2016
Remote desktop connection: An internal error has occurredHi guys, Show
I have problem with RDP when connect to my Server (Windows 2016 std OS) Some time, remote desktop faild with message: An internal error has occurred (please see more detail in video link) Regards, Hien Le Link video: https://youtu.be/BPirG4F8KhU remote-desktop-services Comment Comment · Show 2 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. GraceHE-MSFT · Mar 10, 2021 at 01:43 AM Hi, --- if the suggestions above are helpful, please click ACCEPT ANSWER. Really appreciate. This will also help others with same issue to find this post quickly.--- 0 Votes 0 · SohonHIM-1673 GraceHE-MSFT · Sep 22, 2021 at 01:58 AM hi Please kindly fix for me , The issues is that : an internal error has occurred 0 Votes 0 · GraceHE-MSFT answered • Mar 8, '21 | AnthonyNGOPLOTI-6226 published • Nov 2, '21 Hi,
---If the suggestions above are helpful, please ACCEPT ANSWER. Really appreciate. This will also help others with similar issue to find this post quickly. --- Comment Comment · Show 10 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. LPhngHin-7668 · Mar 10, 2021 at 09:15 PM Hi Grace, Thank you for the support! The issue has been fixed after I turn off "receive side scaling" in the NIC Team config. Regards, Hien 2 Votes 2 · capture.png (187.6 KiB) ThomasLevesque-0570 LPhngHin-7668 · Oct 16, 2021 at 04:30 PM The only option that worked for me is option 4, which isn't ideal, but hey, at least it works now. 0 Votes 0 · JacoboCano-3496 LPhngHin-7668 · Oct 21, 2021 at 01:49 AM This works for me, thank you! 0 Votes 0 · YuvarajuVemalaSarasAmerica-1146 · Mar 16, 2021 at 05:20 AM Option 3 is worked on most of the servers. 0 Votes 0 · DynamicsAdmin-4267 YuvarajuVemalaSarasAmerica-1146 · Aug 28, 2021 at 08:55 AM Yes option 3 worked for me 0 Votes 0 · Ashokkumar-4630 · Jul 02, 2021 at 11:15 AM This one work for me guys..... Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security Regards, 0 Votes 0 · DeenaKistasami-7856 · Jul 24, 2021 at 03:07 PM Solution 3 worked for me. Thanks for the detailed troubleshooting guide. 0 Votes 0 · BrianJohnson-0784 · Sep 18, 2021 at 08:03 PM I would suggest trying number 3 first. It worked for me. It appeared to work but on retrying its back to multiple instances of An internal error has occurred before allowing the connection. 0 Votes 0 · Show more commentsGraceHE-MSFT answered • Mar 5, '21 | LPhngHin-7668 commented • Mar 7, '21 Hi,
---If the suggestions above are helpful, please ACCEPT ANSWER. Really appreciate. This will also help others with similar issue to find this post quickly. --- image.png (22.3 KiB) 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. LPhngHin-7668 · Mar 07, 2021 at 01:46 AM Hi Grace, Thank you for your support! I would like to answer your question as bellow: 1. RDP version: 2 & 3. No VPN connection is established Regards, Hien 0 Votes 0 · image.png (18.3 KiB) KoppNikolasexternal-7238 answered • Apr 19, '21 Possible duplicate / other tips: https://docs.microsoft.com/en-us/answers/questions/360403/rdp-stopped-after-update-must-reboot-server-repeat.html?childToView=362272 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. Neman answered • Jun 8, '21 Adding only for the record, as the problem could be at target computer rather than your source. Our problem was intermittent connection to an AWS EC2 instance which had been working fine for months. One user was logged in, but nobody else could connect. (RDP allows up to two simultaneous logins.) The solution was to confirm all users were logged out, reboot via the EC2 console, log in with an admin user, and forcibly disconnect all other interactive (i.e. supposedly human) users. After reboot/login: This error is too broad and captures too many possible problems with one message. 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. NickolaiMcghie-7555 answered • Jul 9, '21 | Patrick1 commented • Sep 6, '21 Denial of Service attacks on port 3389 (RDP) can also cause this issue. Just had to block request on a public webserver which had thousands of records revealing external entities attacking that port. After about 5 minutes of blocking external access to that port the internal network access worked. Comment Comment · Show 2 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. DanielOm-9781 · Aug 19, 2021 at 10:51 AM Indeed, since none of the suggestions above worked for me, I took a look in the event viewer. It appeared there were thousands and thousands of failed login attempts. The event viewer won't show the external IPs, so I used a port monitor for that. It's very unfortunate that RDP does not offer a block after N failed attempts, though there are 3rd party programs that can do this for you. Eventually I got rid of the hack-attempts by changing the RDP port number in the registry. //Daniel 0 Votes 0 · Patrick1 · Sep 06, 2021 at 10:15 PM Yep, that was the issue for me too. 0 Votes 0 · SimonKravis-3338 answered • Oct 4, '21 Not an answer but I often get the Internal Error message from RDP at various stages when accessing my VPS - sometimes before showing the login screen, sometimes after supplying credentials. If I try making the connection multiple times it usually works eventually. 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. Remote desktop connection: An internal error has occurred windows server 2016Windows server 2016 Remote desktop connection: An internal error has occurred windows-serverremote-desktop-servicesComment 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. learn2skills · Apr 14, 2021 at 06:59 AM To follow-up, Please let us know if you have further query on this. 0 Votes 0 · learn2skills answered • Apr 13, '21 Hi @BilalKhan-7668 This issue is already answered in the Q & A, please refer to the below url If the Answer is helpful, please click Accept Answer and up-vote, this can be beneficial to other community members. 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. Jingruihan-MSFT answered • Apr 14, '21 Hi dear, Please provide the details about the following component. If the answer is helpful, please click "Accept Answer" and upvote it. Best regards 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. Jingruihan-MSFT answered • Apr 19, '21 Hi, Haven't received your message in a few days, was your issue resolved? I am proposing previous helpful replies as "Answered". Please feel free to try it and let me know the result. If the reply is helpful, please remember to mark it as an answer which can help other community members who have the same questions and find the helpful reply quickly. Best regards, 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. RDP: An Internal Error Has OccurredChanging RDP SettingsHow to Fix “RDP an Internal Error has Occurred” in Server 2016Victor Ashiedu February 11, 2020 3386 Views 0 SaveSavedRemoved 0 Browse Post Topics
22 Replies
· · ·
Thai Pepper OP
redrumrudy
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.
Sure it's not a client issue using outdated protocols/ciphers/hashes/key exchanges? The server in question is not using SSL, only TLSv1 and higher? If these clients can RDP to other servers, are there any differences on the culprit server and the working server? The way I see it, if nothing else changed or was changed on the host prior to the upgrade, it would point to VMware. Were there any changes to the guest that were pending a reboot before the upgrade? Maybe run IISCrypto.exe on the server and clients. 1
· · ·
Habanero OP
Space Force Nov 9, 2017 at 18:27 UTC
So if a Mac can connect to it, can another Windows OS not on the domain connect to it? 1
· · ·
Poblano OP
KenNihart Nov 9, 2017 at 18:34 UTC
I didn't do the upgrade, unfortunately, but that is exactly when the error started kicking. It is updated regularly. It was hardened previously (again, not by me), but it had been working until the VMware was upgraded on it. I can connect to every other server in our environment except that one. I can actually connect to it from a Mac, which was confusing to me... I'll try running IISCrypto and see what I get from that. 0
· · ·
Poblano OP
KenNihart Nov 9, 2017 at 18:42 UTC
No, it cannot. I just tested that now to be sure. 0
· · ·
Poblano OP
KenNihart Nov 9, 2017 at 18:45 UTC
Also adding to the troubleshooting steps, I did run a chkdsk as well as sfc /scannow, both of which returned without error. 0
· · ·
Poblano OP
KenNihart Nov 9, 2017 at 19:17 UTC
So I ran IIS crypto, and it seems I was a little wrong. TLS, all 3, is enabled on this (don't ask me why; I didn't build it out...I'm just stuck trying to fix RDP) but SSL 2 and 3 is disabled. I was just kind of reading through Google searches trying to fix this issue, and I stumbled on the registry settings for TLS, which were set to ffffffff (I changed it to 1 and rebooted for testing, then put them back). Ciphers are Triple DES 168 and both AES. All hashes and key exchanges are checked. 0
· · ·
Habanero OP
Space Force Nov 9, 2017 at 19:18 UTC
Is there anything in the event viewer? 1
· · ·
Poblano OP
KenNihart Nov 9, 2017 at 19:23 UTC
The error message I posted in the first post is from the system log. It reoccurs every minute to few minutes, There is also this one in the RemoteDesktopServices-RDPCoreTS Operational log: RDP_TCP: An error was encountered when transitioning from StatePreparingx224CC in response to Event_ERROR_Sendingx224CC (Error code 0x0). That one only occurs when I attempt to connect to it (which means it is definitely receiving my RDP Requests). There is nothing that I can find on my local computer corresponding to my connection attempts. 0
· · ·
Thai Pepper OP
redrumrudy
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.
In that case, I would disregard the schannel errors and concentrate on the RDP event error. 1
· · ·
Poblano OP
KenNihart Nov 9, 2017 at 19:35 UTC
I just included because it started at the same time as the issue (and google links the 10013 internal error to RDP, so I figured it might be worth including). I try to include as much information as possible to hopefully trigger something that I might have overlooked. 0
· · ·
Thai Pepper OP
redrumrudy
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.
Also look at this: https://www.experts-exchange.com/questions/28915274/RDP-Issue-Connecting-to-Server-2012-R2-in-VMWare... 1
· · ·
Poblano OP
KenNihart Nov 9, 2017 at 19:41 UTC
I have done the accepted answer already (that's what I meant with the first thing I tried...sorry for not being clearer). I will try the powershell script for good measure. 0
· · ·
Poblano OP
KenNihart Nov 9, 2017 at 19:52 UTC
No dice...still doesn't work. As a note, I am not getting the 1057/8 error about the self signing certificate. 0
· · ·
Thai Pepper OP
redrumrudy
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.
What are the OSes of the non-Macclients? 0
· · ·
Poblano OP
KenNihart Nov 9, 2017 at 20:01 UTC
All Windows 10 Pro, I believe all the Creator's edition (I know that all 3 of the ones I have tested from are) 0
· · ·
Poblano OP
KenNihart Nov 13, 2017 at 17:31 UTC
Any insight from anyone else? I'm still fighting this battle over here...I'm opening tickets with several vendors, but I've got some big wigs starting to breathe down my neck too. 0
· · ·
Jalapeno OP
Jblancha-on-LV426 Nov 13, 2017 at 21:21 UTC
All. This happened to me as well. I tried tons of things but this is the fix. On the server in question go to C:\Program Data\Microsoft\Crypto\RSA Rename the MachineKeys folder in that directory. Restart the Remote Desktop Services and Remote Desktop Configuration services. That should re-create the Machinekeys folder. That's it it should work now. Thanks J 4
· · ·
Poblano OP
KenNihart Nov 13, 2017 at 21:40 UTC
I had tried similar to that before (removing the keys themselves rather than the whole folder), but I went ahead and tried exactly as you posted it, no dice. I even rebooted the server itself without success. Still the same error message as before. Thanks for the suggestion, though. 0
· · ·
Poblano OP
Best Answer
KenNihart Nov 14, 2017 at 19:55 UTC
FINALLY, I have found the answer. It is a strange answer that has nothing to do with my VMWare upgrades...but it is an answer nonetheless. In the local GP editor, I had to force it to use RDP security layer instead of allowing it to negotiate. With that, I also turned off NLA in the registry itself. With those two settings, everything now works. I have no idea how upgrading VM hardware could cause this, especially considering the server is rebooted weekly as part of a routine, so it couldn't have been a pending reboot thing. I got nothing on how it broke to begin with, but I wanted to make sure that the solution was recorded somewhere, just in case someone stumbles upon this post in a frantic search much like mine was. To all those that have helped me or thought about my little problem here, THANK YOU! You are all wonderful people. 2
· · ·
Habanero OP
Space Force Nov 14, 2017 at 19:57 UTC
Glad you got it sorted out. That one was a head scratcher. 0
· · ·
Pimiento OP
Gerry730 Mar 20, 2018 at 00:40 UTC
I have a strange problem with a Win7Pro 64B pc acting a TS (Using ThinStuff) with external client connecting via RDP are getting a strange error "An Internal Error has occurred". Has been working flawlessly for the last couple of years and just recently end users are getting this error. Can you elaborate on your soln - Quote " In the local GP editor, I had to force it to use RDP security layer instead of allowing it to negotiate. With that, I also turned off NLA in the registry itself. With those two settings, everything now works. " I'd like to check and test those settings on the Win7Pro. Thanks. 0
· · ·
Pimiento OP
christophermccord Apr 9, 2018 at 16:18 UTC
1st Post
I know this is an old thread, but I came on here specifically to say thank you! I've been working on the exact same issue for a few days on one of our new 2016 machines. Sadly it was already in production so that complicated things. Your solution worked perfectly. 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. |