session broker and Gateway Server? Can't connect External.
hello everybody! hope can me out here.
have 3 servers. 1 session broker (rds) , 2 session host servers (terminal1 & terminal2)
when local (inside of domain) use of rdp, desktop session load balanced ease.
when 1 client tries log on terminal1 , 1 “full”, rds tells client has go other server terminal2. part working.
when working remotly through rdp (external dns) , no vpn, connection successfull because there enough room client work on terminal1.
nat on router will redirect directly terminal1. when terminal1 “full” won’t accept new connections. thats logical because use session broker.
how can automatically redirect client rdp session (externally) when terminal1 busy other session redirect them terminal2? rd gateway perhaps?
vpn connection there no problem redirecting (load balancing)
if so, need install gateway on terminal1 and/or on terminal2 and/or on rds server(s)? can me out here. thanks!
hi,
rd gateway not require use rdweb. rd web access way publish remoteapps regular desktop connections. rdweb not same remoteapp.
to use rd gateway, need use client software compatible rd/ts gateway. example, when connecting ipad use itap mobile rdp, supports rd/ts gateway:
http://itap-mobile.com/itap-rdp
as wrote above, 2008 r2 rd gateway, microsoft windows remote desktop client uses port 443 connect rd gateway server, rd gateway makes connection using port 3389 rdsh server on behalf of client. remote desktop client included recent windows versions has ability use rd gateway.
with 2008 r2 rd gateway, only port used between client pc/device tcp port 443. why mentioned block port 3389 on firewall, because not needed if using rd gateway.
rd gateway works equally full remote desktop connections , remoteapp connections. ipad believe type of connection supported available software full desktop.
-tp
Windows Server > Remote Desktop Services (Terminal Services)
Comments
Post a Comment