After setting up Remote Desktop Quick Start, when some Windows users tried to RDP to the RD Server, they received an error stating that Can’t connect to the remote computer. After probing about the error in Event Viewer, they see Event ID 802: RD Connection Broker failed to process has been registered message. In this post, we will see how to resolve the issue.
RD Connection Broker failed to process the connect requirest for user <username>
Error: Cannot create another system semaphore.
Event ID: 802
Remote Desktop Connection
This computer can’t connect tot he remote computer.
Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator.
Fix Event ID 802: RD Connection Broker failed to process
If you get Event ID 802: RD Connection Broker failed to process and RDP to RD Server is not possible, first of all, reboot your system and then try. Sometimes, a glitch can trigger these issues, which can be easily resolved by rebooting the system.
In case, rebooting is to no avail, follow the solutions mentioned below.
- Check if there is a limit on how many concurrent users can log in
- Disable Firewall temporarily
- Configure Group Policy
- Remove the user permission and add it again
Let us talk about them in detail.
1] Check if there is a limit on how many concurrent users can log in
First, you must check if your admin sets a group policy on how many concurrent users can log in simultaneously. You can ask your administrator about it and if they are redundant sessions, they can kill them so that you can log in with ease.
2] Disable Firewall temporarily
Your firewall can stop you from connecting to the remote desktop as it can misidentify the packet request it receives as malicious. In that case, we need to disable the firewall and then connect. Make sure to turn on the Firewall once the connection is established.
3] Configure Group Policy
If you are an admin, or you have configured a communication tunnel, there is a need to configure a few policies using the Group Policy Editor. Policies are what govern the user and system settings.
In order to make the changes, you need to open the Group Policy Editor from the Start Menu. Now, navigate to the location mentioned below.
Local Computer Policy/Computer Configuration/Administrative Templates/Windows Components/Remote Desktop Services/Remote Desktop Session Host/RD Connection Broker
Next up, configure the following policies as instructed.
- Join RD Connection Broker – Enabled
- Configure RD Connection Broker farm name – Not configured
- Use IP Address redirection – Not configured
- Configure RD Connection Broker server name – Enabled (put your FQDN here of the RD Connection Server or servers).
- Use RD Connection Broker load balancing – Not configured.
This will do the job for you.
4] Remove the user permission and add it again
If nothing worked, as an admin, you can remove the permission from the user and then give it to him. This will allow Windows to register privileges granted to that user. Follow the steps mentioned below to do the same.
- Sign in to the Domain Controller.
- Now, in the Active Directory, look for that user.
- Next, go to the Properties of that user.
- Then navigate to the Remote Desktop Services Profile tab.
- Tick the box associated with Deny this user permission to log on to the Remote Desktop Session Host server.
- Click Apply.
- Now, untick the box you ticked earlier and click Apply > Ok.
Finally, check if the issue is resolved.
What is the Event ID for Failed RDP connection?
There are various Event IDs for failed RDP connections, such as Event ID 4625 and 802 (the one we talked about earlier). Mostly the issue is caused when there are way too many concurrent sessions running. Also, if the policies are not configured to allow seamless connectivity, one will face the issue.
How do I fix Remote Desktop Connection error?
If you are failing to connect to a remote desktop, disable your firewall temporarily and then try. Security programs are notorious for misidentifying harmless programs as threats and acting accordingly. If your issue is not resolved, check our guide to resolve Remote Desktop errors.