Connection broker not reconnecting users to existing session

Hi,

We have an RDS 2012 R2 deployment with two RD Session Hosts where one (rds01) is running the Connection Broker. We also have a load balancer in front of the RD environment, with a LB IP (10.33.12.26).

The problem we have is that users are not reconnected to their existing session if their new connection attempt is not done against the same RD SH.

I have checked the Connection Broker event log, and can see that it finds the existing connection, but the new connection is still done to the wrong server.

Log from the first connect, without existing connection:

RD Connection Broker received connection request for user DOMAIN\user.
Hints in the RDP file (TSV URL) = tsv://MS Terminal Services Plugin.1.RDS
Initial Application = NULL
Call came from Redirector Server = rds02.domain.local
Redirector is configured as Farm member

RD Connection Broker successfully processed the connection request for user DOMAIN\user. Redirection info:
Target Name = RDS02
Target IP Address = 10.33.12.26, 10.33.12.32
Target Netbios = RDS02
Target FQDN = rds02.domain.local
Disconnected Session Found = 0x0

Session for user DOMAIN\local successfully added to RD Connection Broker's database.
Target Name = rds02.domain.local
Session ID = 18
Farm Name = RDS

This connection request has resulted in a successful session logon (User successfully logged on to the end point). Remote Desktop Connection Broker will stop monitoring this connection request.

I then disconnected the session, and made a new connection with the same user, which ended up on the other machine.

RD Connection Broker received connection request for user DOMAIN\user.
Hints in the RDP file (TSV URL) = tsv://MS Terminal Services Plugin.1.RDS
Initial Application = NULL
Call came from Redirector Server = rds01.domain.local
Redirector is configured as Virtual machine redirector

RD Connection Broker successfully processed the connection request for user DOMAIN\user. Redirection info:
Target Name = RDS02
Target IP Address = 10.33.12.26, 10.33.12.32
Target Netbios = RDS02
Target FQDN = rds02.domain.local
Disconnected Session Found = 0x1

Session for user DOMAIN\user successfully added to RD Connection Broker's database.
Target Name = rds01.domain.local
Session ID = 18
Farm Name = RDS

I might have missed something obvious, but I haven't found the cause. Is the problem that the LB IP is listed in the Target IP Address, so the client might be instructed to connect to that IP? IN that case, can I control which IP addresses should be included in the Target IP Address list?

May 28th, 2015 3:06pm


Hi Johan,

Please fully patch the RD connection broker and RD session hosts, there are a few similar threads were fixed by hotfixes.

Terminalserver Session Broker not reconnecting to existing session
https://social.technet.microsoft.com/Forums/en-US/6fd58d1f-9020-4bfa-ae5f-fb7b3411d8fc/terminalserver-session-broker-not-reconnecting-to-existing-session?forum=winserverTS

TerminalServices-SessionBroker not reconnecting to existing session
https://social.technet.microsoft.com/Forums/sqlserver/en-US/bef5ff08-eee8-4ac2-977a-5263717a4f2e/terminalservicessessionbroker-not-reconnecting-to-existing-session?forum=winserverTS

Remote Desktop Farm - disconnection issue for users connecting to a different TS than the one they disconnected from

https://social.technet.microsoft.com/Forums/windowsserver/en-US/c27e8028-ec53-4831-b152-90403f04ba4e/remote-desktop-farm-disconnection-issue-for-users-connecting-to-a-different-ts-than-the-one-they?forum=winserverTS

If after install all necessary updates,the issue persists, please check whether the issue occurs to all users or just some of them.

Best Regards,
Amy&

Free Windows Admin Tool Kit Click here and download it now
May 30th, 2015 9:51am

Hi,

The hotfixes mentioned are for 2008/2008 R2. We are running 2012 R2, so they are not applicable. It does not seem to be limited to certain users, as far as I have been able to tell.

June 1st, 2015 10:45am

Hi Johan,

Sorry for the confusion caused, what I meant was that similar issues were resolved by installing Windows updates, please install all necessary updates for your RD Connection Broker to see whether it works.

Best Regards,

Amy

Free Windows Admin Tool Kit Click here and download it now
June 2nd, 2015 6:33am

All Windows Updates are installed on the machines.

Is it possible to configure which IP the connection broker sends to the client, for each session host? I would like to exclude some interfaces from this.

June 2nd, 2015 12:58pm

In 2008R2, this can be configured in Session Host Configuration, by checking which IPs should be used for reconnect. How is this done in 2012R2?
Free Windows Admin Tool Kit Click here and download it now
June 2nd, 2015 2:30pm

Hi Johan,

In 2008R2, this can be configured in Session Host Configuration, by checking which IPs should be used for reconnect. How is this done in 2012R2?

We can still do this through registry in Windows Server 2012/R2, just not via GUI, since tsconfig console has been deprecated. That is under:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\ClusterSettings.

Please create a multi-string value named SessionDirectoryRedirectionIPs.

Here is a related thread below for you:

Configure which IP Win2012 R2 RD Session Host listens on

https://social.technet.microsoft.com/Forums/en-US/b7f50391-f2ea-43a1-9e95-d12dd8f71ec2/configure-which-ip-win2012-r2-rd-session-host-listens-on?forum=winserverTS

Best Regards,

Amy

June 9th, 2015 3:30am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics