HA Connection Broker does not detect failed session host
i have deployment of 2 windows server 2012 r2 hosts, each running rdcb service in ha arrangement (the sql database on separate server). in addition each host running rdsh service.
the rdcb address load balanced via dns round robin.
if user creates rdp session on host, disconnects, , host "disconnected" session becomes unavailable (i.e. disconnected network), broker continue attempt redirect user existing disconnected session though server unavailable.
i have tried adjusting registry settings per post:
https://social.technet.microsoft.com/forums/windowsserver/en-us/050ed3c2-1356-4c69-8337-1be735494670/session-broker-heartbeat-solution?forum=winserverts
but problem persists.
new rdp connections work fine, remaining broker creating new sessions on remaining host.
this post:
https://social.technet.microsoft.com/forums/windowsserver/en-us/757c747f-b390-4f0a-aeb2-493400f6029a/windows-server-2012-r2-session-broker-offline-server-detection?forum=winserverts
mentions co-locating rdcb , rdsh roles may problematic, seemed related new sessions. my new sessions working fine.
can shine light on problem?
surely connection broker should able detect failed session hosts ?!
if user creates rdp session on host, disconnects, , host "disconnected" session becomes unavailable (i.e. disconnected network), broker continue attempt redirect user existing disconnected session though server unavailable.
hi,
i have 1 rd connection broker in testing environment, , it’s been installed on dedicated server.
in tests, connection broker stop redirecting session unavailable rd session host after minute or so, client tried reconnect existing rdp session remote computer unavailable message, next connection directed available host new session.
best regards,
amy
please remember mark replies answers if , un-mark them if provide no help. if have feedback technet subscriber support, contact tnmff@microsoft.com.
Windows Server > Remote Desktop Services (Terminal Services)
Comments
Post a Comment