On Tue, Apr 5, 2011 at 11:04 PM, Mads Kiilerich <[email protected]> wrote: > I assume you are using the tip of the development branch? I guess you > manually added an extra printout of the full pduType field?
yes and yes. > > The pduType warning is "mine", and it is usually a strong indication that > something went completely wrong before this point and nothing after this > point should be trusted. Ok thats good to know, maybe the message should be changed to reflect that? > > But ... do you agree that it seems like the problem just is that FreeRDP in > NLA mode doesn't close the connection soon enough after the login has > failed? Yes (I'm used to it displaying the error on the remote side and giving the possibility to "fix" whats wrong, but i guess that was before NLA came along. but now when comparing to a Win7 mstsc that is its behavior.) > > It sounds like something that should be simple to reproduce. > > You could perhaps try to configure --with-debug --with-debug-nla > --with-debug-assert --with-debug-stream-assert . That might give more > information and stop sooner after the real problem has occurred. Note that > the debug output will contain your credentials, so you might want to change > them temporarily if you want to share the output. Running under valgrind > might also give a hint - but IIRC it already has a lot of complaints in NLA > mode. > > /Mads > It probably is, a NLA capable server with a limited user account that does not have the rights to use RDP shuld show this? It stopped much sooner, right after password prompt: xfreerdp: ntlmssp.c:1147: ntlmssp_send_negotiate_message: Assertion `((s)->p + 8 <= (s)->end)' failed. Aborted valgrind didn't want to come out and play with me right now.. will try and get it to work and post again. /Christian > > Christian Nilsson wrote, On 04/05/2011 10:31 PM: >> >> Hi, >> >> I use Windows 7 Ultimate (64-bit Swedish no SP) Connected to a AD >> domain (2003r2) >> >> This is the same machine that i normally use, i normally connect with >> a local user account and everything works. >> Now i tried to logon to the same machine but use my domain user >> account. which fails with errors below and black or no GUI. >> I then tried with --no-nla, and get the logon prompt. the domain user >> i tried to logon with do not have access to use remote desktop. so i >> get a error message saying so. >> If I use another account that has rights to use remote desktop, then >> everything works. >> >> >> Using NLA and a user account that don't have enough permissions to use >> remote desktop seams to be the cause, even a local account without rdp >> permissions trigger it. So i don't think it has anything to do with >> the domain. >> Anybody else that can confirm this? >> >> >> there are quite a few different errors and i would probably get a new >> one for every time i run it. >> >> >> (modified the ui_error line to output the whole pduType in hex) ------------------------------------------------------------------------------ Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev _______________________________________________ Freerdp-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freerdp-devel
