Remote desktop connection: An internal error has occurred

Lê Phùng Hiến 61 Reputation points
2021-03-05T04:23:48.597+00:00

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
Remote Desktop
A Microsoft app that connects remotely to computers and to virtual apps and desktops.
4,190 questions
{count} votes

Accepted answer
  1. Grace HE 1,236 Reputation points
    2021-03-08T09:51:19.22+00:00

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

    10 people found this answer helpful.

11 additional answers

Sort by: Most helpful
  1. Nickolai Mcghie 11 Reputation points
    2021-07-09T03:09:15.79+00:00

    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.

    2 people found this answer helpful.

  2. Grace HE 1,236 Reputation points
    2021-03-05T08:40:58.253+00:00

    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.
      74689-image.png
    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. ---


  3. Neman Syed 1 Reputation point
    2021-06-08T18:23:06.36+00:00

    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://learn.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.

    0 comments No comments