{"id":27805,"date":"2022-11-26T07:37:11","date_gmt":"2022-11-26T06:37:11","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=27805"},"modified":"2022-11-28T12:11:16","modified_gmt":"2022-11-28T11:11:16","slug":"windows-remote-desktop-connection-issues-to-fqdn-since-october-2022","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2022\/11\/26\/windows-remote-desktop-connection-issues-to-fqdn-since-october-2022\/","title":{"rendered":"Windows Remote Desktop connection issues to FQDN since October 2022"},"content":{"rendered":"

\"Windows\"[German<\/a>]I have received reports of problems with remote desktop connections under Windows when they are made via FQDN (Fully Qualified Domain Name). The connections can then no longer be established. The problem has been occurring since October 2022 and a connection to the difficulties in connection with Remote Desktop problems seems to be given.<\/p>\n

<\/p>\n

Issues with Remote Desktop connections<\/h2>\n

\"\"According to my observations, there have been problems with Remote Desktop connections under various Windows versions for months. I had already reported about the problem in October 2022 in the blog post Windows 11 22H2: Microsoft investigates RDP issues<\/a>. Then, as of November 22, 2022, Microsoft has confirmed that there may be connection issues with Remote Desktop connections in Windows 11 version 22H2. Details can be found in the blog post Windows 11 22H2: Connection issues with remote desktop confirmed<\/a>.<\/p>\n

Issues with FQDN Remote Desktop connections<\/h2>\n

To my German blog post\u00a0Windows 11 22H2: Probleme mit Remote Desktop-Verbindungen best\u00e4tigt<\/a> Nicki got in touch and reported problems with Remote Desktop Connections on FQDN (Fully Qualified Domain Name). In this comment<\/a> the problem is described like this (I've translated the comment):<\/p>\n

Hi G\u00fcnter,<\/p>\n

since the October updates we have the problem that more and more users cannot connect via FQDN. The password is rejected. A connection via the IP address works fine.<\/p>\n

Have you heard about this? It goes here only in the PC-PC connections without gateway or broker.<\/p><\/blockquote>\n

I myself have not had any user reports and have not yet read anything in this regard, but blog reader Christian Braun confirms the problem in this comment<\/a> (translated):<\/p>\n

Same problem already had with 2 customers today. The connection was refused via FQDN. In the event log of the terminal server it was logged that the access data is not correct. IP address directly entered in the RDP connection solved the problem.<\/p><\/blockquote>\n

In the comment there is already a hint to a workaround: Instead of using a Fully Qualified Domain Name (FQDN) as connection target, Christian directly entered the IP address and the RDP connection works again.<\/p>\n

October 11, 2022 updates to blame?<\/h2>\n

Nicki then linked in a follow-up comment<\/a> to a post in the PatchDay MegaThread<\/a> where the October 2022 updates for Windows 10 (KB5018410) and Windows 11 (KB5018418) could be to blame for the connectivity issues. It says there:<\/p>\n

Security Update KB5018410 (Windows 10) and KB5018418 (Windows 11) break RDP SSO Delegated Credentials.<\/p>\n

We use the RDP desktop shortcut with single sign-on to allow logged-in users to simply log in to the remote server without entering the password again. It worked like a charm for years.<\/p>\n

I've been scratching my head all morning and found that some users are greeted with a \"The user name or password is incorrect. Try Again.\" as soon as the remote session window opens. Followed by weird logs in the event viewer.<\/p>\n

Apparently, it's been happening since last week, but not many users complained. When we investigated this issue today, we found several other users have the same issue, and they all had KB5018410 installed, and those that didn't have this issue didn't have the update installed. We uninstalled this update from the affected machines, and everything started working again!<\/p>\n

We do use RDS Farm(s) running WS 2022 with UPD (User Profile Disks).<\/p>\n

We tried the following, but the issue is not fixed, unless we remove the update.<\/p>\n