Hello Marc-André, I tried both domain and non-domain accounts - the result is absolutely the same:
Domain account: VDCSP\SmartLogon, password Qal1029384756 Non-Domain account: WIN2008R2X64\Test, password Qal1029384756 Both of these accounts can log in successfully if RDP Security is used. What you saw as account and domain name lengths (zeroes) is what exactly was dumped by FreeRDP. > > Username (length = 0) > > > > Domain (length = 0) It seems that my setup is not special by any means - the test domain is comprised of Server 2008 SP2 (DC) + Server 2008R2 SP1 - both of them can act as TS. The servers in a production domain I tried to connect to (obviously, using difference domain and account information) reported the same error. Best regards, Maxim ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Freerdp-devel mailing list Freerdp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freerdp-devel
