Fixing an internal error when connecting to a remote desktop

An internal error has occurred The Remote Desktop Connection Error Error is a very vague error message. It usually happens when a user tries to connect to a remote computer. This could be due to a weak network connection, a misconfigured remote connection, etc.

Since the remote desktop connection is used by many users for business or personal purposes, this error can be very annoying. For example, when trying to connect from Windows 10 to a server running Windows Server 2012 R2 via RDP, we got the following error:

an internal error when connecting to a remote desktop

This could be the result of installing and configuring RemoteApps. The RDP console message “An internal error occurred” can occur in several cases and can be caused by both a problem with the Remote Desktop Server and a problem with the client.

Remote Desktop Connection: There was an internal error

Reasons for connecting to Remote Desktop An internal error has occurred

Connection settings :
For some users, the Remote Desktop Connection client settings may be the cause of this error.

RDP Security :
In some cases, the error may be due to the security of the protocol for Remote Desktop. In this case, we need to change the security level.

Computer Area :
Another possible cause could be the domain the system connects to. In this case, deleting the domain and reintegrating it will solve the problem.

Before applying the solutions listed below, please make sure that you are using an administrator account. We also recommend that you follow the solutions listed in the order listed so that you can quickly isolate the problem.

To fix the message “Internal error Occurred”.

Change Remote Desktop Connection Settings

Change Remote Desktop Connection Settings

First, let’s try to isolate the problem by changing the RDP settings a little bit.
Some users have reported that their problem has been resolved after checking “Reconnect if a connection is broken”. This can be done by following these steps:

  • Go to the Start menu, find “Remote Desktop Connection” and open it.
  • Click “Show Options” to make all settings visible.
  • Click the “Experience” tab and make sure that the “Reconnect if the connection is disconnected” checkbox is checked.
  • Attempt to reconnect to the domain.
Connect to the domain

Sometimes the error message is due to the domain to which you have connected your system. In this case, you can fix the problem by deleting the domain and reintegrating it. Please do the following:

  • Press Windows + I to open settings.
  • Go to Accounts, then click on the Access to Work or School tab.
  • Select the domain to which you have connected your system, and then click Disconnect.
  • Click Yes when prompted to confirm.
  • Shut down the system and restart your computer when prompted.
  • After you restart the system, you can log back into the domain if you wish.
  • Try to use RDP again.
Modify the MTU value

Another way to solve the problem would be to change the MUT value. The maximum transmitter size is the largest packet size that can be sent over the network. Reducing the MTU value may help to solve the problem.
How to do it:

  • To change your MTU value, you need to download a tool called TCP Optimizer. You can download it from here.
  • After downloading it, open TCP Optimizer as an administrator.
  • At the bottom, before selecting settings, select Custom.
  • Change the MTU value to 1458.
  • Click Apply changes and exit the program.

Check if this solves the problem.

Modifying the RDP security within the Political Writers group.

In some cases, the error message appears because of your RDP security level in Windows Group Policy. In such scenarios, you should enforce the RDP security level. Do the following:

  • Go to the Start menu, find Local Group Policy and open Change Group Policy.
  • Navigate to the following directory:
  • Computer Configuration > Administrative Templates > Windows Components > Remote Desktop
  • Services > Remote Desktop Session Host > Security.
  • On the right side, find the option “Require use of a specific security level for remote connections (RDP)” and double-click it to change it.
  • If it is set to Unconfigured, select Enabled, and then select RDP before Security Layer.
  • Click “Apply” and then click “OK”.
  • Reboot the system for the changes to take effect.
  • Try logging in again.
Disable network authentication

You can also try to solve the problem by disabling network-level authentication (NLA). Sometimes the problem can be caused by you or the target system is configured to allow only remote connections that run Remote Desktop with NLA. Disabling it will solve the problem, and here’s how:

  • Go to your desktop, right-click on that computer, and select Properties.
  • Click Remote Settings.
  • In the Remote Desktop section, uncheck Allow connections only from computers running Remote Desktop with network authentication.
  • Click the Apply button, and then click the OK button.
  • See if this helps isolate the problem.
Restart Remote Desktop

In some cases restarting the Remote Desktop, service will be helpful, so at this point, we will restart it manually.
To do this :

  • Press “Windows” + “R” to open the “Run” command prompt.
  • Type “services.msc” and press “Enter”.
  • Double-click “Remote Desktop Service” and press “Stop”.
  • Click “Start” after 5 seconds of waiting.
  • Check to see if there is still a problem.
Disconnect VPN connection

Your computer may be configured to use a proxy or VPN connection, causing its Internet connection to be routed through another server, making it unable to connect properly.
In this step, we’ll disable the proxy settings in Internet Explorer, and you should also make sure that any VPNs running on your computer are disabled.

  • Press the Windows + R keys on your keyboard simultaneously.
  • A “Run” dialog box will appear, type “MSConfig” in the empty field and click OK.
  • Select the “Boot” option in the system configuration window and check the “Secure Boot” box.
  • Click “Apply” and click “OK”.
  • Now restart your computer to enter safe mode.
  • Again, simultaneously press the “Windows” + “R” keys and type “inetcpl.cpl” in the “Run” dialog box and press “Enter” to execute it.
  • The “Internet Properties” dialog box will appear on your screen, select the “Connections” tab there.
  • Uncheck “Use a proxy server for your local network” and click OK.
  • Open MSConfig again and this time uncheck the “Secure startup” option, save your changes and reboot your computer.
  • Check if the error message persists.
Modifying the configuration of local security policies

This is another way to solve the problem, in which you need to use the Local Security Policy utility. To do this, perform the following steps:

  • Press “Windows” + “R” to open the “Run” command prompt.
  • Type “Secpol.msc” and press “Enter” to run the Local Security Policy utility.
  • In the Local Security Policy utility, click the “Local Policy” option, and then click the “Security” option in the left pane.
  • Scroll down the right pane and click the “System Cryptography” option, and then click the “Security” option in the left pane.
  • Scroll down in the right pane to find the “System Cryptography” option: use FIPS 140 compliant cryptographic algorithms, including encryption, hashing, and signing algorithms.
  • Double-click this option and in the next window check the “Enabled” button.
  • Click “Apply” to save your changes, then click “OK” to close the window.
  • Check to see if this solves the problem on your computer.
Remote connections are possible

It is possible that remote connections on your computer are not allowed according to certain system configurations, so you see this error when you try to use RDP. So, in this step, we are going to reconfigure this setting in the control panel and then see if it solves the problem on our computer. To do this, we’ll do the following:

  • Press “Windows” + “R” to run the “Run” command line.
  • Enter “Control Panel” and press “Enter” to launch the classic Control Panel.
  • In the Control Panel, click on the “System and Security” option and then click on “System”.
  • Under “System Settings” in the left pane, click “Advanced System Settings”.
  • In the Advanced System Settings, click the “Remote” tab and make sure that the “Allow remote support connections to this computer” option is checked.
  • Make sure that the “Allow remote connections to this computer” tab below is also checked.
  • Click Apply to save your changes, then click OK to exit the window.
  • Check to see if this solves the problem on your computer.

Most Frequently Asked Questions

  1. Go to the Start menu, find "Remote Desktop Connection" and open it.
  2. Click Show Settings to see all the settings.
  3. Click the "Experience" tab and make sure the "Reconnect when disconnected" checkbox is checked. Change the PDR settings.
  4. Try connecting again.

  1. Locate the remote desktop client, right-click it, and select Properties from the menu.
  2. Click the Compatibility tab and check the option Run this program as administrator. Now click Apply and OK to save your changes.

Select the remote desktop name, Ctrl-click, and select Reset from the context menu. Click the Settings button (cogwheel icon) in the upper right corner of the window, select Applications in the left pane, click Reset, and then click Next.

Because of a security error, the client was unable to connect to the terminal server. Make sure you are connected to the network and try connecting to the server again. The remote desktop was disconnected. Because of a security error, the client was unable to connect to the remote computer.

Website | + posts

Mark Ginter is a tech blogger with a passion for all things gadgets and gizmos. A self-proclaimed "geek", Mark has been blogging about technology for over 15 years. His blog, techquack.com, covers a wide range of topics including new product releases, industry news, and tips and tricks for getting the most out of your devices. If you're looking for someone who can keep you up-to-date with all the latest tech news and developments, then be sure to follow him over at Microsoft.