On Thu, Mar 17, 2011 at 02:45:27PM -0500, Shaw, Christopher wrote:
> Willy,
> 
>       I thought I had come up with a working config file, but the
> server persistence still isn't behaving properly. If a server is down,
> or has its weight dropped to 0, a user is unable to reconnect to their
> session from a different IP -- which means that the RDP cookie
> persistence is broken somewhere.
> 
> Here is what I have under the "listen" section of my HAProxy config. Is
> there a specific order necessary for some of these directives? Or is
> there something else that I'm missing? Any help would be greatly
> appreciated.

No there is no particular order (except for the tcp-request content
rules, of course). Your ACL is not used, you can remove it.

I see no reason why this configuration would not work, as it's very
basic.

What you could do is to experiment with "balance roundrobin" to ensure
that the RDP cookie is properly sent : if it is not sent, your session
will be balanced across multiple servers.

You can also check with tcpdump/wireshark that the incoming connections
correctly contain the "msts" cookie. In fact, the symptoms you describ
would indicate that this is not the case and that only load balancing
is used, exactly as if this msts cookie was not sent by the client. The
fact that it works for other situations tends to indicate that the
client sends the "mstshash" cookie though (the one with the user name).

Regards,
Willy


Reply via email to