Users unable to connect to RDP farm. (2 session servers 1 broker)

issue: users unable connect farm when use tsfarm.mydomain.com access our servers. on connection broker server lots of: connection request has timed out. user not log on end point within alloted time. remote desktop connection broker stop monitoring connection request.

on 1 of session servers following:

session state user domain\firstname.lastname changed to: session reconnected.
target name = session2.domain.com
farm name = tsfarm.mydomain.com
session id = 8

it looks they're getting connected, doesn't work either.

server environment

all servers windows 2008 r2 datacenter sp1

connection broker: connect1

session servers: session1, session2

external dns has following records:

tsfarm.mydomain.com points external (nat) ip session1

tsfarm.mydomain.com points external (nat) ip session2

user environment

almost users use windows 7 running version 6.1 client protocol version 7.1

hi,

correct.

in remote desktop client, advanced tab, connect anywhere, settings, select use these rd gateway server settings, enter rdgateway.yourdomain.com (or whatever fqdn want use rdg).  on general tab enter tsfarm.yourdomain.com in computer box.

on public internet create dns record rdgateway.yourdomain.com points public ip address rdg.  on firewall forward tcp port 443 rdg server.

on internal network create 2 dns records tsfarm.yourdomain.com point rdsh servers.  based on have written believe have created these dns records farm name.

as side note may consider installing rd web access on same server rd gateway server.  way if want (it not required) have users log on rd web access , launch remoteapp or full desktop connection rdsh farm.

you need certificate (or certificates) trusted public authority such godaddy, geotrust, thawte, verisign, etc.  1 option wildcard (*.yourdomain.com) you may use all rds purposes (broker, rdg, rdweb, rdsh, digital signing).  second option multiple single-name certificates.  example, 1 certificate subject rdgateway.yourdomain.com , second certificate subject of tsfarm.yourdomain.com.

for planning purposes keep in mind if have rd gateway , rd web on same server use same certificate.  if use single-name certificate rd gateway of rdgateway.yourdomain.com users need access rdweb using rdgateway.yourdomain.com.  if choose wildcard have maximum flexibility use different names each purpose since same certificate.

-tp

Windows Server  >  Remote Desktop Services (Terminal Services)