The issue: Terminal Services Session Broker Client 1306 failed to redirect the user
I encountered the ‘Terminal ServicesSession BrokerClient 1306’ error. I can connect to the published RDP desktop from a Win10 desktop without errors in the logs. I successfully authenticate as a user when attempting to RDP straight to RDS01, but I receive a message saying that the user does not have access to the system. In the event log, I get event 1306 with the message ‘The Remote Desktop Connection Broker Client failed to redirect the user’. How can I solve this issue?”
- Question from Windows Forum
How to fix Remote Desktop Connection Broker Client failed to redirect the user [4 solutions]
Remote Desktop Connection Broker is a Remote Desktop Services role service in Windows Server that allows session load balancing across RD Session Host servers in a farm, virtual desktop connections, and session connections in a load-balanced RD Session Host server farm.
However, when users perform Windows Server Remote Connections, they may encounter problems such as “Remote Desktop Connection Broker is not ready for RPC communication". This post will discuss how to solve the Remote Desktop Connection Broker Client failed problem.
Solution 1. Check Internet connection
First, you need to check whether there is a working network connection.
Step 1. Open Control Panel. Click View network status and tasks.
Step 2. Double-click your connections to check the network status.
Solution 2. Check TCP/IP settings on the local computer
You can check the TCP/IP settings on the local computer to see whether the problem is with the network adapter.
Step 1. Press Win + R, enter "cmd" and hit OK.
Step 2. Enter the command “ipconfig /all” and press Enter. Make sure all the listed information is correct.
Step 3. Use the command “ping localhost” to check that TCP/IP is installed and set up correctly on the local computer. If the ping fails, your network interface or the TCP/IP stack may malfunction.
Step 4. Type “ping IP_address” and press Enter. (IP_address is the computer IP). It may be a problem with the routing table or the network adapter driver if you can ping localhost but not the local IP.
Step 5. Type “ping DNS_server” and press Enter. (DNS_server is the DNS server IP.) You should ping each DNS server if your network has more than one. If you cannot ping the DNS servers, there may be a network issue between the PCs and the DNS servers or a potential problem with the DNS servers themselves.
Step 6. Try pinging the default gateway if the RD Connection Broker server is on a different subnet. When you cannot ping the default gateway, the network adapter, router, gateway device, cabling, or other connectivity hardware may be at issue.
Solution 3. Configure RDP security layer
There is a setting for Security Layer. Try to set it to RDP Security Layer to solve the problem.
Step 1. Open Group Policy Editor and navigate to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security. Double-click Require use of specific security layer for remote (RDP) connection.
Step 2. Tick Enabled. Select RDP from Security Layer. Click OK to take effect.
Solution 4. Switch to the best Remote Desktop alternative [error-free]
If the above solutions do not work, switch to the best Remote Desktop alternative AnyViewer. AnyViewer is developed by a strong technical team, ensuring a stable and safe environment to perform remote tasks without errors. Besides, in addition to unattended remote access, it has the following advanced features over RDP:
➤Large file transfer. It supports flexible file transfer methods with high speed.
➤Multiple session. It allows remote control multiple computers simultaneously.
➤Multi-monitor support. It enables view and control a multi-monitor device.
➤Chat. It offers a chat box in the remote session, making it convenient for users to exchange messages instantly.
Don’t hesitate to download AnyViewer on your devices!
You can start a remote session with the simple steps below:
Step 1. Start AnyViewer on the host. Click Sign up for registration.
Step 2. Enter the information to complete Sign up.
Step 3. Start AnyViewer on the client. Log in to the account you registered. The device will automatically assign when you log in.
Step 4. Click Device. Click the computer you want to remote control, and click One-click control.
- Notes:✎... AnyViewer also has cost-effective plans for businesses. You can select Professional or Enterprise plan to enjoy more rights!
AnyViewer for mobile is available, too. You can access your Windows PC from your phone or tablet conveniently!
We hope the troubleshooting steps we detailed in this post helped you to fix the ‘Terminal Services Session Broker Client 1306’ error. If you seek an error-free remote desktop tool with advanced features, try AnyViewer.