The error, Remote Desktop RDP Connection is usually caused by an incorrect RDP setup or local group security policy. Due to which, ‘There has been an internal error’ message displays. In this article will discuss the primary reasons for remote desktop connection error and how to fix it.
An Internal Error has Occurred: Remote Desktop Connection
As we all know that many people rely on Remote Desktop Connections for work or personal reasons, this issue can be a real annoyance. We encountered the issue an internal error has occurred in RDP while attempting to connect through Remote Desktop Connection (RDP), a Windows 10 server to another one that ran Windows Server 2012 R2 with RDP.
It’s possible that it occurs due to Remote Apps installation and settings. “An internal error has occurred” RDP console message might appear in a variety of situations, and the reason for this could be a Remote Desktop server or client problem.
Let’s have a look at a couple of approaches our support techs employ to fix the problem, in this article.
Causes of Remote Desktop Connection: An Internal Error has Occurred
- Connection settings: For some users, this problem could originate because of their RDP Connection client settings.
- RDP Security: In some circumstances, the error can occur due to the Remote Desktop Protocol’s security. We must modify the security layer in this scenario.
- The domain of the computer: Another explanation could be the domain to which the machine connects. In this scenario, deleting the domain and then rejoining it will resolve the problem.
An Internal Error Has Occurred: Remote Desktop Connection Solutions
To begin, verify that RDP port 3389 on the RDS server accepts connections; the connection should not be blocked by a firewall (Test-Net Connection your RDP server- port 3389).
The MS-Windows-Remote Desktop Services- RdpCoreTS/Operational log, for example, once revealed that it created an RDP session.
Client (IP address): 64379. The server accepts a new TCP connection.
RDP-Tcp#4 connection established. The RDP session, on the other hand, terminates the latter without error:
The main connection (RDP) and the client is terminated by the server. The reason for the disconnect is 0. On our remote server, we need to check status of RDP services before restarting the service.
We can accomplish it remotely using the command:
Services. msc console (“Connect to another machine” option),
But PowerShell makes it much easier to verify service’s status and start again using the below command:
(Get-Service TermService –ComputerName ny-rds1). status.
We restart the service after it is up and running:
Restart-Service –force-verbose | Get-Service TermService-ComputerName ny-rds1
Let’s have a look at some of the other ways our Support Technicians utilize to fix Remote Desktop Connection: There has been an internal error.
Other methods to fix the error
There are a few other ways to clear the remote desktop an internal error that has occurred. Resolving this issue can be difficult for some as you need to follow the correct steps.
- Navigate to C: ProgramDataMicrosoftCryptoRSA folder in the TerminalServices- RemoteConnectionManager event log and rename the Machinekeys folder to Machinekeys bak, then restart the term service.
- If the ‘configure H.264/AVC hardware encoding for Remote Desktop connections policy’ is enabled on the remote machine, the RDP problem occurs in Windows 10 1809. It can be found in the GPO section listed below: Remote Desktop Services -> Windows Components-> Remote Desktop Services -> Remote Desktop Session Host-> Remote Session Environment for fixing the problem of remote desktop connection an internal error occurred, you need to create the fClientDisableUDP option in the registry key with the value 1 to deactivate the UDP protocol for RDP. HKLM/SOFTWARE/Policies/Client for Microsoft Windows NT Terminal Services.
- If the issue displays right after you click connect, you should try increasing the maximum number of RDP connections that are outstanding. SKUs are set as 100 by default in Windows 10, but 3000 in Windows Server. Create the DWORD registry parameter MaxOutstandingConnections in the reg key HKEY LOCAL MACHINESYSTEMCurrenrControlSetControlTerminal Server with the value 10000 using Regedit,exe.
- Clear the RDP connection history in the registry value HKEY CURRENT USERSoftwareMicrosoftTerminalServerClientServers on the client system. Reset the RDP cache in C: Users percent Username percent. AppDataLocalMicrosoftTerminal Server Clientache” R “C: Users percent Username percent AppDataLocalMicrosoftTerminal Server Clientache” R Restart the computer if necessary.
Moving forward, our support technicians discovered that there are a number of different options for resolving ‘Remote Desktop Connection: An Internal Error has Occurred.’ Let’s take a closer look at it.
Change the settings for the remote desktop connection
To begin with, we will change the RDP settings to see if we can isolate the problem. Some users have claimed that if they clicked the ‘Reconnect if the connection is dropped’ option, their problem was solved.
Let’s take a look at how we can achieve it:
Open Remote Desktop Connection by going to the Start Menu and searching for it. To see all of the options, select show options. Make sure the ‘Reconnect if the connection is dropped’ box is checked on the Experience tab. Reconnect if necessary.
Rejoin Domain
The error message is occasionally created as a result of the domain to which our system is connected. In certain scenarios, deleting the domain and then rejoining it will be the problem.
Here’s how we go about it:
To open Settings, press Windows Key+ 1. Switch to the Access work or school tab after going to Accounts. Click Disconnect after selecting the domain that is connected to our system. When prompted to confirm, select yes. After disconnecting the system, restart it as directed. If necessary, rejoin the domain once more. Try using RDP once more.
Change MTU Value
Changing the MTU value is another option for resolving the problem of remote desktop an internal error has occurred. The MTU i.e., Maximum Transmission Unit is the highest packet size that can be transferred through a network. You can resolve the problem i.e., an internal error occurred by dropping the MTU value.
Here’s how we go about it:
TCP Optimizer can be used to modify the MTU value. Open TCP Optimizer as an administrator once it has been downloaded. Select Custom in front of choose settings at the bottom. MTU should be set to 1458. Exit the software after clicking Apply Changes. Check to see whether the problem has been resolved.
Change Security of RDP in Group Policy Editor
The error message appears in some situations as a result of our RDP security layer in Windows group policies. We will have to force it to use the RDP Security layer in such cases.
Here’s how we go about it:
Open ‘Edit group policy from the Start Menu by searching for Local Group security Policy in the Start Menu. To get started, go to the following directory: Remote Desktop Services > Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security.
Double-click the ‘Require usage of specified security later for remote (RDP) connections’ on the right-hand side to edit it. Then tap OK after clicking Apply. To make the modifications take effect, restart the computer. Reconnect if necessary.
Disable Network Level Authentication
We can also try removing Network Level Authentication, or NLA, to see if that helps. When we or the target machine is configured to only accept remote connections that are running Remote Desktop with NLA, the issue can occur. The problem will be resolved by disabling it.
Here’s how we go about it:
Right-click on This PC and select Properties from the drop-down menu. Select Remote Settings from the menu. Uncheck the box that says “Allow connections only from systems running Remote Desktop with Network Level Authentication” under Remote Desktop. Then tap OK after clicking Apply, check to see whether that solves the problem.
Restart Remote Desktop Service
In some cases, restarting the Remote Desktop Service solves the problem, so we will do that in this step.
To open the Run prompt, press “Windows” + “R”. Press “Enter” after typing “services.msc.” “Stop” is selected. After waiting at least 5 seconds, click “start”. Check to check whether the problem still exists.
Disable VPN Connection
It’s possible that our machine has been set up to use a proxy or VPN connection, in which case our internet connection will be routed through a different server. This could be stopping you from successfully establishing a connection. As a result, in this step, we will disable the proxy settings in Internet Explorer and any VPNs that may be active on the machine.
Simultaneously press the Windows + R keys on the keyboard. A run dialogue box will show on the screen; in the empty box, type “MSConfig” and hit OK. From the system configuration window, go to the boot option and tick the “Safe Boot” box. Apply the changes and then OK. To enter safe mode, restart your computer.
Conclusion
To conclude, RDP settings or local group security policy can cause the error Remote Desktop Connection Error: Internal Error has Occurred. However, there are several options that we have listed above for resolving this issue. Try those, one or the other method will surely work.