How can you fix Terminal Services Session Broker Client 1306 failed to redirect the user? Here in this post, we will offer you several solutions to solve this problem. If you encounter the same issue, you are going to the right place!
I got the Terminal Services Session Broker Client 1306 error. When I tried to connect directly to RDS01, even after logging in successfully, I got a message saying I didn't have access. In the event log, I saw event 1306 saying 'The Remote Desktop Connection Broker Client failed to redirect the user'. How can I fix this?”
- Question from Windows Forum
After adding a new tool to watch over remote desktop services in SCOM, certain servers commenced generating alerts featuring Event ID 1306 originating from the source TerminalServices-SessionBroker-Client in their event logs (Eventvwr > Applications and services > Microsoft > Windows > TerminalServices-SessionBroker-Client > Operational). The event's explanation denotes that "Remote Desktop Connection Broker Client failed to redirect the user. Event ID: 1306. Error: NULL".
All the affected servers shared a common trait: they were equipped with the Remote Desktop Session Host role, yet lacked any RDS Collections configured. However, after adding an RDS Collection to each server and performing a re-login, the error events ceased to appear. Instead, informational events 1308 and 1301 emerged, indicating that “RD Connection Broker Client processes a request from a user.”
In cases where an RDS Collection already exists, another potential cause of this error lies in the collection’s security layer.
Here are three solutions to fix "Remote Desktop Connection Broker Client failed to redirect the user. Error: NULL".
To prevent session redirection to RDSH in a fresh RDS setup, adjust the default collection settings in the RD Connection Broker's registry. Begin by establishing the registry value "DefaultTsvUrl" within the path:
HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\ClusterSettings
Assign the value "tsv://MS Terminal Services Plugin.1." to "DefaultTsvUrl" on the RD Connection Broker. Verify the value in Event Viewer on the RD Connection Broker.
Note: It's essential to create a backup before making any changes to the registry.
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.
If the previously mentioned solutions fail to deliver, consider switching to the error-free RDS alternative, AnyViewer for Windows Server. This remote desktop software enables users to connect to a remote server from any location. Developed by a skilled technical team, AnyViewer ensures a stable and secure environment for executing remote tasks without encountering errors.
AnyViewer boasts the following features:
➤Unattended remote access. Connect to unattended servers from a remote place with one click. ➤Multiple session. It allows remote control of multiple computers simultaneously. ➤Large file transfer. It supports flexible file transfer methods with high speed. ➤Screen walls. Monitor and manage multiple devices in one window simultaneously. ➤Device groups. Create groups to manage large numbers of devices conveniently. ➤Privacy mode. Access the remote servers with blackening their physical screens and disabling their physical keyboard to keep privacy and safety. ➤Multi-monitor support. It enables viewing and control of a multi-monitor server. ➤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. 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 server you want to remote control and click One-click control.
AnyViewer for mobile is available, too. You can access your Windows PC from your phone or tablet conveniently!
In conclusion, the Terminal Services Session Broker Client 1306 error typically arises from misconfigurations in RDS setups, particularly when RDS Collections are absent or security layers are improperly configured. To resolve this issue, users can employ several solutions, including adjusting registry values, configuring the RDP security layer correctly, or exploring alternative RDS options like AnyViewer for Windows Server. By implementing these solutions, users can ensure smooth and error-free remote desktop connections, enhancing productivity and efficiency in their workflow.