RDP An internal error has occurred Server 2012 R2

• Home
• Anonymous
• Sign in to post
• Post
• Explore
• Tags
• Questions
• Site feedback
• Articles
• Users

Skip to main content

• • Tags
  • Questions
  • Site feedback
  • Articles
  • Users
• Sign in to post

• Home

question

Hi guys,

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)
- RDP client: Windows server 2016 or windows 10 pro
- Target: windows server 2016 std
- firewall off
- McAfee Enterprise antivirus unlocked all connection
Could you please help me to resolve this problem?

Regards,

Hien Le

Link video: https://youtu.be/BPirG4F8KhU

remote-desktop-services

Hi,
We are looking forward to your reply and ready for help.

--- 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 ·

hi Please kindly fix for me ,

The issues is that : an internal error has occurred

0 Votes 0 ·

This has been happing since server 2003 and still has not been fixed...

The work around is to chnge any setting on the client side in the remoe desktop gui, any setting at all, then retry to connect. I usually go for sharig the local drives to the server, then unsharing them and after 2 or 3 times sharing unsharing and trying to connect inbetween each itch it starts to works.

I never looked into what is actually causing the problem because when it happens I am usually in a hurry to get something done and this seems to work well..

This has been an issue on everyone of the thousands of servers I hve run since at least server 2003. through every update and through every new server overhaul. It also has happened on the client side of every version of windows from xp through windows 11, pro versions, home version etc etc etc... Microsoft has yet to address the isue, because every experienced network engineer knows the work around.. So in thier laziness, they let it be..

Frankly when you 1000+ $$ for an OS it should be relatively bug free, or at least work as well as a free OS like any flavor of linux.. Jeeeeeezzzz

0 Votes 0 ·

Hi,
Thank you for your reply. Here are some suggested solutions.

1. Change Remote Desktop Connection Settings
   Go to the Start Menu, search for Remote Desktop Connection, and open it up.
   Click on Show Options to unveil all the settings.
   Switch to the Experience tab and then make sure ‘Reconnect if the connection is dropped’ box is checked
   Try connecting again.
   

2. Changing MTU Value
   To change your MTU value, you will have to download a tool called TCP Optimizer. You can download it from https://www.speedguide.net/downloads.php.
   Once downloaded, open up TCP Optimizer as an administrator.
   At the bottom, select Custom in front of Choose settings.
   Change the MTU value to 1458.
   Click Apply Changes and then exit the program.
   Check if it fixes the issue.
   

3. Changing Security of RDP in Group Policy Editor
   Go to the Start Menu, search for Local Group Policy and open up ‘Edit group policy’.
   Navigate to the following directory:
   Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security
   On the right-hand side, locate the ‘Require use of specific security layer for remote (RDP) connections’ and double-click it to edit it.
   If it is set to ‘Not configured’, select Enabled and then in front of Security Layer, choose RDP.
   Click Apply and then hit OK.
   Restart your system so that the changes take effect.
   Try connecting again.
   

4. Disabling Network Level Authentication
   Go to your Desktop, right-click on This PC and select Properties.
   Click on Remote Settings.
   Under Remote Desktop, un-tick the ‘Allow connections only from computers running Remote Desktop with Network Level Authentication’ box.
   Click Apply and then hit OK.
   See if it isolates the issue.

---If the suggestions above are helpful, please ACCEPT ANSWER. Really appreciate. This will also help others with similar issue to find this post quickly. ---

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 ·

The only option that worked for me is option 4, which isn't ideal, but hey, at least it works now.

0 Votes 0 ·

This works for me, thank you!

0 Votes 0 ·

Option 3 is worked on most of the servers.

0 Votes 0 ·

Yes option 3 worked for me

0 Votes 0 ·

This one work for me guys.....

Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security
On the right-hand side, locate the ‘Require use of specific security layer for remote (RDP) connections’ and double-click it to edit it.
If it is set to ‘Not configured’, select Enabled and then in front of Security Layer, choose RDP.
Click Apply and then hit OK.
Restart your system so that the changes take effect.
Try connecting again.

Regards,
Ashok

0 Votes 0 ·

Solution 3 worked for me. Thanks for the detailed troubleshooting guide.

0 Votes 0 ·

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 comments

Hi,
Thank you for posting your query. According to your description above, I would appreciate if you can help me with more information. And here are some suggestions.

1. please check your RDP version.
   

   
   

2. When VPN'ed in from the computer in question, can you ping the remote network? If not then thats where the problem lies.
   If yes then can you ping any other device on the network. Is there any other server which you can try and connect to? does that work?
   

3. reset the VPN tunnel and set it to allow all traffic.
   

4. remove the PC from the domain and rejoined.

---If the suggestions above are helpful, please ACCEPT ANSWER. Really appreciate. This will also help others with similar issue to find this post quickly. ---

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
4. I tried to rejoin PC to the domain but still get same problem

Regards,

Hien

0 Votes 0 ·

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:
1. Open a command prompt (either as an admin user or an administrative command prompt)
2. Type qwinsta or query session (gives more info than query user) - see https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/qwinsta
3. Look at ID (session ID) column in the list of users. Determine which ones should be logged off. (Your current user has an > preceding its name.)
4. Type logoff 3 to forcibly logoff the user with session ID = 3. No output appears, but the session is terminated. (Run qwinsta a second time to confirm.)

This error is too broad and captures too many possible problems with one message.

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.

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 ·

Yep, that was the issue for me too.
My solution was to adjust the inbound rules on my firewall to only allow the specific IP address of my client.

0 Votes 0 ·

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.

In my case it was caused by changes in registries specifically to do with SCHANNEL. For instance RDS requires TLS1.0 client enabled. In my case I found that setting was fine but I had TLS1.1 and 1.2 disabled. 1.1 doesn't matter but when I re-enabled 1.2 the error went away.

question details

Related Questions