Hi sorry for being quiet on this but I was unavailable for a while.
I've updated to rev. 8abc0edd.. (current master) and it now seems stable, after many tries and using xfreerdp for a while, I've not been able to reproduce the problem yet. I'm aware that the fix you made is supposed to fix symptoms and not the cause of my problem, but I cannot currently reproduce it ... As for the debug information, with WITH_DEBUG_REDIR enabled, it looks like this : > $ ./xfreerdp -u userid -d domain -v rds.umons.ac.be > connected to rds.umons.ac.be:3389 > Password: > [DEBUG][com.freerdp.core.redirection] - flags: 0x0400, redirFlags: 0x0B0D > length: 182, sessionID: 0x00000001 > redirectionFlags = { > LB_TARGET_NET_ADDRESS > LB_USERNAME > LB_DOMAIN > LB_TARGET_FQDN > LB_TARGET_NETBIOS_NAME > LB_TARGET_NET_ADDRESSES > } > [DEBUG][com.freerdp.core.redirection] - Username: userid > [DEBUG][com.freerdp.core.redirection] - Domain: domain > [DEBUG][com.freerdp.core.redirection] - TargetFQDN: RDS1.umons.ac.be > [DEBUG][com.freerdp.core.redirection] - TargetNetBiosName: RDS1 > [DEBUG][com.freerdp.core.redirection] - TargetNetAddressesCount: 1 > [DEBUG][com.freerdp.core.redirection] - TargetNetAddresses[0]: 193.190.208.60 > connected to RDS1.umons.ac.be:3389 (some days it's redirected to RDS2... or RDS3... instead of RDS1, but it often reconnects to the same for a while) and then nothing until I log off > ERRINFO_LOGOFF_BY_USER (0x0000000C): > The disconnection was initiated by the user logging off his or her session on > the server. > DisconnectProviderUltimatum: reason: 3 which makes sense ... I'll try to setup a virtual machine with windows (is XP alright or too old for this ?) and wireshark to capture mstsc packets Alexis On 30/04/14 16:42, Marc-André Moreau wrote: > Hi Alexis, > > From my understanding, your deployment does not use a TS Gateway, which > should make debugging easier for us. Knowing this, here's what you can do: > > 1) Get mstsc to connect through the broker correctly > 2) Capture traffic with wireshark while mstsc connects > > There should be two TCP connections done by mstsc. The first connection is > done with the broker, and the broker sends a redirection packet to the > client. The client then disconnects and reconnects based on that redirection > packet. Information related to connection brokering is present in the very > first packet sent over TCP in an RDP connection, the X224 Connection Request. > In wireshark, look for the beginning of of those tcp connections, and copy > those X224 connection requests. I'd like to inspect them, as the specs are > very vague as to what should happen in practice for brokering. > > In addition to this, if you can have FreeRDP build with WITH_DEBUG_REDIR, I'd > have a sample redirection packet to look at. From there we can try to figure > out what FreeRDP is doing differently from mstsc. > > > On Wed, Apr 30, 2014 at 9:17 AM, Marc-André Moreau > <marcandre.mor...@gmail.com <mailto:marcandre.mor...@gmail.com>> wrote: > > Hi Alexis, > > You can build with WITH_DEBUG_REDIR, and see what redirection packet you > are getting. You are getting the redirection packet, but reconnection to the > redirected machine fails. In the case of the person I was assisting the other > day, I had issues connecting with mstsc, so it was hard to figure out what > was truly wrong. Also, I assume this should be cookie-based redirection, not > ip-based redirection, correct? The main difference is that with cookie based, > the client reconnect to the broker a second time but with a cookie that was > provided in the redirection packet. In ip-based, the client reconnects > directly to the address provided in the redirection packet. > > > On Wed, Apr 30, 2014 at 3:03 AM, Alexis Moinet <alexis.moi...@umons.ac.be > <mailto:alexis.moi...@umons.ac.be>> wrote: > > Hello > > On 29/04/14 17:02, Marc-André Moreau wrote: > > I've been investigating this all of yesterday with someone on IRC. > I fixed > > the double free issue on my branch. > > > https://github.com/awakecoding/FreeRDP/commit/c2a59c23a7b8eb262209bdadb66fe1e429ec943e > > Indeed, I can confirm no double free anymore, thanks! > > > This problem would only occur in the case of a failed redirection. > > $ ./xfreerdp -u username -d domain -v rdsserver > connected to rdsserver:3389 > Password: > freerdp_set_last_error 0x2000C > Error: protocol security negotiation or connection failure > recv: Bad file descriptor > > what kind of debug info would be useful to figure this out ? or at > least to know whether it's a freerdp bug or a server-side problem > > so far as I know, microsoft client is working fine, but I cannot test > it right now. > > thanks, > > Alexis > > > ------------------------------------------------------------------------------ "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs _______________________________________________ Freerdp-devel mailing list Freerdp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freerdp-devel