none
Problem with Remote Desktop Connection Broker.

    Question

  • Hi,

    I currently have multiple servers/environments with the exact same problem
    the users (sometimes) aren’t reconnected to their existing/disconnected sessions.

    This is the setup:
    - All 2008 R2 machines.
    - Token redirection.
    - 4 Terminal servers.
    - NLB for load balancing.
    - RD connection broker installed on the domain controller.
    - All terminal servers are in the same farm.
    - All terminal servers are member of the Session Broker Computers group (including the domain controller).

    On the domain controller I see the following error:

    Event ID: 802
    RD Connection Broker failed to process the connection request for user ----.
    Load Balancing failed OR Specified endpoint could not be found.
    HRESULT = 0x80070515.

    On the terminal servers I see two types of errors:

    Event ID: 1296
    Remote Desktop Connection Broker Client failed while getting redirection packet from Connection Broker.
    User :
    HRESULT =
    0x80070515

    Event ID: 1306:
    Remote Desktop Connection Broker Client failed to redirect the user ---.
    HRESULT =
    0x80070515

    The network connection between all servers seems fine when I ping them.
    Also all servers are virtual machines running on Hyper-V.

    Does anybody know how to resolve these errors?

    Regards,
    Luuk

    Friday, September 09, 2011 10:25 AM

All replies

  • I have exaxt the same issue here reported by SCOM07R2 for our ConnectionBroker,

     

    Ereignis-ID: 802 -- Beschreibung: Fehler des Remotedesktop-Verbindungsbrokers beim Verarbeiten der Verbindungsanforderung für Benutzer INTERN\Administrator.8
    HRESULT = 0xffffffff80070515.

    However, connections to the servers are fine.

     

    Regards

     

    Monday, September 12, 2011 8:15 AM
  • Same problem here. The only difference in setup as described by Luuk-B  is that we do not use NLB and RD connection broker server is a virtual server. So far we did not found any workaround except manually log off user from current session.

     

    Any help appreciated.

    Regards

    Bostjan

     

    Tuesday, November 15, 2011 12:51 PM
  • 1. Please try to limit single RDS session for TS user. 2. Install RDS broker to separate server 3. run NLB diagnose to check if any issue related to NLB 4. use IP address redirection instead of token redirection
    Thursday, November 17, 2011 5:26 AM
  • Somehow we missed the Gp setting: Computer Configuration / Administrative Templates / Windows Components / Remote Desktop Services / Remote Desktop Session Host / RD Connection Broker / Use RD Connection Broker load balancing . Changed from Disabled to Enabled and gpupdate / force on RD session hosts put the trouble away !

    Bostjan




    • Edited by berglez Thursday, November 17, 2011 1:23 PM
    • Proposed as answer by Jure Jereb Thursday, November 17, 2011 1:23 PM
    Thursday, November 17, 2011 1:21 PM