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.


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

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:

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

  2. Kari L Tedrick says:

    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!

  3. Hasan Reza says:

    Excellent solution , God Bless ,

  4. 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).

  5. TS79 says:

    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.

  6. retsoksirhc says:

    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.

  7. Lee says:

    Thanks so much!

  8. emad says:

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

    thanks so much

  9. Jay Platt says:

    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?

  10. lherrera says:

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

  11. TKO says:

    Thanks for the help! This worked right away!

  12. Amos Kimiti says:

    Help me as well. Thanks.

  13. Luca says:

    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.


  14. Shlomi says:

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

  15. Chad Elliott says:

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

Leave a Reply to Shlomi

Sharing Buttons by Linksku