From: Brian D <bj...@si...> - 2013-04-22 15:46:52
|
Hi Henrik, The r1710 fix has fixed this situation for me. Interestingly enough I was testing the old version just to make certain the issue still existed. What I found is that if I was already logged into the remote system, TLS was being attempted and my connection crashed. If however I was not logged in, the old released version, rdesktop-1.7.1-2.1.2, was working for the initial login. In either case, this latest fix solved it. Thank you for your diligence. Thanks for the pointer on TLS Authentication, I will take a look at that option as well. Regarding the "new NLA code" you mention, are you saying a server side change did indeed come with the patch I mentioned that appeared to be client only? Just trying to confirm that's how this issue started, as I've been using it for over a year without any problems. Thanks, Brian On Thu, Apr 18, 2013 at 3:30 AM, Henrik Andersson < hen...@ce...> wrote: > Hi Brian, > > I was pretty sure that rdesktop would fallback to plain RDP connection but > that was not the case. I have pushed a fix to upstream for that. Could you > update and recompile rdesktop to verify the functionlity. > > > Regards, > > Henrik Andersson > > > On 04/18/2013 07:37 AM, Henrik Andersson wrote: > > Hi Brian, > > This is due to the new NLA code of rdesktop, your server presents it can > do TLS but you do not have a certificate assigned to the RDP-tcp connection > which will make rdesktop fallback to use non TLS eg. plain RDP protocol. > > See following article how to configure a certificate for your server, > http://support.microsoft.com/kb/895433, which applies on both 2003 and > 2008. > > > Regards, > > Henrik Andersson > > |