Unable to RDP to Windows 11 via Remote Desktop Gateway

Anonymous
2024-07-15T11:24:59+00:00

Hi,

I'm encountering issue when trying to remote desktop to my office Windows 11 desktop via the Remote Desktop gateway after July's update (KB5040442) has been installed.

Windows 11 build (22631.3880)

Remote Desktop Gateway is running on Windows 2019 Server.

Windows Windows Client for IT Pros Remote and virtual desktops Remote desktop services and terminal services

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments No comments
{count} votes

11 answers

Sort by: Most helpful
  1. Anonymous
    2024-07-16T01:06:27+00:00

    Hello,

    Are you indicating that the problem arises specifically on your Windows 11 system after a recent update, whereas other computers are able to connect to their office desktops via remote access without issues?

    In that case, it may be unnecessary to examine the CAPs (Connection Authorization Policies) and RAPs (Resource Authorization Policies) configurations on the Remote Desktop Gateway server, as the problem does not seem to originate from the server side.

    However, supplying the precise error message you receive when attempting to establish an RDP connection to the office desktop would be significantly beneficial. Additionally, obtaining the connection logs found in the Event Viewer on the Server 2019 machine, under the path *Application and Services Logs\Microsoft\Windows\TerminalServices-Gateway\Operational*, could offer further insights into what is causing the failure.

    TS Gateway Server Connections | Microsoft Learn

    Additionally, it's worthwhile to go through the below general checklist to ensure nothing basic has been overlooked:

    1. Ensure that your Remote Desktop client software is up to date.
    2. Make sure that your network connection is stable and that there are no firewall rules blocking RDP traffic. The default RDP port is 3389; ensure this port is open on your network and on the server's firewall.
    3. Ensure that Remote Desktop is enabled on Windows 11and check if your user account has permission to connect remotely.

    Kind Regards,

    Karlie

    0 comments No comments
  2. Anonymous
    2024-07-16T01:44:59+00:00

    Hi Karlie,

    The target machine (Windows 11) patched with KB5040442. Remoting to a Windows 10 client (via the same Remote desktop gateway) will not have any issue.

    The description in the log,

    The user, on client computer "IP Address", did not connect to the following network resource: "Computer Name" because the remote computer does not  support secure device redirection. Try selecting another network resource or possibly lower RD Gateway security by modifying RD CAP to allow client connections to resources that do not enforce device redirection.

    0 comments No comments
  3. Anonymous
    2024-07-16T06:30:37+00:00

    Hello,

    Could there be any Group Policy settings that prevent updates on this Windows 11 machine? The error in the event log appears to be associated with the Group Policy located at 'Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Device and Resource Redirection.' Moreover, are there Resource Authorization Policies configured on the gateway that might be restricting the Windows 11 machine from connecting?

    Besides, have you verified the network connectivity between win11 and RDG?

    0 comments No comments
  4. Anonymous
    2024-07-16T10:56:09+00:00

    Hi,

    Just to clarify, there was no issue remoting in (via gateway) before till the recent security update, KB5040442 was installed.

    No changes in the GPO nor the network connectivity.

    0 comments No comments
  5. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more