Problem with RD Session Broker, Certificates, and Token Based Routing through an ACE
hello,
i have 2 rdp servers in farm using token based routing through cisco ace appliance.
one of rdp servers functioning session broker.
the farm dns name rdsb.domain.com
the rdp servers named rdp1.domain.com , rdp2.domain.com.
the issue having when assign certificate both rdp servers fqdn of rdsb.domain.com, rdp connection client machine fails. there not details of failure, no entries in logs of either server, client, nor ace.
if change certificates on rdp servers fqdn individual name (ie rdp1.domain.com has cert rdp1.domain.com) connection works fine, rdp client warns user trying connect rdsb.domain.com , getting certificate fqdn of rdp1.domain.com (or rdp2.domain.com depending on server trying connect to).
i've searched high , low information on how these certificates supposed setup...
is configuraiton issue rd session broker, configuration issue rd hosts, or configuraiton issue cisco ace?
i want client conect rdsb.domain.com , have work without warning certificate different fqdn.
thank you,
daren
naresh,
thank information.
we figured issue out... i'll post happened in case else encounters issue. can affect using load balancer rdp traffic , using session broker.
after investigation cisco ace appliance, found rdp1.domain.com listed being "out of service". means load balancer considered rdp1 down , not try send traffic it.
the rdp client connected rdsb.domain.com (the vip load balancer). load balancer contacted rdp2.domain.com (since rdp1 considered down in eyes of load balancer).
rdp2 contacted session broker on rdp1 find out rdp server in farm should take on new connection.
the session broker said rdp1 take new connection. response packaged token sent load balancer (we using token based routing our rdp farm). load balancer unable route traffic rdp1 because thought rdp1 down... connection failed, no specific error message , no logs on of servers.
after getting ace configuration resolved... , session broker on rdp1 communicating ace properly, issues resolved. able use our certificate rdsb.domain.com without issue , connections being brokered correctly.
this different having rdp session broker fail, or rdp1 fail because had actual failure, none of other rdp servers in farm able contact rdp session broker , work independently... , load balancer route traffic correctly using vip.
i hope helps in future, strange issue , being windows engineer, don't have lot of experience cisco ace appliance load balancer.
Windows Server > Remote Desktop Services (Terminal Services)
Comments
Post a Comment