What do I need to do to setup the network correctly in order to use RD Connection Broker Load Balancing

wootenj2001 used Ask the Experts™
Currently I have four physical terminal servers running Windows Server 2008 R2 SP1.  I'm still using NLB and just RD Connection Broker, not the RD Connection Broker Load Balancing.  I want to do away with NLB, because it doesn't work that great.  Ideally, I just want to use the RD Connection Broker Load Balancing.  I have a few questions about this scenario:

Can I team the two NICs on the server and create one teamed IP address? Will that work with RD Connection Broker, and IP Address Redirection? Is it beneficial to do so?

Do I need to put the physical NIC cables in a VLAN on our core switch? I know you have to with NLB running multicast, but not sure about this setup.  Is the RD Connection Broker Load Balancing chatty over the network? If I have to put the NIC cables in a VLAN, then what do you setup, if the servers will need to talk to mostly everything else.  

Let me know if you need more background information on our setup.

Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®

first of all teaming process is used in clustering / lan backup process...so it's not a related to this subject....

Overview of Remote Desktop Connection Broker (RD Connection Broker)
Applies To: Windows Server 2008 R2

Remote Desktop Connection Broker (RD Connection Broker), formerly Terminal Services Session Broker (TS Session Broker), is a role service that provides the following functionality:

Allows users to reconnect to their existing sessions in a load-balanced RD Session Host server farm. This prevents a user with a disconnected session from being connected to a different RD Session Host server in the farm and starting a new session.

Enables you to evenly distribute the session load among RD Session Host servers in a load-balanced RD Session Host server farm.

Provides users access to virtual desktops hosted on RD Virtualization Host servers and to RemoteApp programs hosted on RD Session Host servers through RemoteApp and Desktop Connection

see this following link for detailed explaination and setup


all the best


Thank you shaiksaj for the response.  You can team the NICS using HP teaming software on the HP servers.  It provides fault tolerance for the terminal server, and the virtual IP can be designated as the redirection IP.  I just don't know if it's beneficial, and if it's supported. I know it's done by some people, but not sure how prevalent it is.  On the last page of this article below, the guy is saying to perhaps leave it unteamed, but seperate the traffic.  

Example: http://www.citrixthings.com/whitepapers/HP%20Proliant%20Network%20Adapter%20Teaming.pdf

The links you provided are interesting, but I'm not quite ready to implement the web front-end. Plus, this is a physical environment, not virtual yet. I already have the RDSH environment setup, and the web/remote app front end will be next.  In fact, we'll probably utilize the "Desktop Connections" in Windows 7, so that I can push out the remote app icons to their desktop.  But first things first, I need to understand the networking architecture.  That is the problem I'm asking about now.
I ended up connecting all the RDSH servers in the core switch and it's been working fine.  I'm using RD Connection Broker Load Balancing and that is also working fine.  The only thing I did was disconnect the second NIC on the RDSH servers for now, and I'm just using the primary. I would like to team the NICs together and use that as the load balancing NIC, but I'm not sure that can be done.  


It turned out that I didn't need to make any major network changes.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial