Quantcast
Channel: Remote Desktop Services (Terminal Services) Forum
Viewing all articles
Browse latest Browse all 493

2008 R2 Session Broker and RDS Farm - Client redirection issues

$
0
0

Hi all,

I'm seeing some issues with Thin Clients running XPe 2009 with RDP client 6.1.7600 RDP 7.0 supported

The setup

RDSB - 2008 R2 session broker (running DC roles as well)
RDSH01 and RDSH02 are members of farm "RDS"
They also have NLB configured with no affinity and TCP 3389

TC - XPe 2009 Thin Client running RDP Client

RDS.Domain.local exists in DNS and resolves to the NLB virtual IP

Connection that works
TC looks up rds.domain.local -> NLB directs it to RDSH01
TC logs into RDSH01
RDSH01 contacts the broker RDSB
RDSB can't find an active session, and conveniently load balances the connection to RDSH01
Bingo we're in

Connection that fails
TC looks up rds.domain.local -> NLB directs it to RDSH01
TC logs into RDSH01
RDSH01 contacts the broker RDSB
RDSB can't find an active session, and balances it to RDSH02
Error:

Remote Desktop can't connect to the remote computer for one of these reasons

1) Remote access to the server is not enabled
2) the remote computer is turned off
3) The remote computer is not available on the network

It appears that the RDP client doesn't handle redirection

Further info

NLA is not enabled
Encryption is set to negotiate 
This also happens when NLB is disabled and I'm using RR DNS

Both RDS Hosts list "connection type" as RDP 7.1

I can't find a change list between RDP 7.0 and 7.1, everything I've found just touts RemoteFX around

Is it possible to get RD Connection Broker/Redirection working with RDP 7.0 clients?

I can see a section in the RD Connection Manager on RDSB  for Redirection Settings
The body of the properties window mentions Virtual Desktop pools and Virtual Desktops
There is a sub section for DC version support, in which I have added an entry named rds-legacy.domain.local and tried with that resolving to the NLB IP and also making it a RR DNS entry for RDS01 and RDS02.

This post seems very similar to my issue, just an older client version - The resolution was not to use RD Session Broker.. which isn't ideal.
http://social.technet.microsoft.com/Forums/en-US/winserverTS/thread/14937433-9524-40a5-966e-dff62b04c354


Viewing all articles
Browse latest Browse all 493

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>