Hi Mathew, On Thu, Aug 15, 2013 at 10:21:51AM +0100, Mathew Levett wrote: > Hello Willy, > > I believe the client (mstsc.exe) connects to the Gateway server via RPC > over HTTPS (443), the gateway then terminates this, and makes a new normal > RDP connection to haproxy, and then onwards to the Real servers, so in this > case the Gateway is the client to haproxy. > > However what seams to be happening is that the loadbalancer then balances > the connections as normal but does not seam to honor the MSTS cookie at > all. its there in the packet capture and its encoded IP match the correct > server but it seams haproxy ignores it.
I suspect there is a very minor difference in the packets that make haproxy not recognize it as the one supposed to contain the MSTS cookie. It could be both a horrible or a subtle bug. Could you please send me privately a copy of the packet capture for the faulty connection ? I'd like to run the protocol parser by hand on it to understand what's wrong there. Thanks! Willy
