RD Gateway not forwarding when using Remote Desktop Client

CuringaRJ 1 Reputation point
2021-02-14T14:15:57.6+00:00

Hi,

I am testing RDS 2019 in my company.
I installed 4 servers, one for RDWeb and RD Gateway, one for Broker and two for RD Sessions
I dont know what is wrong, when i access https://portalname/rdweb i can log on using 443 port and access one of the RD Sessions,
but when i try to connect using Remote Desktop Connection Client, i put the portalname and i connect to the RD Gateway server, not the RD Session Server.
What is wrong in the configuration?

Thanks

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

3 answers

Sort by: Most helpful
  1. Jenny Yan-MSFT 9,336 Reputation points
    2021-02-15T05:34:20.733+00:00

    Hi,
    1.when i access https://portalname/rdweb i can log on using 443 port and access one of the RD Sessions
    Are input this url into the web browser? If not kindly confirm the detailed steps you've performed.
    Such url of Rdweb is used to for users to remote via browsers.

    2.For normal remote connection starting from mstsc or Remote Desktop Connection Client, the Gateway setting is different thing than the target server you would like to access.
    The computer here refers to the remote/target server that you would like access.
    67978-image.png

    To configure RDGateway, go to Advanced-->Settings:
    Checking bypass option will guide the remote session not go through gateway for internal network.
    67956-image.png


    Hope this helps and please help to accept as Answer if the response is useful.

    Thanks,
    Jenny

    0 comments No comments

  2. CuringaRJ 1 Reputation point
    2021-02-16T02:49:40.067+00:00

    Hi,

    I was filling the same url address of the RDS Gateway in the "Computer" option in the first picture and in the "Server name" in the second picture.

    After you warned me, i created a dns round robin record for the two Session Hosts Servers and i filled in the "Computer" field with that.

    I dont know if its wrong, but it works, now i can log on to both Session Hosts Servers. I think is not ok to fill one specified computer because it can be offline one day.

    68462-image01.png68427-image02.png

    0 comments No comments

  3. Jenny Yan-MSFT 9,336 Reputation points
    2021-02-16T03:17:44.707+00:00

    Hi,
    DNS round robin could be one of the methods used to access remote session host farm but since RDS 2012, the initial connection goes to RD Connection Broker instead of RD SH.
    If you'd like to get it working by connecting to RD Connection Broker (collection name) directly with mstsc.exe, you may configure default collection on RD Connection Broker via registry below:
    HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\ClusterSettings
    DefaultTsvUrl     REG_SZ     tsv://MS Terminal Services Plugin.1.<Collection Alias>

    In the meantime, add DNS Host record that collection name points to RD Connection Broker's IP address.

    Reference links:
    Connection Broker Redirection – RDS 2012
    https://ryanmangansitblog.com/2013/03/11/connection-broker-redirection-rds-2012/

    https://social.technet.microsoft.com/Forums/windowsserver/en-US/19237d81-47e6-4f4b-b1f7-3f43ea78e427/remote-desktop-to-rds-farm?forum=winserverTS
    Please note: Information posted in the given link is hosted by a third party. Microsoft does not guarantee the accuracy and effectiveness of information.


    Hope this helps and please help to accept as Answer if the response is useful.

    Thanks,
    Jenny

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.