2012 R2 RDS servers broker

I’m having an issue with our new RDS servers we are testing.  We have two RDS 2012 R2 servers that both use a broker and a round robin name for load balancing.  
When I change a server to not allow new connections (say for maintenance purposes), any user connected to that server who logs off and then reconnects to the round robin DNS name,  gets directed  back to that same server and of course gets the message that “Remote logins are currently disabled”.  Sometimes if I reboot the Wyse box (T10 firmware 8.0_512) it will connect correctly, but there are some cases where it does not.

Has anyone seen this or have any ideas?  
Ryan YanezAsked:
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:
If you don't have your brokers configured for high availability, but still configure round robin DNS, this happens. Only one broker is aware f the maintenance status. You need to configure your brokers to be highly available. Or use only one broker.
Ryan YanezAuthor Commented:
We do only have one broker
Cliff GaliherCommented:
Then don't use round robin DNS. The broker handled load balancing in 2012. Round robin DNS actually breaks that.
Ryan YanezAuthor Commented:
Cliff so your saying just point the thin clients to the broker name and it will handle the load balancing?
Cliff GaliherCommented:
As long as the broker knows which collection you want, yes. Microsoft has *not* uodated the GUI for the "classic" RDC application to specify collectionnakes. But modern apps (android, iOS, win8) can query the RDWA web feeds, and clicking on a collection via RDWA itself, does include this info. So if your thin clients are very old, you'll need to plan for that. Using RDWA is usually the best option.  But going forward, it is best to consider RDC's GUI as legacy and shouldn't be opened by end users directly.

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
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.