Vadim Mikhal
asked on
RDS Session redirection
I have following RDS setup:
2 RD session Hosts RDSH01.local and RDSH02.local,Connection Broker RDCB01.local on the company network
RD Web Access RDWA01.local and RD Gateway RDGW01.local in DMZ
RDWA01.local has external FQDN RDWA01.com
RDGW01.local has external FQDN RDGW01.com
Internal users bypassing RD Gateway when accessing RemoteApps
If one session host fails (RDSH01.local), internal users got reconnected to another session host (RDSH02.local)
External users can connect to RemoteApps without problem. If external computer loses connection (disconnect network cable),and then connection established back, user got re-connected to the same session
However if session host fails (RDSH01.local) external user does not got re-connected to another session host (RDSH02.local) Instead lost connection attempts to re-connect to the same host and after 20 attempts permanently fails with error
"Remote Desktop cannot find computer RDCB01.local (connection broker) This might mean that RDCB01.local does not belong to the specified network. Verify the computer name and domain that you trying to connect to"
If I cancel remote desktop connection and re-start it - external computer connects to RDSH02.local (second session host) and external user can use applications
2 RD session Hosts RDSH01.local and RDSH02.local,Connection Broker RDCB01.local on the company network
RD Web Access RDWA01.local and RD Gateway RDGW01.local in DMZ
RDWA01.local has external FQDN RDWA01.com
RDGW01.local has external FQDN RDGW01.com
Internal users bypassing RD Gateway when accessing RemoteApps
If one session host fails (RDSH01.local), internal users got reconnected to another session host (RDSH02.local)
External users can connect to RemoteApps without problem. If external computer loses connection (disconnect network cable),and then connection established back, user got re-connected to the same session
However if session host fails (RDSH01.local) external user does not got re-connected to another session host (RDSH02.local) Instead lost connection attempts to re-connect to the same host and after 20 attempts permanently fails with error
"Remote Desktop cannot find computer RDCB01.local (connection broker) This might mean that RDCB01.local does not belong to the specified network. Verify the computer name and domain that you trying to connect to"
If I cancel remote desktop connection and re-start it - external computer connects to RDSH02.local (second session host) and external user can use applications
ASKER
I do not have public FQDN for Connection Broker
I have Public IP and FQDN for RD Web Access and RD Gateway
Do I need to set public IP for RD Connection Broker (it is not in DMZ,but on the network) and create public FQDN for Connection Broker
I have Public IP and FQDN for RD Web Access and RD Gateway
Do I need to set public IP for RD Connection Broker (it is not in DMZ,but on the network) and create public FQDN for Connection Broker
No its not required
In internal AD DNS server, create zone with public name space (you might have already) and simply create host(A) record representing public name for RDCB with private IP
In internal AD DNS server, create zone with public name space (you might have already) and simply create host(A) record representing public name for RDCB with private IP
ASKER
No I didn't created zone with public name space
Would you tell me how
Would you tell me how
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Set-RDPPublishName to rdcb.domain.com where rdcb.domain.com should point to connection broker server internal IP address and internal dns should have its host(A) record, you can use below script to change RDP publishing Name
https://gallery.technet.microsoft.com/Change-published-FQDN-for-2a029b80
OR
Set Alternate Full Address to rdcb.domain.com by running below command on RDCB server
Open in new window
Same time you need to create Host(A) record in internal DNS named rdcb.domain.com which points to connection broker internal IPCheck below post for more info.
http://ryanmangansitblog.com/2013/03/10/configuring-rds-2012-certificates-and-sso/
Also if you are using Win7 SP1, you must update RDP client on machines, otherwise you will get issues
http://support.microsoft.com/KB/2830477