Forum Discussion
NimbostratusRD farm with F5 BIG IP, errors in event logs
Hello,
we have a RD farm (Windows Server 2008 R2 Enterprise Ed.) with three nodes, the load balancing goes over a F5 BIG-IP. It's our first RD farm with F5. I'm the windows administrator of the farm nodes, I know nothing about F5.
We used the White Paper about 2008 R2 and 2012 RD Farms for set up the configuration.
From the sight of the users all things work well.
But I see following entries in the event logs of the servers. My question is: is this a normal behavior (cause the load balancing over the session broker is deactivated) or indicates this a misconfiguration?
On the Session Broker:
02/01/2013 09:14:13
RD Connection Broker received connection request for user DOM\barbara.
Hints in the RDP file (TSV URL) = tsv://MS Terminal Services Plugin.1.winterm.xxx.de
Initial Application =
Call came from Redirector Server = SERVERNAME.dom.xxx.de
Redirector is configured as Farm member
02/01/2013 09:14:13
RD Connection Broker has successfully determined the end point for this connection request.
Endpoint name = winterm.xxx.de
Endpoint type = Farm
Resource plugin name = MS Terminal Services Plugin
02/01/2013 09:14:13 (ERROR)
RD Connection Broker failed to process the connection request for user DOM\barbara.
Load Balancing failed OR Specified endpoint could not be found.
HRESULT = 0x80070515.
02/01/2013 09:14:36
Session for user DOM\Barbara successfully added to RD Connection Broker's database.
Target Name = SERVERNAME.dom.xxx.de
Session ID = 55
Farm Name = winterm.xxx.de
On the farm node:
02/01/2013 09:14:14
Remote Desktop Connection Broker Client received request for redirection.
User : DOM\barbara
RDP Client Version : 3
02/01/2013 09:14:14 (ERROR)
Remote Desktop Connection Broker Client failed while getting redirection packet from Connection Broker.
User : DOM\barbara
HRESULT = 0x80070515
02/01/2013 09:14:14 (ERROR)
Remote Desktop Connection Broker Client failed to redirect the user DOM\barbara.
HRESULT = 0x80070515
Greetings Barbara
6 Replies
- Hi grue,
I have never seen that error before. This makes me wonder:
Load Balancing failed OR Specified endpoint could not be found.
Do you have Connection Broker load balancing enabled? It should be disabled in the RDCB configuration.
Also, if you open a support case with F5 , we can have a look at your BIG-IP configuration.
thanks
Mike 
grue_115031Sorry for the late answer.
The Connection broker Load balancing is disabled. This was my first guess too and I checked this before asked here.
Could it be, that there are fragments of an earlier configuration in the registry? If so where?
For the F5 i will ask our F5-administrator.
Greetings Barbara Joost
kendAltostratus
We are having this same problem. Did you ever figure out what was causing it and how to fix it?
- I just wanted to confirm that you are not load balancing Connection Broker traffic through the BIG-IP (that is only supported with Windows Server 2012).
Ken, are you seeing the same issue as Barbara? Are users having issues connecting, or are you just seeing errors in the event logs? - kend
Yes, we are
load balancing Connection Broker traffic through the BIG-IP and according to "Deploying the BIG-IP LTM with MicrosoftRemote Desktop Services (2008 R2 and 2012)" F5 deployment guide, that should be supported for Windows 2008. Also, users are not having connectivity issues, we are just seeing the errors in the event log. Per the deployment guide, load balancing Connection Broker through BIG-IP is only supported with Windows 2012:
"If you have configured high availability for RD Connection Broker (available in Windows
Server 2012 only), BIG-IP LTM load balances requests from the Session Host servers to the
Connection Broker service between all members of the RD Connection Broker farm." - page 2
"Remote Desktop Connection Broker configured in High Availability mode, if
deploying a virtual server to load balance Connection Broker traffic (Windows Server
2012 only)." - page 5
