I cannot get my users logged in when my new terminal servers are using RD Connection Broker Load Balancing.
So I'm trying to use the Windows Server 2008 R2 SP1 operating system to host our Remote Desktop Services (terminal services) Host service. I setup three physical servers with that OS, and enabled the Remote Desktop services host service. All the apps are loaded, and all three servers are in the same OU with a group policy applied to it. In the past, we only used NLB (network load balancing) for the 2003-based terminal servers, which worked okay. Now I'm looking forward to using the session-based load balancing, aka, RD Connection Broker Load Balancing. I enabled this feature, along with the other pertinent Connection Broker settings. I then added three static DNS entries for the cluster name, with each entry including the main IP address of each host server (ex. - rdcluster1: 192.168.4.61, 62, 63). One of our DC's has the RD Connection Broker service running on it.
When I go to login as a user, it looks like it will login, but the welcome circle spins for a while and then it just bounces back to the login screen. It seems that a few sessions would get through, but mostly it just sits there and bounces back. At first I thought it was a problem with the user's roaming profile, but the same problem occurs if I even try to login as local administrator.
After searching all over the Internet, and finding nothing, I decided to revert to Network Load Balancing. I turned the RD Connection Broker Load Balancing feature off, deleted the round-robin DNS entries, and then created one cluster entry (ex. - rdcluster1: 192.168.4.60). I then configured NLB on each of the host servers, and abracadabra, everything works fine.
Does anyone know why this would occur?
Join RD Connection Broker, Configure RD Connection Broker farm name, Use IP Address Redirection, and Configure RD Connection Broker server name are all enabled and setup correctly.
One other thing that may be worth mentioning: When I initially set all this up, I didn't know if I should have NLB enabled along with RD connection broker load balancing. There isn't a lot of information out there on the Internet about whether to use one or more load balancing mechanisms for your cluster. So I had originally set everything up with the NLB and RD Connection Broker Load Balancing running side-by-side. I created one dns entry for the cluster IP and that's it. When I discovered that there was a problem logging in, I went into NLB, deleted all hosts from the cluster, and then created the round-robin DNS entries for each host. After changing all of this, I still had the same problem with logging in users. I tried everything I knew but it's still a problem.
When NLB only is used, it logs in fine and balances relatively okay.