Error 1306 Remote Desktop

Maybe it doesn't like even numbers of processors. I've seen SQL Server fail to start for the opposite reason. Try giving it 3 instead of 2

We sorted it. Seems that both the Session Host and Connection broker both need the same number of virtual CPUs.

As soon as we set them both to use two vCPUs everything started working as normal.

Odd, but one to remember for the future.

We're running a 2012 R2 RDS environment and have a different number of cores per the CB and SH's. Unless this is something new to 2019, I'm not sure that is a requirement. A session host has much higher processing needs than a connection broker. Maybe this is a new requirement I've never heard before, but that does not sound correct to me.

Hi Thanks for replying, Yes Remote desktop is enabled on both servers, I don't know if the RDS setup enables it or not. but I manually enable it when setting up the server settings after first install like IP, computer name etc, during this process i also enable Remote Desktop. - And Yes i've verified it right now that its enabled on both servers.

Also upon further investigation i am also getting the following Event ID's 1280, 1296 & 1306 - when i login as a user.

Event ID 1280: Remote Desktop Services failed to join the Connection Broker on server RDSCLUSTER-01.domain.com.
Error: Current async message was dropped by async dispatcher, because there is a new message which will override the current one.

Event ID 1296: Remote Desktop Connection Broker Client failed while getting redirection packet from Connection Broker.User : domain\username

Error: Remote Desktop Connection Broker is not ready for RPC communication.

Remote Desktop Connection Broker Client failed while getting redirection packet from Connection Broker.User: domain\username Error: Element not found.

Event ID 1306: Remote Desktop Connection Broker Client failed to redirect the user domain\username.

Error: NULL

Hi All,I have a RDS deployment based on W2K19 Server.

RDS07 - Session Host Server

RDS08 - Session Host Server

RDS09 - Session Host Server

DCS01 - Connection Broker

RDW01 - RD Web Access

I have installed all the servers I configured three collection and when I want to connect from mstsc.exe to Connection broker I got the message:

The connection was denied because the user account is not authorised for the remote login.When I want to directly connect to RD07 08 or 09 using mstsc there is no problem.

When I added my user to remote users on connection broker I had an error ID 1306 that connection broker:

Remote Desktop Connection Broker Client failed to redirect the users domain\user....Error: NULL

Can anyone help me with it? How to setup it to let our users to connect to RDC01 (Connection Broker) and be redirected to proper Host Server based on Session Configuration?

I have an issue with a RDS server (Windows 2012R2)
I had to migrate this server to a new domain, but since it's impossible to login through RDP.

When I try to connect this server from a Windows client I have the error:
"This computer can't connect to the remote computer. Try connection again. If the problem continues, contact the owner of the remote computer or your network administrator."

No other events in the server log or client log.

So I decided to uninstall the RDS role on this server. After that, I was able to connect through RDP. I tried to reinstall the role, the problem occur again.

After investigations, I found that when I set the MinEncryption Level to 1 (https://www.mvps.net/docs/how-to-secure-remote-desktop-rdp/) the connection works.

I think the problem is when the TLS session is initiated.

I decided to renew all the certificates for the server, broker and licence manager (which is the same machine). Register the licence manager server again (no error in the licence diagnostic)

Delete registry key in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM

Still no luck.

Event ID 1306 — RD Connection Broker Communication

Published: January 8, 2010

Applies To: Windows Server 2008 R2

Remote Desktop Connection Broker (RD Connection Broker), formerly Terminal Services Session Broker, is a Remote Desktop Services role service in Windows Server 2008 R2 that supports session load balancing between RD Session Host servers in a farm, connections to virtual desktops, and reconnection to an existing session in a load-balanced RD Session Host server farm. For RD Connection Broker to work properly, the RD Session Host server must be able to communicate with the RD Connection Broker server across the network.

Event Details

Product:	Windows Operating System
ID:	1306
Source:	Microsoft-Windows-TerminalServices-SessionBroker-Client
Version:	6.1
Symbolic Name:	EVENT_FAIL_REDIRECTION
Message:	Remote Desktop Connection Broker Client failed to redirect the user %1\%2. HRESULT = %3

Resolve
Identify and fix network connectivity issues

To resolve this issue, identify and fix any network connectivity problems between the RD Session Host server and the RD Connection Broker server.

Note: The following procedures include steps for using the ping command to perform troubleshooting. Therefore, before performing these steps, check whether the firewall or Internet Protocol security (IPsec) settings on your network allow Internet Control Message Protocol (ICMP) traffic. ICMP is the TCP/IP protocol that is used by the ping command.

To perform these procedures, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.

If you cannot successfully ping the RD Connection Broker server by IP address, this indicates a possible issue with network connectivity, firewall configuration, or IPsec configuration.

The following are some additional troubleshooting steps that you can perform to help identify the root cause of the problem:

Ping other computers on the network to help determine the extent of the network connectivity issue.
If you can ping other servers but not the RD Connection Broker server, try to ping the RD Connection Broker server from another computer. If you cannot ping the RD Connection Broker server from any computer, first ensure that the RD Connection Broker server is running. If the RD Connection Broker server is running, check the network settings on the RD Connection Broker server.
Check the TCP/IP settings on the local computer by doing the following:
1. Click Start, click Run, type cmd, and then click OK.
2. At the command prompt, type ipconfig /all, and then press ENTER. Make sure that the information listed is correct.
3. Type ping localhost to verify that TCP/IP is installed and correctly configured on the local computer. If the ping is unsuccessful, this may indicate a corrupt TCP/IP stack or a problem with your network adapter.
4. Type ping IP_address, where IP_address is the IP address assigned to the computer. If you can ping the localhost address but not the local address, there may be an issue with the routing table or with the network adapter driver.
5. Type ping DNS_server, where DNS_server is the IP address assigned to the DNS server. If there is more than one DNS server on your network, you should ping each one. If you cannot ping the DNS servers, this indicates a potential problem with the DNS servers, or with the network between the computer and the DNS servers.
6. If the RD Connection Broker server is on a different subnet, try to ping the default gateway. If you cannot ping the default gateway, this might indicate a problem with the network adapter, the router or gateway device, cabling, or other connectivity hardware.
In Device Manager, check the status of the network adapter. To open Device Manager, click Start, click Run, type devmgmt.msc, and then click OK.
Check network connectivity indicator lights on the computer and at the hub or router. Check network cabling.
Check firewall settings by using the Windows Firewall with Advanced Security snap-in.
Check IPsec settings by using the IP Security Policy Management snap-in.

Verify

To verify that the RD Session Host server can successfully communicate with the RD Connection Broker server:

On the RD Session Host server, start a new Remote Desktop Services session.
After the session is established, disconnect the session. Do not log off from the session.
On a different RD Session Host server, try to reconnect to your existing session. If you are able to reconnect to the existing session, the RD Session Host server is successfully communicating with the RD Connection Broker server.

Related Management Information

RD Connection Broker Communication

Remote Desktop Services