When connecting to LoadBalancer, the sessions are on the LoadBalancer machine not forwarded to the Terminal Servers?
Posted by - NA - on 23 October 2007 12:26 PM
It could be you are using a standard RDP client which is trying to connect to port 3389.

On the LoadBalancer machine Terminal Services is installed or the RDP listener is running on 3389, this will mean our listener is not running on the port and so a local terminal server session will be established.

Check the Console, Information to see which ports the Client Gateway is listening on.

As default our Listener is on port 80

So in a standard MSRDP client you would place in ipaddress:80 eg

If you wish to support normal rdp clients,. consider changing the RDP port of Windows and enabling our RDP listener on 3389 , you will find this under Connections.

(1389 vote(s))
Not helpful

Comments (0)
Post a new comment
Full Name: