Remote Desktop Connection Broker Client failed to redirect the user 2012

Server 2012 RDS - Remote Desktop Connection Broker Client failed to redirect the user domain\username. Error: NULL

Archived Forums

>

Windows Server 2012 General

• Question

• 2

  Sign in to vote

  Seeing the error listed here.

  The Remote Desktop Connection Broker server could not enumerate the targets for the provider named NULL from the database.
  
  Pooled virtual desktop collection name: NULL
  Error: Error code: 0xFFFFFFFF.

  Broker and Hyper-V are on the same physical machine.

  Any ideas on where to start troubleshooting this?

  Used the happy wizard to create everything, and got no errors.
  I have created a small pool collection, and given rights to domain users. Everything "looks" good.
  
  • Edited by The_Ron Wednesday, September 5, 2012 4:57 PM Clarity

  Wednesday, September 5, 2012 2:47 PM

Answers

• 7

  Sign in to vote

  Solution:

  http://support.microsoft.com/kb/331951

  Adding the broker to "Windows Authorization Access Group"

  This is only needed if the Domain the system is connected to was setup with as Pre-Windows 2000 Compatible.

  • Marked as answer by The_Ron Friday, September 14, 2012 8:13 PM

  Friday, September 14, 2012 8:12 PM

All replies

• 0

  Sign in to vote

  Obvious issue appears to be the SessionBroker cannot access its own database. Anyone out there experienced this or know of a possible solution.

  I have removed all RD services and re-added them to the machine a couple times, but the result seems to be the same. Permissions issue obviously but I am at a loss. What is location of the database and what account is trying to access it?

  Thursday, September 6, 2012 1:54 PM

• 1

  Sign in to vote

  Ron,

  I have the same issue. Broker cannot logon to Windows Internal Database, but I haven't figured out where those credentials are. I do know that I have a group policy I think may be the culprit that relates to log on as a service settings. If possible you may try pausing your group policies or removing the server 2012 machine from the domain just as a test to see if this addresses the issue.

  Just guessing at this point though

  Thursday, September 6, 2012 3:56 PM

• 0

  Sign in to vote

  Ron,

  I have the same issue. Broker cannot logon to Windows Internal Database, but I haven't figured out where those credentials are. I do know that I have a group policy I think may be the culprit that relates to log on as a service settings. If possible you may try pausing your group policies or removing the server 2012 machine from the domain just as a test to see if this addresses the issue.

  Just guessing at this point though

  Download and install SQL Server Management Studio.

  Connect to local host with \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\queryusing domain admin credentials. If Credentials fail... then you're running the Windows Internal Database as the System account and not the Network Service.

  SSEE might have been replaced with SSIS... not 100% sure because I haven't setup an RDP Broker on mine yet.

  http://msdn.microsoft.com/en-us/sqlserver/cc511477.aspx

  Your databases should be stored in the C:\Windows\SYSMSI folder... in previous versions it looked similar to this.

  C:\Windows\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data - should be 2008 or 2012 I assume for Server 2012.

  Also, see if this post helps with any guidance. http://social.msdn.microsoft.com/Forums/en-US/sqltools/thread/d2735d0d-f593-40e5-bf7a-356704c3aaee

  Best Regards,

  ---

  Steve Kline
  Microsoft Certified IT Professional: Server Administrator
  Microsoft Certified Technology Specialist: Active Directory, Network Infrastructure, Application Platform, Windows 7
  Microsoft Certified Product Specialist & Network Product Specialist
  Red Hat Certified System Administrator
  Microsoft® Community Contributor Award 2011
  All opinions expressed on my own behalf and not that of my company.
  This posting is "as is" without warranties and confers no rights.

  
  
  • Edited by Steve Kline Thursday, September 6, 2012 4:14 PM

  Thursday, September 6, 2012 4:12 PM

• 0

  Sign in to vote

  The Broker is using an Internal Database location is "C:\Windows\rdcbDb".

  Thursday, September 6, 2012 6:29 PM

• 0

  Sign in to vote

  I blocked the parent GPOs and checked locally to be sure nothing was coming through. I removed the Roles and database folder; which it does not do after the role is removed. I then rebooted and reinstalled. Same results.

  Thinking it may be time to open a ticket on this.

  Thursday, September 6, 2012 6:32 PM

• 0

  Sign in to vote

  Hi,

  im also having the same problem, the connection broker says failed to redirect

  but whats weird is i can run and connect fine internaly in my domain from a domain pc

  but when i use a remote gateway outside my network, i get this error?

  any resolutions?

  
  
  • Edited by si458 Monday, September 10, 2012 8:22 PM

  Monday, September 10, 2012 8:22 PM

• 0

  Sign in to vote

  Are you using mstsc.exe or the web interface for internal or external?

  Monday, September 10, 2012 8:41 PM

• 0

  Sign in to vote

  Hi

  i have the same Problem internal and external , i use mstsc.

  always the same error :-(

  ---

  Jvo

  Tuesday, September 11, 2012 2:08 PM

• 0

  Sign in to vote

  Still working with MS on this, but the only thing I have confirmed with them is RDC 7 must be used. I'm not sure if that helps you, but I will report back when I get a solution.

  http://www.microsoft.com/en-us/download/details.aspx?id=29022

  Tuesday, September 11, 2012 2:21 PM

• 1

  Sign in to vote

  From MS (edited slightly to remove issues specific to my setup):

  You must use an RDC client that understands how to connect to the RDWeb feed, which can be accessed by logging on to RDWeb itself or through the “RemoteApp and Desktop Connections” control panel applet. All Windows clients know how to do this, and even some thin clients that are running WES7 (Windows Embedded).

  Even the Microsoft RDC client does not have a way to enter this through the RDC UI, which is why we suggest you subscribe to the feed. You can connect to a single RDSH server just fine, but unless it is based on at least RDC 6.1 you can’t run RemoteApps. You could also connect directly to a VM via Remote Desktop, but the user would have no way of knowing which VM in the pool they are supposed to connect to unless the admin tells them. There is nothing preventing you from setting up unmanaged collections, but you can’t do managed collections as with managed collections, only the Connection Broker knows which VMs can be connected to in the pool, there is no way for the user to know.

  Tuesday, September 11, 2012 7:41 PM

• 0

  Sign in to vote

  this would explain why i cant connect from my mac :) and also my ipad!

  i will give a try using windows

  Wednesday, September 12, 2012 8:39 AM

• 7

  Sign in to vote

  Solution:

  http://support.microsoft.com/kb/331951

  Adding the broker to "Windows Authorization Access Group"

  This is only needed if the Domain the system is connected to was setup with as Pre-Windows 2000 Compatible.

  • Marked as answer by The_Ron Friday, September 14, 2012 8:13 PM

  Friday, September 14, 2012 8:12 PM

• 0

  Sign in to vote

  Dear All,

  I got similar problem -- and I cannot open the broker DB file at C:\Windows\rdcbDb because some other app is using it

  Has anyone been able to resolve this issue?

  Thanks,

  Leon Li

  Monday, April 1, 2013 3:32 AM

• 1

  Sign in to vote

  OK I resolved this myself, just or share:

  Solution: install SQL server, connect to Windows internal database, delete the rds.target and rds.pool with pool id = NULL

  Monday, April 1, 2013 5:24 AM

• 0

  Sign in to vote

  I have same problem How do you delete fields in database? How can i open/attach database?

  Thursday, April 18, 2013 1:20 PM

• 0

  Sign in to vote

  Salam,

  After you install the MSSQL management studio use this string "\\.\pipe\MICROSOFT##WID\tsql\query" to connect to Windows Server 2012 internal database (WID), also note you will need to run it as administrator even though if you've installed the WID with you account.

  I hope this helps.

  ---

  For every action, there is a reaction!

  Sunday, April 28, 2013 6:37 PM

• 0

  Sign in to vote

  I have the same problem.
  

  (Making this long hand for those who come after)
  I have installed SQl Management Studio Express 2012 SP1
  http://www.microsoft.com/en-us/download/details.aspx?id=29062
  (You only need the one file "SQLManagementStudio_x64_ENU.exe")

  Ran this as Administrator
  And typed in the Server Name field
  \\.\pipe\MICROSOFT##WID\tsql\query
  Then hit connect.
  

  Expanded Databases (+sign)
  Expanded RDCms
  Expanded Tables

  Right Clicked on rds.target, select Edit top 200 rows
  Right Clicked and copied, then pasted this into a notepad file on the desktop (As a backup)

  Right Clicked and selected Delete to delete the row with the data in it (and PoolID was set to Null in this row)
  

  Did the same for rds.pool

  Manually addedRemote Desktop server into the MEMBER OF tab of “Windows Authorization Access Group” via Active Directory Users and Computers. As this domain was Windows 2003 Native when the RDS server was first installed.

  Rebooted server and same issue>
  Checked SQL again and rows had come back.
  

  Is that what you meant by "delete the rds.target and rds.pool with pool id = NULL"?
  

  Not a SQL guru, so any help appreciated.

  Tuesday, September 17, 2013 4:20 PM

• 0

  Sign in to vote

  First run

  Set-Item WSMan:\localhost\Shell\MaxMemoryPerShellMB 1000",
  
  then run

  netsh winhttp reset proxy

  Thursday, November 7, 2013 6:47 AM

• 2

  Sign in to vote

  Any FULL resolution to this? I'm stuck. Environment originally started with Windows Server 2000, migrated to Windows Server 2003 and now Domain is Windows Server 2008 R2.

  We're implementing our 1st Windows Server 2012 Standard but only for RD Services. In Server Manager, Remote Desktop Services shows "A Remote Desktop Services Deployment does not exist in the server pool"

  When restarting the RD Server, Server Manager attempts Broker Connection, but returns to Server Manager and displays "Remote Desktop Connection Broker Client failed to redirect the user domain\administrator. Error: NULL"

  It's as if RDS has not been installed; when in fact I've installed RD Connection Broker (with WID), RD Licensing and RD Session Host.

  I have followed the above quite thoroughly adding the new RD Server to the Windows Authorization Access Group, ran an Access Permissions VB script, and installed SQL Server 2012 Management Studio. I can open the database but fields in the 1st Row of Tables rds.target and rds.pool show NULL. I can clear but not delete them, save, etc., but they return.

  It appears there are many paths in the rabbit hole and some suggested solutions work but not for all.

  RESOLUTION FOR OUR SITUATION: In paying for a support call to Microsoft, their tech uninstalled ALL RDS Roles. The tech then ran RDS Quickstart, Session based deployment. We did have to Disable a Default Domain Policy (Computer Configuration, Policies, Windows Settings, Security Settings, Local Policies, User Rights Assignment): Logon As a Service - to get it to work.

  During my previous Role based installation, I did addMSSQL$MICROSOFT##WID to this policy setting and successfully installed RDS Roles, specifically Connection Broker (with WID).

  So it appears Role based installation doesn't work out of the box from Microsoft when installingRD Connection Broker (with WID), RD Licensing, RD Session Host and RD Web Access.

  • Proposed as answer by GodSmackDaQueen Tuesday, November 11, 2014 4:12 PM
  • Edited by GodSmackDaQueen Tuesday, November 11, 2014 4:26 PM Resolution

  Monday, November 3, 2014 6:22 PM

• 0

  Sign in to vote

  I got this error for certain users and found that the users had opened Remote Desktop Client and typed inn the name of the RDS Broker directly instead if using the web interface or the correct rdp-files that we provided. The broker then gets no information on what collection to use and throws an error when trying to connect the user to NULL.

  I never tried myself, but defining NULL as a collection in the DB might produce a default collection for anyone just typing in the broker FQDN in the client.

  K.

  Monday, May 11, 2015 12:34 PM

• 3

  Sign in to vote

  Hi,

  >The Remote Desktop Connection Broker server could not enumerate the targets for the provider named NULL from the database.

  this means 'there is no collections'. Open server manager - RD Services - Collections and create a new one (add your server to the collection). Now session broker have acollection and a potential targets (RDS servers) list and can select a server from this list and redirect a client.

  ---

  http://OpsMgr.ru/

  • Proposed as answer by Stefano Belluomini Monday, October 19, 2015 1:18 AM

  Thursday, July 2, 2015 8:12 AM

• 1

  Sign in to vote

  Spot on Alexy!

  We had a brand new 2012 R2 environment, not upgraded from 2000 or 2003 and had the same issue. After creating a Collection, this error went away.

  Cheers

  Stefano

  Monday, October 19, 2015 1:19 AM

• 0

  Sign in to vote

  Same here, It was working before, then just stopped. I checked the database and there was an entry with a NULL pool Id. After I added a collection it changed from null to 1 and RDP to the broker server worked again. I removed the collection and the line was deleted from the database and RDP still worked.

  • Proposed as answer by jn3825 Friday, January 5, 2018 12:57 AM
  • Unproposed as answer by jn3825 Friday, January 5, 2018 12:57 AM

  Thursday, January 21, 2016 10:48 PM

• 3

  Sign in to vote

  Just to add to this thread as it seems to be the best information available on the internet regarding this still common issue-- what fixed the could not log on to database issue for me was to add the network service account (nt authority\network service) as a logon to the internal database (and give is the sysadmin role). I connected to it using the above method of "\\.\pipe\MICROSOFT##WID\tsql\query".
  

  • Proposed as answer by John Babbitt Thursday, May 10, 2018 6:55 PM

  Sunday, December 4, 2016 4:42 PM

• 1

  Sign in to vote

  Better late than never... Very grateful for this post. Of all the solutions proposed in this thread Matt's solution worked for me. The WID/rdcms was not corrupted; All remote services were operational, but could not access to Server Manager/ Remote Desktop Services/ Collections/ "Collection Name. Also any PowerShell access to RDServer ended in error.

  Now all good, thanks to everyone

  Wednesday, June 14, 2017 12:14 AM

• 0

  Sign in to vote

  Just to add to this thread as it seems to be the best information available on the internet regarding this still common issue-- what fixed the could not log on to database issue for me was to add the network service account (nt authority\network service) as a logon to the internal database (and give is the sysadmin role). I connected to it using the above method of "\\.\pipe\MICROSOFT##WID\tsql\query".
  

  
  I second this as the answer. I'm using Server 2016 in a Domain Level of 2008R2. Just be aware that you need to Run As Administrator for MSSMS and use the above pipe for accessing the WID database. Once in, expand the Security then the Logins. In the Logins, add a new login as NETWORK SERVICE, without the NT AUTHORITY. It will automatically add NT AUTHORITY to it once you press enter. Otherwise, it rejects "NT AUTHORITY\NETWORK SERVICE". Not sure why but hopefully this saves frustrations for everyone else. After that, I restarted the RD Broker/Gateway/Web server and the login error no longer shows up as well as the NULL reference. It was NULL just because the server could not get the information out of WID due to inability to log into it.
  
  
  • Edited by John Babbitt Thursday, May 10, 2018 7:05 PM Explain better

  Thursday, May 10, 2018 7:02 PM

• 0

  Sign in to vote

  Just to follow up, I also had this issue and the above fixed it.

  I was also getting another error "A Remote Desktop Services deployment does not exist in the server pool", this partly fixed this error as well but I also had to remove a network path we had set in our PSModulesPath, as this was preventing remote management access to the other 2016 servers.

  Wednesday, July 25, 2018 10:35 AM

• 0

  Sign in to vote

  Thanks, after hours of surfing...... this is the solution.... a empty collection and works.
  

  1 Dc server and license server
  1 RD host + rd broker + No RD gateway + no RD VDI

  very minimal...... a lot of time wasted.
  
  I need to access direct on the desktop of rd host, but a rd broker is pbligated.

  Friday, August 10, 2018 3:14 PM

• 0

  Sign in to vote

  Seeing the error listed here.

  The Remote Desktop Connection Broker server could not enumerate the targets for the provider named NULL from the database.
  
  Pooled virtual desktop collection name: NULL
  Error: Error code: 0xFFFFFFFF.

  Broker and Hyper-V are on the same physical machine.

  Any ideas on where to start troubleshooting this?

  Used the happy wizard to create everything, and got no errors.
  I have created a small pool collection, and given rights to domain users. Everything "looks" good.
  

  Although none of the proposed solutions worked for us, this thread was the most useful and I just wanted to add what worked for us.

  We found that there were numerous "TermServLicensing" Service Connection Points within the AD environment that were associated with old RDSH broker servers or RDSH servers that were not supposed to be licensing servers.

  Deleting these Service Connection Points and reinstalling the RDS Licensing role on the RDSH Broker resolved the issue for us.

  During my research, I found this article to be useful:

  • https://dimitri.janczak.net/2015/08/21/find-the-rds-licensing-servers-in-your-domain/
  • https://social.technet.microsoft.com/Forums/windowsserver/en-US/7cd408e3-09cc-4c10-bd1d-34c878b5de9c/removing-old-license-servers-scp-issues?forum=winserverTS

  Wednesday, September 25, 2019 3:16 AM

• 0

  Sign in to vote

  We had the same problem, hours and hours....and then this solved the problem with the database...:

  https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/ee907343(v=ws.10)?redirectedfrom=MSDN

  Friday, October 18, 2019 8:30 AM

Remote Desktop Services failed to join the Connection Broker on server

1 tháng trước

Recently I ran into a problem with an existing Remote Desktop Services 2012 R2 at a client site. The error occurred intermittently and after a number of retries, client could establish connection normally making the issue not always reproducible. This blog summarises the process of identifying the symptoms, possible causes, and the resolution steps.

Some Background

The RDS farm consisted of two connection broker servers and two session hosts. The Remote Desktop Connection Broker is configured in HA mode using two DNS records pointing to two broker nodes for round robin. The session hosts are 2012 R2 based machines. The broker nodes also host the RD Web Access and RD gateway with one of the nodes assuming the RD Licensing role.

Troubleshooting

The end user encountered the following error when trying to connect:
Your computer cant connect to the remote computer because the Connection Broker couldnt validate the settings specified in your RDP file. Contact your network administrator for assistance.

After further digging, I found the error below (Event ID 802) on the second broker node:
RD Connection Broker failed to process the connection request for user .
Farm name specified in users RDP file (hints) could not be found.
Error: The farm specified for the connection is not present.

Additional errors encountered were:
Remote Desktop Connection Broker Client failed while getting redirection packet from Connection Broker.
User :
Error: Element not found.

Remote Desktop Connection Broker Client failed to redirect the user
Error: NULL

One aspect I discovered was that the same error didnt occur on the other broker server. This led me to investigate the RDS configuration: the RDCB was setup in HA mode with a SQL backend however it only has one node configured. We got somewhere. To isolate the issue, we had decided to operate the RDS on a one node configuration to confirm suspicion that whenever a user gets redirected to the broker thats not configured it would cause a redirection failure (RDCB uses Round Robin DNS for HA).

In the server manager console, the following tasks were done:

• Removed DNS RR record of the second broker node
• Removed the second gateway
• Removed the RD Web Access of the second node

Connecting to the remote desktop farm from internal network worked fine after we have made this change tested this multiple times and from different machines to confirm that its stable. However we received a different error when connecting from external network but this time the end users error was different:

Remote Desktop cant connect to the remote computer for one of these reasons:
1) Remote access to the server is not enabled
2) The remote computer is turned off
3) The remote computer is not available on the network
Make sure the remote computer is turned on and connected to the network, and that remote access is enabled.

The next port of call was to check RD gateway and we found that the second gateway was still part of the RD gateway farm. From Windows Server 2012, RDS is administered in the Server Manager console which included configuration for Session Collections, RD Web Access, Broker Deployment, and RD Licensing. One aspect that is not fully managed via the console is Remote Desktop Gateway. One key takeaway is after adding or removing RD gateway from the server manager console check if the RD gateway server has been removed from the RD gateway manager.

*Further investigation showed that the configuration had Bypass RD Gateway server for local addresses checked resulting in a different outcome when connectingfrom localnetworks as it bypasses the RD gateway. Unhecking this enforces all connections through the RD gateway.

Category:

Technology

Tags:

RDS, troubleshooting, Windows Server 2012

Previous Post: Why You Should Move Your IT to the Cloud

Next Post: Protect Your Identity in the Cloud With Multi-Factor Authentication

Video liên quan

12 Replies

· · ·

Habanero

OP

davidr4

This person is a verified professional.

Verify your account to enable IT peers to see that you are a professional.

Nov 8, 2016 at 19:46 UTC

Right click the one you downloaded and click edit. You can edit it with Notepad. Look at what is different compared to the one you make.

2

· · ·

Jalapeno

OP

adamstadnick

This person is a verified professional.

Verify your account to enable IT peers to see that you are a professional.

Nov 8, 2016 at 19:48 UTC

I haven't made one at all, I'm talking about connecting without a defined .rdp file - open mstsc, type in the connection broker's name, and connect.

0

· · ·

Habanero

OP

Best Answer

davidr4

This person is a verified professional.

Verify your account to enable IT peers to see that you are a professional.

Nov 8, 2016 at 19:50 UTC

You can save the connection you are making. Just expand it by clicking Show Options and click Save As. Or open the default which is hidden in your Documents folder. Something in the default must be different

1

· · ·

Mace

OP

Justin1250

This person is a verified professional.

Verify your account to enable IT peers to see that you are a professional.

Nov 8, 2016 at 19:51 UTC

Like David said, the RDP file will have an entry in there for the load balancer.

Without that, it will fail.

2

· · ·

Mace

OP

Justin1250

This person is a verified professional.

Verify your account to enable IT peers to see that you are a professional.

Nov 8, 2016 at 19:53 UTC

Something like this will be needed in the RDP file for the farm:

Text

full address:s:MYRDSFARM.domain.com workspace id:s:farm.domain.com use redirection server name:i:1 loadbalanceinfo:s:tsv://MS Terminal Services Plugin.1.SessionHostcollectionname

1

· · ·

Jalapeno

OP

adamstadnick

This person is a verified professional.

Verify your account to enable IT peers to see that you are a professional.

Nov 8, 2016 at 19:53 UTC

Oh, duh. Sorry.

I see the missing balancer line. Is that normal? I was not aware that this had to be in the .rdp, I thought in 2012R2 they made the connection broker smart enough to handle this on its own.

I swear I haven't seen this written anywhere, hopefully I just missed it.

0

· · ·

Datil

OP

britv8 Nov 9, 2016 at 08:24 UTC

IIRC you need to use the farm address, if you use the gui and point it to server 1, you should get and error saying to use the farm address. the only exception to this is using the /admin switch on mstsc which will connect you directly to server 1

0

· · ·

Sonora

OP

thierry3186 Nov 9, 2016 at 09:15 UTC

1st Post

Same problem here, and we're indeed using the broker address...

0

· · ·

Datil

OP

britv8 Nov 9, 2016 at 10:46 UTC

I use DNS round robining

IIC create two cnames for the farmname using the session host servernames.

The process for connection is that you use the farmname. DNS will return one of the dns entries in the round robin, you connect to that IP address and that session host will take your connection.

the session host will then talk to the connection broker as to where your session should be and either accept your connection and log you in, or pass you to the server the connection broker tells the first server to send you to ,. the second server than will accept your log in

you never connect directly to the connection broker, which may be why you are having the issue

0

· · ·

Jalapeno

OP

adamstadnick

This person is a verified professional.

Verify your account to enable IT peers to see that you are a professional.

Nov 9, 2016 at 14:24 UTC

I don't believe this is how it works for 2012 R2 any more, none of the documentation for 2012 R2 mentions DNS round robin or having to set up the farm name as a DNS entry unless you are using multiple brokers for HA (which I am not). Everything I have read says to connect directly to the broker.

And that does work, I guess I just didn't expect to be forced to use a .rdp file instead of the gui. It works, I just wanted to make sure nothing was wrong.

1

· · ·

Thai Pepper

OP

Brant Wells

This person is a verified professional.

Verify your account to enable IT peers to see that you are a professional.

Nov 9, 2016 at 19:56 UTC

You may also want to check the RD Gateway settings in the RDP file. If you don't specify that in mstsc, then you'll have similar issues.

0

· · ·

Poblano

OP

sindbad Jun 22, 2018 at 20:28 UTC

I got the same thing as OP.
How did you fix it?

I dont want them to go through rds webpage and download the rdp file.
I dont want to make rdp files for them.

When working through rds webpage. It’s working perfect

Through mstsc rdp it’s not redirecting.

I hope someone has a fix for this?!

0

This topic has been locked by an administrator and is no longer open for commenting.

To continue this discussion, please ask a new question.

Remote Desktop Connection Broker Client failed while getting redirection packet from Connection Broker. User : Error: Remote Desktop Connection Broker is not ready for RPC communication.

Posted on 11th October 2016 by

I was getting this in my event log and users could no longer connect to RDS when trialling it –

Event ID – 1296

Remote Desktop Connection Broker Client failed while getting redirection packet from Connection Broker.
User : DOMAIN\USER
Error: Remote Desktop Connection Broker is not ready for RPC communication.

and then

Event ID – 1306

Remote Desktop Connection Broker Client failed to redirect the user DOMAIN\USER.
Error: NULL

I found the Fix for me was –

If you edit the properties of your Session Collection, click on the Security on the left. There is a setting for Security Layer. By default it is Negotiate. Try toset it to RDP Security Layer

My users could then connect again, i made the change in group policy for all TS (RDS) servers

– Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Security

– Edit ‘Require use of specific security layer from rermote (RDP) connections to Security Layer-RDP

This entry was posted in Tech Post and tagged 1296, 1306, broker, connection, event id, rds, ts. Bookmark the permalink.

Cannot connect RemoteApp or Desktop Connection via the Connection Broker

When trying to connect to a RemoteApp or Desktop Connection via the Remote Desktop Web Access or RemoteApp and Desktop Connections on a Windows desktop you can start the remote application but receive the following error:

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.

—

There are two Windows 2012 R2 servers in the Remote Desktop deployment, one with the RD Licensing, RD Gateway, RD Web Access and RD Connection Broker roles and one with the RD Session Host role. Investigating the deployment and collection settings there are no misconfigured settings found.

When you create a manual RDP file and create a desktop connection via the RD Gateway to the Session Host there is no problem.

—

Examining the eventlogs on the RD Connection broker will result in the following errors:

Event log: Microsoft-Windows-TerminalServices-SessionBroker-Client/Operational
Event 1301 Verbose:
Remote Desktop Connection Broker Client received request for redirection.
User : Domain\username
RDP Client Version : 5

Event 1296 Error:
Remote Desktop Connection Broker Client failed while getting redirection packet from Connection Broker.
User : Domain\username
Error: Element not found.

Event 1306 Error:
Remote Desktop Connection Broker Client failed to redirect the user Domain\username.
Error: NULL

Event log: Microsoft-Windows-TerminalServices-SessionBroker/Admin
Event 802 Error:
RD Connection Broker failed to process the connection request for user Domain\username.
Error: Element not found.

—

Solution:

The solution to the problem was as easy as just deleting the Collection and creating a new Collection.

—

• Delicious

Posted in Blog by ronnypot at December 1st, 2015.

18 Responses to “Cannot connect RemoteApp or Desktop Connection via the Connection Broker”

1. Jo says:

   January 31, 2016 at 1:07 am

   Thanks, helped me out a lot! Had the exact same issue.

   Reply

2. Kari L Tedrick says:

   February 5, 2016 at 3:46 pm

   Many thanks for sharing this. I had doubts it could have been that simple but since I was at a loss figured it couldn’t hurt.
   It fixed me immediately.
   Kudos and 2 thumbs up!

   Reply

3. Hasan Reza says:

   July 15, 2016 at 10:54 pm

   Excellent solution , God Bless ,

   Reply

4. John Robillard says:

   September 20, 2016 at 1:58 pm

   I have been struggling with this for days now. I make a collection, the collection appears on the RD Web Access Work Resources next to the apps Calculator, Internet Explorer, Paint, and Word Pad. Clicking on the collection let’s me logon to the server desktop. But clicking on any of the apps leads to the same problem again ‘This computer won’t connect…’ . And the old Remote Desktop program under the start button doesn’t work anymore. Not to mention one of the ‘solutions’ I tried makes CTRL+Alt+Del non-functioning on the rds server (win 2012 r2).

   Reply

5. TS79 says:

   November 11, 2016 at 4:44 pm

   Also saw this after installing the broker on top of a working session host before creating a collection. Once the collection was created the issue resolved.

   Reply

6. retsoksirhc says:

   February 14, 2017 at 4:30 pm

   Had a similar (same?) issue. Getting the 802 error in the terminal services gateway log, and users receiving “the remote desktop gateway server is temporarily unavailable”.

   I read somewhere before that changing a single published app regenerated all the configs and rdp files, and I had published calc.exe as a test for something a few weeks ago. I just unpublished it, and everything else regenerated and I was good to go. No need to recreate the whole collection.

   Reply

   • ronnypot says:

     February 15, 2017 at 8:34 am

     nice thanks for this!

     Reply

7. Lee says:

   February 16, 2017 at 3:39 pm

   Thanks so much!

   Reply

8. emad says:

   February 18, 2017 at 3:23 pm

   please can anyone help for deleting and creating of new collection..where to find these.

   thanks so much

   Reply

9. Jay Platt says:

   June 1, 2017 at 12:10 am

   Hey Guys,

   I am having the exact same problem, however we are running a production environment with 100+ clients. Is there an alternative fix that does not require deleting a collection & re-adding?

   Reply

   • Tor says:

     September 19, 2018 at 6:19 am

     Hi Jay,

     Did you ever find a way to do this without removing and adding collection?

     Reply

   • Harry says:

     December 15, 2019 at 5:23 pm

     you can connect with VPN. then this issue will be not come. if you have any other solution please suggest me.

     Reply

10. lherrera says:

    October 6, 2017 at 5:16 am

    muchas gracias, tanks a lot, after deleting the collection the issue has fixed, regards.

    Reply

11. TKO says:

    November 20, 2017 at 3:42 pm

    Thanks for the help! This worked right away!

    Reply

12. Amos Kimiti says:

    August 7, 2018 at 8:18 am

    Help me as well. Thanks.

    Reply

13. Luca says:

    May 23, 2019 at 10:58 am

    We had this problem. The solution has been giving proper READ permission to the NETWORK SERVICE account to the certificate used by the RD Gateway.
    on the RD Gateway server: mmc – add certificate snapin – personal certificates – right click on certificate – advanced – manage private keys – security
    Check if NETWORK SERVICE account has READ permission.

    Bye
    Luca

    Reply

14. Shlomi says:

    October 4, 2019 at 2:08 pm

    we are experience same problem, can any one say what was the final solution ?

    Reply

15. Chad Elliott says:

    October 9, 2020 at 1:49 am

    Thank you for this!! It helped clear things up when we came across this issue this morning.

    Reply

Click here to cancel reply.

Leave a Reply

Name (required)

Email (will not be published) (required)

Website