2012 RDS Deployment RoundRobin Issues?

Hi everyone,

I am setting up a new RDS deployment. Here is the setup

RDWA01 (Web, Gateway, Broker Services)

RDSH01 (Session Host & License)

RDSH02 (Session Host)

I have setup two dns pointers rdsfarm which one points to rdsh01 the other to rdsh02

I verified round robin is working for the dns pointers.

I setup a collection rdsfarm and published apps to it.

Now, when the first user logs in they can get in and run the remoteapp... (connects to rdsh01) no issues.

When the second OR if the first user's session is closed and attempts to reconnect, it connects them to rdsh01 but rdsh01 is redirecting traffic to rdsh02......... I get a "An authentication error has occured 0x607"... i assume this is the connection broker "load balancing the connections"

Also when this happens and you try to rdp to the server rdsh01 it throws an error

" The remote computer rdsh01 that you are trying to connect to is redirecting you to another remote computer named rdsh02. Remote desktop connection cannot verify that the computers belong to the same RD Session Host server farm. You muse use the farm name, not the computer name, when you connect to an rD Session host server farm"

In the gateway manager, i setup a local stored computers group with "RDS Farm" as the name and having the rdsh01, rdsh02, and rdfarm as the network resources.

Does anyone have any insight to what i am missing?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

Cliff GaliherCommented:
Don't use round-robin DNS with 2012. Let the connection broker do its job. It handles session distribution. RR DNS actually breaks things.

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
is_staffAuthor Commented:
Thanks Cliff for responding.

I originally did not have RR DNS and it was having the issue still. Is it something else on the Connection Broker that is not working as it should?

I will remove the 2 entries and see if that has any better luck.
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
Windows Server 2012

From novice to tech pro — start learning today.