Hi,
I’m having a problem with my Remote Desktop farm. I have 3 Windows Server 2008 R2 servers.
SH1 = Session Host 1 (Farm Member)
SH2 = Session Host 2 (Farm Member)
SH3 = Session Host in Dedicated Redirection Mode with Connection Broker
I am not using a Gateway server and I have no need for Web Access.
This system is only used for remote desktop connections, no remoteapps and no virtual desktops.
A connection comes in through a Juniper SSL and is directed through Network Load Balancing to SH1 or SH2.
Both SH1 and SH2 are configured …
- To connect to the Connection Broker using FQDN
- To join the farm specified with identical FQDNs
- To use the local IP address (not the NLB) for reconnections
The problem is that when the Remote Desktop Connection Broker service is started on SH3, connections are rejected on one of the servers for each user.
Eg.
User 1 can logon to SH1 but fails on SH2
User 2 can logon to SH2 but fails on SH1
So only 50% of connections are successful. The error message is “The client could not connect to the remote computer. Remote connections might not be enabled or the computer might be too busy to accept new connections. It is also possible that network problems are preventing your connection. Please try your connection again later. If the problem continues to occur, contact your administrator.”
However, if I turn off the Remote Desktop Connection Broker service on SH3, then any user can log on to either SH1 or SH2, consistently. The problem with this is that any sessions that are disconnected are not automatically reconnected when the user logs back on.
So the question is, why does the Remote Desktop Connection Broker service stop users from connecting to one or other of the servers?