An Internal Error has Occurred: Remote Desktop Connection Error

I noticed an odd message “An inner error has occurred” when attempting to attach from Windows 10 to a just lately deployed RDSH server working Windows Server 2012 R2 utilizing RDP. As recently as yesterday, the Remote Desktop connection to the server labored high-quality, however after the set up and configuration of RemoteApps and server restart, I used to be not ready to connect with its desktop. Obviously, the Remote Desktop Services appears to be working, since a consumer is prompted for a password when connecting.

As I’ve understood, the RDP console message “An inner error has occurred” might seem in numerous instances and be brought on by each Remote Desktop server and consumer points. In this text I attempted to explain all of the methods to resolve the issue and the state of affairs that had helped me.

windows 10 remote desktop connection error An internal error has occurred

First of all, be sure that the accepts connection in your RDS server, and that the connection isn’t blocked by the firewall ( your_rdp_server –port 3389).

Having studied the on the RDS server, I didn’t see any errors. The Microsoft-Windows-RemoteDesktopServices-RdpCoreTS/Operational log confirmed that the RDP session was created:

The server accepted a brand new TCP connection from consumer 192.168.1.60:64379.
Connection RDP-Tcp#four created

However, the RDP session was terminated later with none error:

The server has terminated primary RDP reference to the consumer.
The disconnect motive is zero

The server has terminated main RDP connection with the client: Microsoft-Windows-RemoteDesktopServices-RdpCoreTS

Check the standing of the Remote Desktop Services in your distant server and restart the service. You can do it remotely via the Services.msc console (use the “Connect to a different pc” choice), however it’s simpler to :

(Get-Service Time periodService -ComputerTitle ny-rds1).standing

The service is working, let’s restart it:

Get-Service Time periodService -ComputerTitle ny-rds1| Restart-Service –pressure –verbose

restart TermService powershell

But this didn’t resolve the issue.

Here are another methods to resolve it I’ve managed to seek out within the Web:

  • If you see the EventID 1057 within the TerminalServices-RemoteConnectionSupervisor occasion log (The RD Session Host Server has didn’t create a brand new self signed certificates for use for RD Session Host Server authentication on SSL connections), go to the folder C:ProgramDataMicrosoftCryptoRSA, rename the Machinekeys folder into Machinekeys_bak and restart the Time periodService;
  • I’ve additionally discovered that the RDP drawback “An inner error has occurred” occurred in Windows 10 1809 if the Configure H.264/AVC encoding for Remote Desktop connections coverage is enabled on the distant pc (it’s situated within the following GPO part: Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Remote Session Environment). To resolve the issue, you simply have to disable the UDP protocol for RDP by creating the fClientDisableUDP parameter with the worth 1 within the registry key HKLMSOFTWAREPoliciesMicrosoftWindows NTTerminal ServicesConsumer;
  • If the error seems instantly after clicking join (the connection try appear to be instantly rejected by distant desktop server), attempt to improve the utmost excellent RDP connections restrict. On Windows 10 the SKUs by default is ready to 100, however on Windows Server is 3000. Run the regedit.exe and create the DWORD registry parameter MaxOutstandingConnections with the worth 10000 within the reg key HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlTerminal Server. (The particular RDP counter takes under consideration not fairly right RDP logins, and upon reaching the required MaxOutstandingConnections worth, the RDP entry is blocked.)

Neither of the situations described above was relevant in my case. Occasionally, I discovered that different computer systems didn’t expertise any issues when connecting to this RDS server. It meant that there was a difficulty with my pc, not with the Remote Desktop server.

I within the registry key HKEY_CURRENT_USERSoftwareMicrosoftTerminal Server ConsumerServers and reset the RDP cache in C:Users%Username%AppDataLocalMicrosoftTerminal Server ClientCache (previous to doing it, shut all working mstsc.exe classes):

del "C:Users%Username%AppDataLocalMicrosoftTerminal Server Clientcache"

clean rdp cache cmd

Then I restarted my pc, and the RDP connection error disappeared!

Check Also

How to Enable and Configure MPIO on Windows Server 2016/2012R2?

In this text we’ll contemplate how to set up and configure MPIO on Windows Server …

Leave a Reply

Your email address will not be published. Required fields are marked *