RDP connection Round Robin functionality not working.

I have a 2016 RDS system comprised of 4 servers. "Server1" = Licensing/Connection Broker/WebAccess; "Server2" = Profile disk host for .VHDX files. "Server3" = Session Host; "Server4" = Session Host.  There is one Collection called "Test" which both Session Host servers (Server3 and Server4) are members. There is no Gateway server because this is an internal system only with no public access. NOTE: I have not created any certificates as I did not think them needed due to public access not being allowed.

Issue: Not always, but sometimes when a client tries to RDP into one of the Session Hosts, the attached error occurs. I have read lots of conflicting information regarding the "Farm" that is referenced in the error. I have read that there is no need to add DNS entries for Round Robin functionality between these Sessions Hosts with 2016 RDS systems, and I cannot find any Farm name to direct my clients to.

My next step was going to be to add RD Gateway functionality to Server1 to see if I could create a Farm and then actually get a Farm name and, subsequently, add the DNS entries. I'm going to wait on responses before doing so.

If anyone can help here, I would really appreciate it.

Drew McCurdy
Drew McCurdyAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

David Johnson, CD, MVPOwnerCommented:
no attachment.. one usually rdp's into the connection broker and not the session host. The connection broker then decides which session host.
Cliff GaliherCommented:
There is no attachment so we don't know the error.

Dont try to create a farm name and round Robin DNS records. That *will* break things. The purpose of the connection broker is to redirect connections. Using round Robin DNS and a farm name can cause the connection broker to be bypassed and since it'd be unaware of the connection, it'd fail to reconnect disconnected sessions or balance loads in any meaningful way.

Since Server 2012, the RDCB is the orchestrator for all of that. There is no need to do the 2008 era "farm" configuration.
Drew McCurdyAuthor Commented:
I updated the post with the error.

David, you wrote "one usually rdp's into the connection broker and not the session host". That's the first time I've read that and brings me to the question of how would that work if the there are, say 5 collections (each collection using different session hosts) that the Connection Broker knows about. In other words, if I have users rdp using server name of the Broker, how does the Broker know what collection to route the user to?

Cliff what you wrote is exactly how I understood it to work, however, the error indicates otherwise. There are no server errors to guide me into a solution, so I'm at a loss.
The 7 Worst Nightmares of a Sysadmin

Fear not! To defend your business’ IT systems we’re going to shine a light on the seven most sinister terrors that haunt sysadmins. That way you can be sure there’s nothing in your stack waiting to go bump in the night.

Cliff GaliherCommented:
There is still no attached error.
Quick question: how are users connecting to the RDS envirinment?  Are you having them open mstsc and manually filling out info?!? If so, that is wrong.
David Johnson, CD, MVPOwnerCommented:
you need to amplify your setup i.e.
server 1/2/3 - collection 1
server 4/5/6/7 - collection 2
server 8 - collection 3

so you need 2 connection brokers  
RCCB #1  uses servers 1/2/3
RCCB #2  uses servers 4/5/6
direct connect to server 8 OR add another connection broker that connects to server 8 option to add additional servers for collection #3

Do you seperate your collections by AD Groups? you can restrict access to collections by AD user group and only use 1 connection broker
Drew McCurdyAuthor Commented:
Sorry, Dave, I confused things when I brought up "5 collections". That was a hypothetical. I only have one collection with two Session Hosts dedicated to it. As for the error, I've tried to upload a picture twice and edit the original post with the error as well. Those attempts didn't work, so I'm just going to put at the bottom of this reply. Btw, I've found some information relating to the error in the following link, but it applies to 2012. What do you think?


Error: "Remote Desktop Connection cannot connect to the remote computer.
The remote computer that you are trying to connect to is redirecting you to another remote computer. Remote Desktop Connection cannot verify that the computers belong to the same RD session host server farm. You must use the farm name, not the computer name, when you connect to an RD session host server farm."
Cliff GaliherCommented:
So I will repeat:

Quick question: how are users connecting to the RDS envirinment?  Are you having them open mstsc and manually filling out info?!? If so, that is wrong.
Drew McCurdyAuthor Commented:
This system isn't in production, yet;  but, yes, right now as I'm testing, I am manually filling in info.
Cliff GaliherCommented:
It won't work. And the reason why stems back to a question you asked earlier:

"if I have users rdp using server name of the Broker, how does the Broker know what collection to route the user to?"

When yoj are using mstsc then the broker can't know. Even if you only have one collection. Mstsc has no GUI to specify the collection name.

*BUT* if you use the RDP files that are created for RDWA (either by using the website or by subscribing to the XML feed) then that has the collection name embedded it it.  They can be saved and opened in notepad to verify this.  That collection property is sent to the connection broker when you connect and the broker then k ow where to redirect you.

Microsoft basically made RDWA a mandatory component and the intended way to distribute RDS resources to end users. They never enhanced the mstsc GUI to handle the new architecture. You'll never get successful tests using it alone.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Drew McCurdyAuthor Commented:
David and Cliff, thanks for all your help. Hopefully, I can find some straightforward guidelines on how to use the RDP files you stated were necessary.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Remote Access

From novice to tech pro — start learning today.