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

Hi, Thank you for your reply. Here are some suggested solutions. 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. 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. 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. 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. ---

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.

I found the same issue. While trying to login in the server 2019. Suddenly, I start facing the issue "an error occurred" & the session hardly take 1 ms to response. After investigation I found that the server port was hung & even after reboot something was blocking the server to get RDP. Even, mstsc /admin was also not working. During the investigation it was detected that the server was throwing some incorrect errors also like certificate issue & throw some Schannel errors too. Renaming the folder c:\ProgramData\Microsoft\Crypto\RSA\MachineKeys & changing the port of RDP 3389 to 3388 in my case it helps. Later on you can roll back it to 3389 . Port change reg path :- HKLM\system\CCS\Control\terminal server\winstations\RDP-TCP\ then navigate to port number (default value d3d) d3c means 3388. Note:- TLS1.2 should be enabled. Enjoy the fix.

I would like to follow up on @Mitch Steinsberger answer. I usually find it necessary to SAVE AS to a new RDP file. Then go to OPTIONS -> Experience and save something. The next time i hit connect, it blanks out the user name. Usually, when this happens, whatever issue has been avoided and your connection will work. this always catches me when Im super slammed and dont have the 40 minutes it takes to remember how to get around this! hope it helps

Remote desktop connection: An internal error has occurred

Lê Phùng Hiến 61

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

Grace HE 1,241 Reputation points

2021-03-10T01:43:18.887+00:00

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.---
Sohon HIM 6 Reputation points

2021-09-22T01:58:09.62+00:00

hi Please kindly fix for me ,

The issues is that : an internal error has occurred
mitch stein 31 Reputation points

2022-11-09T01:02:53.623+00:00

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

Accepted answer

Grace HE 1,241 Reputation points

2021-03-08T09:51:19.22+00:00
Hi,
Thank you for your reply. Here are some suggested solutions.

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.

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.

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.

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. ---
Please sign in to rate this answer.

10 people found this answer helpful.
Lê Phùng Hiến 61 Reputation points

2021-03-10T21:15:37.76+00:00

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

Yuvaraju, Vemala | Saras America 1 Reputation point

2021-03-16T05:20:24.987+00:00

Option 3 is worked on most of the servers.

Ashok kumar 6 Reputation points

2021-07-02T11:15:46.413+00:00

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

Deena Kistasami 1 Reputation point

2021-07-24T15:07:44.267+00:00

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

Dynamics Admin 1 Reputation point

2021-08-28T08:55:47.15+00:00

Yes option 3 worked for me

Brian Johnson 1 Reputation point

2021-09-18T20:03:00.913+00:00

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.

Bill Pennock 1 Reputation point

2021-09-29T20:19:21.733+00:00

None of these have worked for me. One thing I am unclear about. Since this shows up as an Internal Error on the client machine I assumed the solution would be changes to the client machine. #4 and possibly others appear to be settings on the target (machine I'm trying to connect too). Can you clarify please. This is happening on multiple computers and multiple targets. I have depended on RDP for a long time and this just started happening a few weeks ago, perhaps as many as 8 to 10 weeks. The only place I can RDP without the error is to the server on my LAN.

Thomas Levesque 1 Reputation point

2021-10-16T16:30:00.727+00:00

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

Jacobo Cano 1 Reputation point

2021-10-21T01:49:21.47+00:00

This works for me, thank you!

Anthony NGOP-LOTI 1 Reputation point

2021-11-02T01:45:33.96+00:00

Thank you Grace, the third option has worked for me on Windows 7 machine

Rainer, Lynette 0 Reputation points

2023-03-20T20:34:23.9833333+00:00

The number 4. resolution fixed the issue. Thanks for the tips!!!

NAVARRO CALDERON, HARUMY REBECA 0 Reputation points

2023-06-30T15:27:44.9866667+00:00

La opción 3 y luego la 4 funcionó.

Joseph Mornhineway 0 Reputation points

2023-06-30T20:17:28.4966667+00:00

Thank you! Number 3 fixed the issue of not being able to connect. I would still like to be able to fix the SSL connection was working.

Working on Windows server 2019 standard

Thank you! Number 3 fixed the issue of not being able to connect. I would still like to be able to fix the SSL connection was working.

Carl Santoro 0 Reputation points

2023-07-18T12:59:47.0333333+00:00

My issue too was resolved with:

Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security

David Torres 0 Reputation points

2023-09-22T17:27:39.45+00:00

This worked for me !, I only had to go to Step #2 before it was fixed (Set MTU Value to 1458)
Sign in to comment

11 additional answers

Simon Kravis 1 Reputation point

2021-10-04T22:41:12.643+00:00

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.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment
YaroC 311 Reputation points

2022-10-20T20:15:02.183+00:00

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.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment
Sachin Kumar 0 Reputation points

2023-01-17T18:49:30.8633333+00:00

I found the same issue. While trying to login in the server 2019. Suddenly, I start facing the issue "an error occurred" & the session hardly take 1 ms to response.

After investigation I found that the server port was hung & even after reboot something was blocking the server to get RDP. Even, mstsc /admin was also not working.

During the investigation it was detected that the server was throwing some incorrect errors also like certificate issue & throw some Schannel errors too.

Renaming the folder c:\ProgramData\Microsoft\Crypto\RSA\MachineKeys & changing the port of RDP 3389 to 3388 in my case it helps. Later on you can roll back it to 3389 .

Port change reg path :- HKLM\system\CCS\Control\terminal server\winstations\RDP-TCP\ then navigate to port number (default value d3d) d3c means 3388.

Note:- TLS1.2 should be enabled.

Enjoy the fix.
Please sign in to rate this answer.
Sachin Kumar 0 Reputation points

2023-01-18T12:33:49.3033333+00:00

Super....

It works.

Sachin Kumar 0 Reputation points

2023-01-19T05:38:06.3133333+00:00

Ys, it works
Sign in to comment
Greg McFarlane 0 Reputation points

2023-02-10T17:23:46.3933333+00:00

I would like to follow up on @Mitch Steinsberger answer.

I usually find it necessary to SAVE AS to a new RDP file.

Then go to OPTIONS -> Experience and save something.

The next time i hit connect, it blanks out the user name. Usually, when this happens, whatever issue has been avoided and your connection will work.

this always catches me when Im super slammed and dont have the 40 minutes it takes to remember how to get around this!

hope it helps
Please sign in to rate this answer.

0 comments No comments
Sign in to comment