anyone have any thoughts on this? or is it something that will have to wait till freerdp 1.0 comes?


On Fri, Aug 19, 2011 at 3:26 PM, chris nelson <> wrote:
the latest git.


On Fri, Aug 19, 2011 at 3:09 PM, Mads Kiilerich <> wrote:
On 08/19/2011 10:39 PM, chris nelson wrote:

first of all, thanks for all of your incredible work! your product
is indispensable.

recently, i have noticed a pretty big bug in my terminal
services environment that it seems i have isolated to freerdp. first, a
little about my setup: i have a 2k8r2 session broker, and a farm of 4
2k8(non r2) terminal servers. the broker and farm are located off site
and we have a permanent vpn to their network. i have a
mixed environment with about 1/2 people connecting from xp machines, and
the other 1/2 connecting from linux machines (thinstation 2.3svn).

all terminal servers are configure to allow only one session per user.
when a user session is disconnected, upon reconnection they are
connected to their previous session with the xp clients 100% of the
time. however, with the freerdp clients, often they start a new session,
not connecting to their disconnected session. the users then lose their
work when we suffer network outages (i won't go into it, but it happens
frequently due to our vpn over comcast). i can duplicate this behavior
very reliably, although sometimes everything works as expected with
freerdp. the terminal server and session broker event logs do not shed
any light. the xp clients have never had this issue once.

i can provide some freerdp debug output if you'd like.

What FreeRDP version are you using?