RDP Mac Keeps Dropping Connection Server 2022

Question

I've searched the web, but am not finding an solution to my issue. My RDP session keeps losing its connection to Server 2022 instances. It is not happening with our 2019 servers. There is no error that shows up on the screen. It happens frequently--every 3-10 minutes. I can tell since we have MFA and I keep getting a DUO prompt on my phone. The session does not end, rather it is interrupted long enough to try and reconnect but with re-authenticating.

This is not a terminal services server and this is just using the two included RDP sessions allowed to manage a server.

No errors show in the log file on the server side. Here is a snippet of the error log file from RDP on the Mac side. I've tried googling the error codes with no success. The bolded line below is where the connection dropped.

E|2024-03-13 13:16:52.0220 -04:00|FileLoggingWindowController.swift:243 Logging to file started!!
E|2024-03-13 13:17:03.1050 -04:00|:0 {39cc8fa4-ce54-47bc-822b-a1066a8a0000} <0x700008bba000> "-legacy-"(ERR): No data of type 0xc09
/Users/runner/work/1/s/source/stack/libtermsrv/rdpplatform/uclient/ucore/rdpstack.cpp(1340): ParseUserData()
E|2024-03-13 13:17:03.2210 -04:00|:0 {39cc8fa4-ce54-47bc-822b-a1066a8a0000} <0x700008619000> "-legacy-"(ERR): (xRes = 3) SendDevicesPacket(false) failed
/Users/runner/work/1/s/source/stack/libtermsrv/rdp/xPlat/DriveRedirection/RdpXUClientDeviceRDManager.cpp(478): SetState()
E|2024-03-13 13:17:03.2220 -04:00|:0 {39cc8fa4-ce54-47bc-822b-a1066a8a0000} <0x700008513000> "-legacy-"(ERR): (xRes = 3) SendDevicesPacket(true) failed
/Users/runner/work/1/s/source/stack/libtermsrv/rdp/xPlat/DriveRedirection/RdpXUClientDeviceRDManager.cpp(483): SetState()
E|2024-03-13 13:26:04.5980 -04:00|:0 {39cc8fa4-ce54-47bc-822b-a1066a8a0000} <0x700008619000> RDP_WAN(ERR): Client connMonitor goto CMSTATE_DROPPED (total-missed=5)....try reconnect!
/Users/runner/work/1/s/source/stack/libtermsrv/rdp/LegacyXPlat/basecoreapi/implementation/ConnectionMonitor.cpp(429): RunMonitoringFSM()
E|2024-03-13 13:26:04.6530 -04:00|:0 {39cc8fa4-ce54-47bc-822b-a1066a8a0000} <0x700008bba000> "-legacy-"(ERR): Channel::StartWrite failed
/Users/runner/work/1/s/source/stack/libtermsrv/devices/common/HarmoniousVC/clientadapter/DynVC.cpp(1865): SendChannelClose()
E|2024-03-13 13:26:04.6540 -04:00|:0 {39cc8fa4-ce54-47bc-822b-a1066a8a0000} <0x700008bba000> "-legacy-"(ERR): Channel::StartWrite failed
/Users/runner/work/1/s/source/stack/libtermsrv/devices/common/HarmoniousVC/clientadapter/DynVC.cpp(1865): SendChannelClose()
E|2024-03-13 13:26:05.7140 -04:00|:0 {39cc8fa4-ce54-47bc-822b-a1066a8a0000} <0x700008bba000> "-legacy-"(ERR): No data of type 0xc09
/Users/runner/work/1/s/source/stack/libtermsrv/rdpplatform/uclient/ucore/rdpstack.cpp(1340): ParseUserData()
E|2024-03-13 13:26:05.7960 -04:00|:0 {39cc8fa4-ce54-47bc-822b-a1066a8a0000} <0x70000871f000> "-legacy-"(ERR): (xRes = 3) SendDevicesPacket(false) failed
/Users/runner/work/1/s/source/stack/libtermsrv/rdp/xPlat/DriveRedirection/RdpXUClientDeviceRDManager.cpp(478): SetState()
E|2024-03-13 13:26:05.7970 -04:00|:0 {39cc8fa4-ce54-47bc-822b-a1066a8a0000} <0x70000871f000> "-legacy-"(ERR): (xRes = 3) SendDevicesPacket(true) failed
/Users/runner/work/1/s/source/stack/libtermsrv/rdp/xPlat/DriveRedirection/RdpXUClientDeviceRDManager.cpp(483): SetState()
E|2024-03-13 13:26:39.7840 -04:00|:0 {39cc8fa4-ce54-47bc-822b-a1066a8a0000} <0x700008513000> RDP_WAN(ERR): Client connMonitor goto CMSTATE_DROPPED (total-missed=5)....try reconnect!
/Users/runner/work/1/s/source/stack/libtermsrv/rdp/LegacyXPlat/basecoreapi/implementation/ConnectionMonitor.cpp(429): RunMonitoringFSM()
E|2024-03-13 13:26:39.8650 -04:00|:0 {39cc8fa4-ce54-47bc-822b-a1066a8a0000} <0x700008bba000> "-legacy-"(ERR): Channel::StartWrite failed
/Users/runner/work/1/s/source/stack/libtermsrv/devices/common/HarmoniousVC/clientadapter/DynVC.cpp(1865): SendChannelClose()
E|2024-03-13 13:26:39.8650 -04:00|:0 {39cc8fa4-ce54-47bc-822b-a1066a8a0000} <0x700008bba000> "-legacy-"(ERR): Channel::StartWrite failed
/Users/runner/work/1/s/source/stack/libtermsrv/devices/common/HarmoniousVC/clientadapter/DynVC.cpp(1865): SendChannelClose()
E|2024-03-13 13:26:40.9350 -04:00|:0 {39cc8fa4-ce54-47bc-822b-a1066a8a0000} <0x700008bba000> "-legacy-"(ERR): No data of type 0xc09
/Users/runner/work/1/s/source/stack/libtermsrv/rdpplatform/uclient/ucore/rdpstack.cpp(1340): ParseUserData()
E|2024-03-13 13:26:40.9980 -04:00|:0 {39cc8fa4-ce54-47bc-822b-a1066a8a0000} <0x700008f4f000> "-legacy-"(ERR): (xRes = 3) SendDevicesPacket(false) failed
/Users/runner/work/1/s/source/stack/libtermsrv/rdp/xPlat/DriveRedirection/RdpXUClientDeviceRDManager.cpp(478): SetState()
E|2024-03-13 13:26:40.9980 -04:00|:0 {39cc8fa4-ce54-47bc-822b-a1066a8a0000} <0x700008513000> "-legacy-"(ERR): (xRes = 3) SendDevicesPacket(true) failed
/Users/runner/work/1/s/source/stack/libtermsrv/rdp/xPlat/DriveRedirection/RdpXUClientDeviceRDManager.cpp(483): SetState()
E|2024-03-13 13:27:09.9220 -04:00|FileLoggingWindowController.swift:194 Logging to file finished!!

Answer 1

Thank you to all who replied. After further research and a lot of wasted time and money, the issue turned out to be a bad network cable causing packet drops which then created the loss of connection.

Answer 2

Hi Random Guy 63,

I'm here to help with your problem.

Do you use the Microsoft Remote Desktop Client App for Mac?

If yes, could you see if using the latest version improves the situation?

Another possible cause could be a TCP/UDP problem.

Can you try to change the following setting to turn off UDP on your 2022 server:

1. Open the "Local Group Policy Editor" by running the "gpedit.msc" command in the command line, in PowerShell (or Win+X → Run) as an administrator.
2. Go to Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Client connection to a remote desktop" (Remote Desktop Connection Client).

3. Find the Turn Off UDP On Client option and set it to Enabled.
4. Go to "Computer Configuration" -> "Administrative Templates" -> "Windows Components" -> "Remote Desktop Services" -> "Remote Desktop Session Host" -> "Connections" ( Connections).

5. Find the Select RDP Transport Protocols option and set it to Enabled, and in the options select Use only TCP.

Best regards,

Yu

Answer 3

Hello,

Session disconnections often result from networking issues, such as packet drops. To determine whether networking is the cause of this issue, trying to RDP to the localhost. If the local RDP session remains stable without dropping, it indicates that the issue is not related to networking.

When performing RDP to the localhost, you will get an access denied if you specify the credentials of a user who already has an RDP session with the server.

Regards,

Karlie

Answer 4

i've been experiencing alot of rdp issues to Azure free tier ultimately the answer for me has been to use more than 1gb ram or go into advanced settings and turn it to best performance and enable the caching.
Also to turn down the graphics settings.

In older versions of Windows i've seen more packet issues with RDP especially when it comes to using VPN's effectively it's an overhead to your MTU size and one quick fix was to enable fragmentation and change the default MTU size from 1500 down to 1400 and it would resolve rdp and other protocols. As VPN introduce overhead when they encapsulate the datagrams into IPSec packet it takes abit of the datagram size up so if you have a combination of a 1500 byte packet with the do not fragment flag on with the IPSec you get a droped packet which introduces service degradation and service disruption. I've heard some people using jumbo frames typically used for iSCSI to their favour not sure how and if that works. Carrying out ping tests with a variety of MTU sizing can determine if thats the case.

Solved: Identifying IP MTU fragmentation issues - Cisco Community

RDP does take abit of an overhead on the end point. I think there is a drive from Microsoft to use it less so in favour of Powershell (Enter-PSSession,New-PSSession, invoke-command), Windows Admin Centre, RSAT tools (Windows active directory admin centre).

Answer 5

THANK YOU THANK YOU!! I had been plagued with this problem for years on our network, and as soon as I did this on the remote/target machine everything was fine and stable now. I cannot believe this was such a quick fix, but nobody knew it. Thank you!!