Changed RDS Port - Now Can't Connect as Domain User

Colin Dexter 1 Reputation point
2023-10-16T16:37:08.01+00:00

Hello,

Server 2019 with RDS Session Host, RD Web Access, RD Gateway, RD Licensing and RD Connection Broker roles added. All worked very well but after changing the RDS Port from 3389 to another, I can no longer connect as a domain user. Can connect fine as local user using the new port. Haven't closed 3389 yet.

I'm guessing this has something to do with the port the gateway is using to access the session host, but just not sure where to address it. Thanks.

Remote Desktop
Remote Desktop
A Microsoft app that connects remotely to computers and to virtual apps and desktops.
4,303 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Colin Dexter 1 Reputation point
    2023-10-16T17:23:27.71+00:00

    Figured it out - To connect to Session Host, add the new port number to the end of the server/domain name. Ex: server.domain.net:12345.

    To use the RD Gateway, change the port number (to new RDS port) in the Resource Authorization Policies in RD Gateway Manager.

    0 comments No comments