RemoteApps using TCP/3389

Anonymous
2024-02-13T21:17:27+00:00

I have an all-in-one RDS (Remote Desktop Services) server running 2019 publishing a handful of RemoteApps. I'm working a project to put it behind a firewall. I have noticed that when a client connects to a RemoteApp, netstat reports it's connecting on 3389 as opposed to 443. Can that be changed? Me end goal is to have RemoteApps separate from RDP to the server. The reason for that is to have the firewall apply more restrictions to Remote Desktop than RemoteApps. Ideally, RDS could be configured to use 443 only. However, if it does require a second port, can it be a different port than the native RDP server?

Windows for business | Windows Server | User experience | 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

1 answer

Sort by: Most helpful
  1. Anonymous
    2024-02-15T18:46:09+00:00

    Hello, I will support you as a support community member.

    You can use the 443 port if you configure the RDGateway server in front of the RDP Server in your environment.

    This would allow you to have RemoteApps separate from direct RDP connections and utilize port 443 for greater security.

    Here are references on how to set up RDGateway.

    https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/remote-desktop-gateway-role https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-rdweb-gateway-ha

    If you have another question, please let me know.

    Best regards,

    Yu

    0 comments No comments