I remotely connect using RDP from a Windows 8.1 computer to a Windows 10 Pro computer (version 2004, 19041.572) and am able to work just fine.
However, it occasionally freezes for a minute. This happens 1 to 5 times a day.
When looking in the Windows Event Viewer on the Windows 10 computer, one of the RDP logs (Microsoft-Windows-RemoteDesktopServices-RdpCoreTS/Operational) has errors recorded.
Here are some snippets from that log, with my comments:
First log entry when the freeze happened…
Lots of other Info entries, then:
It automatically started to reconnect, then:
Continued to connect, then:
Continued, but got two more of the above error.
Connection was reestablished and continued with no further log entries
What is wrong and how can this be fixed?
Those are network errors. You are unlikely to solve it by looking at Windows logs. You will need to troubleshoot the network connection all along the full path. If this includes the open internet you are going to have links that you can't see or fix.
I recommend using Wireshark on both ends and filter the traffic so you only see the RDP tunnel. This will give you an idea of where the connection is lost. Then you can check your networking hardware for events near the timestamps of the trouble seen in wireshark.
In response to a comment of mine, the poster has upgraded from Windows 8.1 to Windows 10. We will see if that has solved the problem.
Because of the dialog boxes, the idle time limit might be reached for the RDP session, causing its termination.
The settings for session time limits may be found via gpedit.msc
, at
Computer Configuration/Administrative Templates/Windows Components/Remote Desktop Services/Remote Desktop Session Host/Session Time Limits.
You may adjust here the four settings as desired. You are probabaly mostly interested in "Set time limit for active but idle Remote Desktop Services sessions" and "Set time limit for active Remote Desktop Services sessions", but check all of them.
So, the client computer was rebuilt with Windows 10. The problem has not been noticed in the day or two since.
Unfortunately, there's no way to know whether it was a Windows 8.1 issue, or a setting on the computer when it was running 8.1 that was impacting the connection.
User contributions licensed under CC BY-SA 3.0