Error Event 1306
Contents |
Microsoft Tech Companion App Microsoft Technical Communities Microsoft Virtual Academy Script Center Server and Tools Blogs TechNet Blogs TechNet Flash Newsletter TechNet Gallery TechNet Library TechNet Magazine TechNet Subscriptions remote desktop connection broker client failed to redirect the user error null TechNet Video TechNet Wiki Windows Sysinternals Virtual Labs Solutions Networking Cloud and event id 1296 Datacenter Security Virtualization Downloads Updates Service Packs Security Bulletins Windows Update Trials Windows Server 2012 R2 System Center 2012 remote desktop connection broker is not ready for rpc communication R2 Microsoft SQL Server 2014 SP1 Windows 8.1 Enterprise See all trials » Related Sites Microsoft Download Center TechNet Evaluation Center Drivers Windows Sysinternals TechNet Gallery Training Training Expert-led, virtual classes
Remote Desktop Services Failed To Join The Connection Broker On Server 2012 R2
Training Catalog Class Locator Microsoft Virtual Academy Free Windows Server 2012 courses Free Windows 8 courses SQL Server training Microsoft Official Courses On-Demand Certifications Certification overview MCSA: Windows 10 Windows Server Certification (MCSE) Private Cloud Certification (MCSE) SQL Server Certification (MCSE) Other resources TechNet Events Second shot for certification Born To Learn blog Find technical communities in your area Support Support options For adding the broker to "windows authorization access group" business For developers For IT professionals For technical support Support offerings More support Microsoft Premier Online TechNet Forums MSDN Forums Security Bulletins & Advisories Not an IT pro? Microsoft Customer Support Microsoft Community Forums United States (English) Sign in Home Windows Server 2012 R2 Windows Server 2008 R2 Library Forums We’re sorry. The content you requested has been removed. You’ll be auto redirected in 1 second. Remote Desktop Services Remote Desktop Session Host RD Connection Broker Communication RD Connection Broker Communication Event ID 1306 Event ID 1306 Event ID 1306 Event ID 1013 Event ID 1014 Event ID 1015 Event ID 1280 Event ID 1281 Event ID 1282 Event ID 1283 Event ID 1284 Event ID 1296 Event ID 1297 Event ID 1298 Event ID 1299 Event ID 1300 Event ID 1301 Event ID 1302 Event ID 1303 Event ID 1304 Event ID 1306 Event ID 1307 Event ID 1308 TOC Collapse the table of content Expand the table of content This documentation is archived and is not being maintained. This documentation is archived and is not being maintained. Event ID 1306 — RD Conn
is as stated: A non-administrator domain user is trying to log into one of the pooled event id 802 virtual desktops (running windows 7). Said user gets prompted from windows
Event Id 1306
security to login with their domain credentials; but instead of being directed to the Virtual Desktop,
Event Id 802 Element Not Found
this user is redirected to a second logon session for the actual server. IE: User\Administrator has a logged in session where he/she see's server manager, with Hyper https://technet.microsoft.com/en-us/library/ee890979(v=ws.10).aspx V etc all running. [Please note: When User\Administrator attempts to log into the remote desktop services that account is redirected to one of the pooled VMs. As well both the Administrator and non-admin accounts are on the access list for the pooled vms in the settings of the golden template, and in the http://www.networksteve.com/forum/topic.php/Event_ID_1301_-%3E1296_-%3E_1306:_Connection_Broker_Client_Failed_to/?TopicId=73432&Posts=3 usergroup of the collection] When User\Non-Administrator has logged in they just see another copy of Server 2012 running with the same "Data Retrieval Failure" error on all the server roles. While checking the event viewer the series of verbose/error codes were as such. Verbose 1301: Connection Broker Received the non-admin's request for redirection Error 1296: Connection Broker Client failed while getting redirection packet from Connection Broker Error 1306: Connection Broker Client Failed to redirect the user User\non-admin. Now I went though the troubleshooting illustrated here:https://technet.microsoft.com/en-us/library/ee890979(WS.10).aspx It's not a network issue, since I can ping from the server straight through to my router, user desktop, firewall, primary DNS, Alternate DNS, and all the little NIC's inbetween. Has anyone else encountered this issue? Edited by Alexander Tranauskas Monday, June 22, 2015 7:16 PM June 22nd, 2015 6:39pm Hi Alexander, Said user gets prompted from windows security to login with their domain credentials; but instead of being directed to the Virtual Desktop,
rcmtech On trying to connect to a Windows Server 2012 Remote Desktop Session Host published desktop I got the following error https://rcmtech.wordpress.com/2013/08/22/remote-desktop-connection-cant-connect/ from my Remote Desktop Client: Remote Desktop Connection This computer can't connect to the remote computer. Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator. [OK] [Help] Which was annoying, I'd just built the RDSH server and via Server Manager - Remote Desktop Services event id everything looked ok for it: the TermService was running, Remote Desktop Services and Remote Desktop Session Host roles were present. Drilling down into Collections and looking in the collection containing the published desktop and this particular RDSH server, Allow New Connections was set to True. Going back to Server Manager, Remote Desktop Services, remote desktop connection Servers, I selected the connection broker server. In the Events section there were three events listed at the time when my client connection failed: Log Name: Microsoft-Windows-TerminalServices-SessionBroker/Admin Source: Microsoft-Windows-TerminalServices-SessionBroker Date: 22/08/2013 11:26:16 Event ID: 802 Task Category: RD Connection Broker processes connection request Level: Error Keywords: User: NETWORK SERVICE Computer: RDCB2012-01.rcmtech.co.uk Description: RD Connection Broker failed to process the connection request for user RCMTECH\user. Error: Element not found. Log Name: Microsoft-Windows-TerminalServices-SessionBroker-Client/Operational Source: Microsoft-Windows-TerminalServices-SessionBroker-Client Date: 22/08/2013 11:26:16 Event ID: 1296 Task Category: RD Connection Broker Client processes request from a user Level: Error Keywords: User: NETWORK SERVICE Computer: RDCB2012-01.rcmtech.co.uk Description: Remote Desktop Connection Broker Client failed while getting redirection packet from Connection Broker. User : RCMTECH\user Error: Element not found. Log Name: Microsoft-Windows-TerminalServices-SessionBroker-Client/Operational Source: Microsoft-Windows-TerminalServices-SessionBroker-Client Date: 22/08/2013 11:26:16 Event ID: 1306 Task Category: RD Connection Broker Client processes request from a user Level: Error Keywords: User: NETWORK SERVICE Computer: RDCB2012-01.rcmtech.co.uk Description: Remote Desktop Connection Broker Client failed to redire