Remote desktop connection: An internal error has occurred

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

Answer 1

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

Answer 2

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.

Answer 3

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.

Answer 4

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

Answer 5

Possible duplicate / other tips:

https://learn.microsoft.com/en-us/answers/questions/360403/rdp-stopped-after-update-must-reboot-server-repeat.html?childToView=362272