RDP farm automatic session reconnect

Have you run a packet capture from either end? That will let you know whether a timeout is occurring, or whether a TCP RST is being sent one way or another. I would start with that known first.

I'd suspect a policy on your firewall is doing this. Though, if that's the case, the capture will show the TCP RST coming from the inside host's IP (same socket) .

Kevin, to answer one point you wrote:

"I imagine this system doubling as a session host could be trouble under heavy load, but this is only a trial."

Not at all, the broker service is a very lean service which all it does is poll the various servers in the farm and maintain who is logged on where in a small database and tell where to go.

There are a few steps in setting up RD Session Farms.

This is the best starting point: http://technet.microsoft.com/en-us/library/cc753891.aspx

But in essence:

1) Create a round robin dns entry with the farm name which has the IP of all your session host servers. 2) On the broker, add all session host (alpha + beta in your case) to the group Remote Desktop Server (may be slightly different name, I don't have it in front of me). 3) Setup the Remote desktop service telling it that it is part of a farm. 4) Enable the policy of "one session per user" - otherwise you may have a situation where a user has a session on each server.

Then with all that, on the client you just go to the farm name (since it's in DNS).

Your client will be directed to one of the entry in the round robin dns. They will get a logon prompt. The server they got will then check with the broker to see whether they should let the user on or redirect him to a different server and proceed.

If you are using pre-win7 clients, then they will get a repeated login screen if they get redirected. A bit annoying my users are saying! But on win7+ clients then it does not do that.