Hi
Firstly apologies if this is a bit mixed up but this is my first attempt at a RD Connection Broker Farm and I'm having a few difficulties. I have the following setup all using Server 2008/R2 Virtual servers and our users only use Remote Desktop connections
- no RemoteApps or Virtual Desktop infra-structure.
RD01 (192.168.1.243) - First Remote Desktop Session Host (internal name rd01.ptbm.local)
RD02 (192.168.1.244) - Second Remote Desktop Session Host (internal name rd02.ptbm.local)
GW01 (192.168.1.242) - Connection Broker, License Server & RDWeb server (internal name gw01.ptbm.local)
I have created an RD session farm called desktop.externaldomname.co.uk and configured this in DNS with a round-robin entry for each session host and also made the necessary config changes on the session host servers themselves. My internal clients use a RDC client to connect to address desktop.externaldomname.co.uk and the RD Connection Broker should connect them to their session. This seems to work 75% of the time but others it doesn't. There are no errors I can see in Event Viewer on any of the servers - the users just get a new session regardless if one already exists! Rebooting all the servers seems to cure if for a while and then it comes back. I've got the restriction "only allow one session" set on both Session Hosts and in Group Policy.That's the first problem. The second problem is when our external users are trying to connect to their Remote Desktop over RDWeb from home or a remote office. In Remote App Manager on each Session Host server I've entered the farm name (desktop.externaldomname.co.uk) in the RD Session Host Server Settings field as instructed. However, when my users try to connect they get an error:
"Remote Desktop cannot connect to the remote computer "desktop.externaldomname.co.uk" for one of these reasons:
Your user account is not listed in RD Gateway's permission list
You might have specified the remote computer in NETBIOS format but the RD Gateway is expecting an FQDN"
If we try RDWeb when connected to the the LAN then it works OK. Also if we use the local FQDN of the session host services in Remote App Manager instead of the farm name then it also works OK internally and externally. However, other TechNet posts state that it must be the farm name used not the individual session hosts.
So... I'm obviously doing something wrong and I wonder if it's down to me using a .local domain mixed with a .co.uk domain. I did this so I could use a regular SSL cert to secure all the servers not a SAN cert which can support the .local extension
- for a few more months at least. I'd really welcome any advice anyone could give as I can't find the exact same problem elsewhere on-line.
Thanks in advance
Andy Truelove
Andy Truelove Tate Computer Technology Ltd