none
SessionBroker 1306, 1296, 802 errors

    Question

  • Situation: 
    Windows Server 2012 standard- with NO virtualization enabled. Machine is NOT a DC.  It is a single WS 2012 file server among 6 other WS 2008R2 machines.  All servers are members of a single domain.
    I have been attempting to load Remote Desktop Services- Many failures prior to finally getting RD Connection Broker, RD licensing and RD Session Host to load.  Ended up using a combination of PS and Server Manager.

    The problem:  No Remote Desktop access to the server--- NONE--- No Admin access - No User access. Admins DID have access prior to loading Connection Broker, Session Host and Licensing. Remote desktop connection is enabled & users have been specified. When you try to log on to the server a popup states the following:  Your computer can't connect to the remote computer because the Connection Broker couldn't validate the settings specified in your RDP file. Contact your network administrator for assistance."     The server event logs show:

    event 802:  RD connection Broker failed to process the connection request for user xxxx\yyy.  User's RDP file has invalid hint format.  Error:  the format of the connection hint in the RDP file is incorrect.  

    Event 1306 Micosoft-Windows-TerminalServices-SessionBroker-Client:  Remote Desktop Connection Broker Client Failed to redirect the user xxxx\yyy.  Error:  NULL

    Even 1296 Micosoft-Windows-TerminalServices-SessionBroker-Client: Remote Desktop Connection Broker Client failed while getting redirection packet from Connection Broker.  User:  xxxx\yyy Error:  Element not found.

    I would be very grateful for any help.  Since this is a new installation and has never worked, it is difficult to know where to start.  I do know that if I remove session broker and the other remote desktop services, normal admin remote desktop access is restored.

      
    Thursday, August 01, 2013 8:41 PM

Answers

  • Have found the "fix" 
    Added the connection broker to DC Group policy:  Local Computer Policy>Administrative Templates>Windows Components>Remote Desktop Services >Remote Desktop Session Host> RD Connection Broker >Configure RD Connection Broker server name  
    Added the new 2012 server and the other, existing 2008R2 connection broker server

    Did the same in GroupPolicy (GPedit.msc) on the new 2012 server (this server is both the connection broker and the session host).  Also cleared ALL other configuration in the new 2012 server Local Computer Group Policy>Administrative Templates >Windows Components>Remote Desktop Services >Remote Desktop Session Host> Left eveything but the connection broker server NOT CONFIGURED

    ran gpupdate from cmd on both servers

    NOW Everything is working... I feel pretty stupid- The 2008 Term Services/Remote Desktop was Soooo EASY.  Maybe this will help someone else. 

    Saturday, August 03, 2013 2:33 AM

All replies

  • Have found the "fix" 
    Added the connection broker to DC Group policy:  Local Computer Policy>Administrative Templates>Windows Components>Remote Desktop Services >Remote Desktop Session Host> RD Connection Broker >Configure RD Connection Broker server name  
    Added the new 2012 server and the other, existing 2008R2 connection broker server

    Did the same in GroupPolicy (GPedit.msc) on the new 2012 server (this server is both the connection broker and the session host).  Also cleared ALL other configuration in the new 2012 server Local Computer Group Policy>Administrative Templates >Windows Components>Remote Desktop Services >Remote Desktop Session Host> Left eveything but the connection broker server NOT CONFIGURED

    ran gpupdate from cmd on both servers

    NOW Everything is working... I feel pretty stupid- The 2008 Term Services/Remote Desktop was Soooo EASY.  Maybe this will help someone else. 

    Saturday, August 03, 2013 2:33 AM
  • Hi,

    Very glad to hear that your issue has been solved. And thanks for your good sharing.

    It will help the people who have the same issue.

    Thanks.

    Have a nice day.

    Regards.


    Vivian Wang
    TechNet Community Support

    Wednesday, August 07, 2013 6:09 AM