Connecting to Remote Desktop Session Host servers by the Broker

Problem

If you followed the article: Setting up an RDS farm under Windows 2012R2/2016, the client connection configuration is done using a Round Robin on the DNS.

What happens if the server returned by the DNS is offline?

The connection will not succeed and an error message is displayed.

Solution: Establish a connection through the Broker service

To solve the round robin DNS connection problem, the connection must be established directly on the broker.

If the Remote Desktop Connect client is configured with the broker’s address, it will not work, the client will try to log on directly to the broker server itself.

Echec ouverture de session

Open the Remote Desktop Connect client: in computer put the broker 1 server address and click Save As … 2.
Configuration client

Right click on the saved file 1 and edit the 2 (Notepadd ++ / notepad …).
Modifier fichier RDP

Make the changes below:

Search:

Replace with :

Add :

Result:
Notepad édition RDP

Save file.

Double-click on the file and click on Connect 1.
Connexion via RDC

Enter the credentials and validate the security messages on the certificates.

The connection is established, in the banner we see that the connection is established on the broker 1. Open a command window (cmd) and enter hostname 2, the name of the server that is displayed is a remote desktop session host.
connexion par le broker



Related Posts


RDS Farm: High Availability Service Broker Configuration

As a follow-up to the article: Deploy a RDS Windows 2012 R2 / 2016/2019 farm, we will see in this tutorial how to configure the high availability service broker. This configuration is optimized for cl

RDS: reduce the logon time

Introduction Before I explain how to optimize the opening of sessions on your RDS servers, I will explain the operation. By default, since Windows XP, the group policy processing mode is asynchronous,

Managing virtual machines in a Windows Server Hyper-V cluster

In this tutorial, we will see how to manage your virtual machines in a Hyper-V cluster using the Cluster Manager console. It is also possible to use the following tools to manage virtual machines with