Hello, As requested, you will find several files in attachment : http://dl.free.fr/pcOBG3mzU
The 3 debug files were generated during the connexions of the xfreerdp client (IP : 10.100.30.219) with the debugging option. The 2 pcap files were generated during the same connexions with the wireshark tool. Regards. -----Message d'origine----- De : Mads Kiilerich [mailto:m...@kiilerich.com] Envoyé : vendredi 3 décembre 2010 02:30 À : Olivier Dumon Cc : freerdp-devel@lists.sourceforge.net; Joey Messenger; Marc-André Moreau Objet : Re: [Freerdp-devel] Connection Problem on Windows 2008 R2 RDS Farm with FREERDP 0.8.2 Olivier Dumon wrote, On 12/03/2010 12:45 AM: > Hello, > > I agree with you, it doesn't work with me. I didn't say anything else ! > I can connect directly to any of the farm servers with freerdp (-0 option) > and with mstsc (/admin option) Can you connect to any of the machines with freerdp? If it never works, not even in a farm with only one machine, then we know that it isn't an issue with the farm/redirect functionality but ... something else. I got a private mail (!?) with a hint that the problem is in licensing model per-device versus per-user. Can you investigate that? Console/admin connections avoids licensing issues. > Again, i have no problem to connect to the farm with a windows mstsc client. > In attachment, you can find a connection of a mstsc client to the Windows > 2008 R2 servers farm. > > The client IP is 10.100.30.224 > The first remote desktop server IP is 10.100.30.228 > The second one is 10.100.30.226 Thanks. The trace shows that the servers offers/requests CredSSP security protocol (http://msdn.microsoft.com/en-us/library/cc240806%28v=PROT.10%29.aspx) which I don't think FreeRDP support. (A recent rdesktop patch might however inspire us to how it can be implemented.) Connecting with FreeRDP should however fall back to another supported protocol. I don't know how CredSSP influences the communication, but it surprises me that in both cases the first connection is closed by the client after several package exchanges, and then it reconnects - this time successfully. The actual communication is encrypted, so I don't know how the conversation goes. Can we get the output from a connection attempt with xfreerdp compiled with --with-debug ? (--no-tls as before is fine for a starter.) A wireshark trace of the same connection attempt might be handy too and answer unexpected questions. Is it possible to configure mstsc to use the "old" RDP security protocol and neither TLS nor CredSSP? That would be more similar to what xfreerdp does, so a trace of that might reveal something interesting. I and others have tested that connecting and redirecting works with 2008 R2 farm. There are probably lots of bugs left that we will fix when they are found, but it is probably also possible to work around the issues. /Mads ------------------------------------------------------------------------------ _______________________________________________ Freerdp-devel mailing list Freerdp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freerdp-devel
