Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Here's my network...

enter image description here

(Link to network diagram:

I have three RDSH servers - SVRDS1, SVRDS2 and SVRDS3. My Connection Broker is located on a separate box SVPDC1.


If a user is logged into SVRDS2 and this server goes down, then he can't log on (via RdWeb) again before SVRDS2 is online again. I don't get why he's not redirected to SVRDS1 or SVRDS3? Isn't that the brokers job?

I see this error on the Broker:

Source: TerminalServices-SessionBroker
Event ID:802
Error: RD Connection Broker failed to process the connection request for user mydomain\username. 
Error: Element not found. 

Is it my Connection broker, that is causing me problems or is it the gateway?

share|improve this question
@MojoDK, does the session broker reconnection your sessions locally, if you connect without the gateway at all? – Zoredache May 13 '14 at 22:22
@Zoredache I'm not excatly sure what you want me to do, but if I open RD on a client, type in the brokers name (SVPDC1) in the "Computer" and I don't use gateway, I get this error: "Connection denied because user account not authorized for remote login" – MojoDK May 14 '14 at 5:27
If I log a user onto SVRDS2 and remotely shuts down SVRDS2 then the user of course is kicked. If the user opens a RD connection (without gateway) and enter SVRDS1, then he gets this error: "Remote logins are currently disabled" – MojoDK May 14 '14 at 5:39
I think I said this on your first question about this but you really should separate the DC from any of this. It's not a good idea to have RD roles on the DC. Also, your Gateway and Broker should both be separate machines from the RDSH servers or other servers, which the Broker is (sort of, it's not on an RDSH server but it's on the DC which is not good), but the Gateway isn't; it shouldn't be combined with a server that already has the RDSH role. As far as the Broker though, have you set it up to tell it that the RDSH servers are part of a farm and used DNS round robin? Can you also... – Brad Bouchard May 14 '14 at 14:04
... elaborate more on the cloud to the firewall? I think it's just showing two NAT policies, but can you tell me exactly what's going on there? And, finally with your Gateway, are you having people connect from outside of your office using the Gateway? – Brad Bouchard May 14 '14 at 14:05

I had the same problem but a different solution.

In group policy – configure FQDN for the RD Connection Broker. (you will also need to enable ‘join rd connection broker)

my working config as below. Local Computer Policy/Computer Configuration/Administrative Templates/Windows Components/Remote Desktop Services/Remote Desktop Session Host/RD Connection Broker/

Join RD Connection Broker – enabled

Configure RD Connection Broker farm name – not configured

Use Ip Adress redirection – not configured

Configure RD Connection Broker server name – enabled (put you FQDN here of the RD Connection Server or servers).

Use RD Connection Broker load balancing – not configured. (I have only one server)

I hope this maybe can help someone. :)

share|improve this answer

You do not need to setup HA with round robin for your CB, but it is good practice to set it up just in case you want to add another CB into the mix and have HA.

You should setup NLB for your RDSH servers so the CB looks at NLB IP and NLB can see what server is up or down. each RDSH install NLB, create a VirtIP (used for all RDSH servers). This alone will allow the CB to see find an online server. Round robin for your RDSH farm will not check to see if a server is available, it will continue to pick the down server while shuffling through dns entries.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.