How to: Remote Desktop Connection Broker is Not Ready for RPC Communication
What if you run into the error “Remote Desktop Connection Broker is not ready for RPC communication? Here in this post, we’ll provide you with solutions.
By Ellie / Updated on December 13, 2024
RDC Broker is not ready for RPC communication
"Good morning, everyone. I met with an annoying problem. I ran into the error "Remote Desktop Connection is not ready for RPC communication" while using Remote Desktop to access a server on my Windows server 2016, and I fail to connect to that server again. Can anybody give me the advice to fix the issue?”
- Question from Jessica
Before the operation, let’s get to know something about RPC( Remote Procedure Call). Remote Procedure Call is a distributed system construction technique. It essentially lets software on one system call a subroutine on another machine without being aware of the fact that it is remote. When it comes to the error in this post, most of the time, it may occur when the RDP session requires secure RPC communication but it didn’t correctly set.
How do I fix Remote Desktop Connection Broker is not ready for RPC Communication?
As we mentioned above, the Remote Desktop may inquire about secure RPC communication. So, we can fix the issue “Remote Desktop Connection Broker is not ready for RPC communication” on Windows server 2016, 2012 R2...by changing the RDP security layer in Group Policy.
Step 1. Press Win + R and then enter “gpedit.msc”, hit the “OK” button to open Group Policy.
Step 2. Navigation:
Computer Configuration\ Administrative Templates\ Windows Components\ Remote Desktop Services\ Remote Desktop Session Host\ Security\ Require use of specific security layer for remote (RDP) connections
Step 3. Double-click on the policy “Require use of specific security layer...”, and then choose tick “Enabled”. Beside the Security Layer, choose “RDP”. Click on “Apply” and then click on “OK”.
Step 4. Now you can connect to the remote server again to see whether the issue disappears.
Get a free Remote Desktop alternative-- AnyViewer
Is the solution above already fixed your issue “Remote Desktop Connection Broker is not ready for RPC communication”? If the issue has been fixed, that will be nice. But if the issue persists and has an effect on your user experience, we recommend using a professional and secure remote access software-- AnyViewer.
- ★Tips:
- ✎ With AnyViewer, you can enjoy the fast connection speed, low latency and high responsiveness.
- ✎ Supported by a strong team, AnyViewer can help you realize remote access with one click if you log into the same AnyViewer account.
- ✎ And with the feature like privacy mode in an advanced plan, the screen of the remote PC will be blackened and the keyboard & mouse will be disabled, which definitely safeguards the security of your data. Follow me to know how to operate.
- ✎ It’s workable for multiple Windows versions, including Windows 10 Home Edition.
Step 1. Download and install AnyViewer. Go to Log in, and then click Sign up.
Step 2. Fill in the signup information. Then you can see you successfully logged in to AnyViewer. Your device will automatically be assigned to the account you've logged in to.
Step 4. Log in to the same AnyViewer account on the two devices, then you can achieve a direct connection by clicking One-click control.
✍ Note: If you need to remotely assist your friends or family members on IT-related issues, you can also try “ Send a control request” in the "Connect" tab to achieve the goal.
Conclusion
From the post, we know that the issue “Remote Desktop Connection Broker is not ready for RPC communication” can be fixed by changing the RDP security layer. However, if the issue persists or you don’t want to take too much time on fixing the issue, you can try a free alternative to RDP -- AnyViewer.
