Pushed to the bzr branch.<br><br>Thanks.<br><br><div class="gmail_quote">On Fri, Feb 27, 2009 at 3:59 AM, Jeremy Wilkins <span dir="ltr"><<a href="mailto:wjeremy@shaw.ca">wjeremy@shaw.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
I just noticed this error this week. Marcelo, could please make that change<br>
in the main trunk and credit Jim for the edit. If we want to allow spaces I<br>
think we might be able use the URL encoded version of the domain name. We<br>
need to look into this later though. I have had troubles logging into a<br>
Windows Server 2008 box with these quotes here. It makes domain logons<br>
impossible which is worse than only domains with spaces. Thank you Jim for<br>
pointing that out.<br>
<div class="Ih2E3d"><br>
<br>
jim.sifferle wrote:<br>
><br>
> Hi Shima,<br>
><br>
> I downloaded and applied the diff. It worked well, except I had to make<br>
> one small change on Line 40 of nxdesktop_helper.<br>
><br>
> - [ "$agent_domain" = "" ] || DOMAIN="-d \"$agent_domain\""<br>
> + [ "$agent_domain" = "" ] || DOMAIN="-d $agent_domain"<br>
><br>
> The reason for the change is that Windows authentication failed because<br>
> the username was "DOMAIN"\username, where the quotes were treated<br>
> literally as part of the domain name. I can't imagine anyone would have a<br>
> Windows NetBIOS domain name with a space in it. I think you may be able<br>
> to safely remove the escaped quotes. It worked great for me.<br>
><br>
> Thanks for your help!<br>
><br>
> Thanks,<br>
><br>
> Jim Sifferle<br>
> Danaher T&M / Tektronix Network Services<br>
> Work: 503-627-5364<br>
> Mobile: 503-860-5558<br>
</div>> <a href="mailto:Jim.sifferle@tektronix.com">Jim.sifferle@tektronix.com</a><mailto:<a href="mailto:Jim.sifferle@tektronix.com">Jim.sifferle@tektronix.com</a>><br>
<div class="Ih2E3d">><br>
><br>
> From: Marcelo Boveto Shima [mailto:<a href="mailto:marceloshima@gmail.com">marceloshima@gmail.com</a>]<br>
> Sent: Thursday, February 26, 2009 2:58 PM<br>
> To: User Support for FreeNX Server and kNX Client<br>
> Subject: Re: [FreeNX-kNX] Cannot use Windows Desktop<br>
><br>
> Hello,<br>
><br>
> This should be <a href="https://bugs.edge.launchpad.net/freenx-server/+bug/295958" target="_blank">https://bugs.edge.launchpad.net/freenx-server/+bug/295958</a><br>
> The fix is<br>
> <a href="http://bazaar.launchpad.net/%7Efreenx-team/freenx-server/ubuntu/revision/84" target="_blank">http://bazaar.launchpad.net/~freenx-team/freenx-server/ubuntu/revision/84</a><br>
><br>
> Regards.<br>
> Shima<br>
> On Thu, Feb 26, 2009 at 7:20 PM,<br>
</div><div class="Ih2E3d">> <<a href="mailto:jim.sifferle@tektronix.com">jim.sifferle@tektronix.com</a><mailto:<a href="mailto:jim.sifferle@tektronix.com">jim.sifferle@tektronix.com</a>>> wrote:<br>
><br>
> Hi,<br>
><br>
><br>
><br>
> I'm having trouble using the Windows Desktop / Terminal Services feature<br>
> on my systems. When I connect using FreeNX / Terminal Services, I get<br>
> logged into the Windows server, then receive an error "The system cannot<br>
> find the path specified. This initial program cannot be started:<br>
> /usr/bin/nxdesktop_helper. Please consult Help for more information."<br>
> This error appears to be coming from the Windows server, and it occurs<br>
> whether I specify a program to run after login or not. I get the same<br>
> error if the NoMachine client is set to Present the Windows Logon screen.<br>
> In that case, I get the login screen, successfully login, and then get the<br>
> error.<br>
><br>
><br>
><br>
> All systems run CentOS 5.2, and have FreeNX 0.7.3 and NoMachine client<br>
> 3.3.0-6 installed. The FreeNX packages came from the CentOS Extras repo.<br>
><br>
><br>
><br>
> Any ideas?<br>
><br>
><br>
><br>
> Thanks,<br>
><br>
><br>
><br>
> Jim Sifferle<br>
><br>
> Danaher T&M / Tektronix Network Services<br>
><br>
> Work: 503-627-5364<br>
><br>
> Mobile: 503-860-5558<br>
><br>
</div>> <a href="mailto:Jim.sifferle@tektronix.com">Jim.sifferle@tektronix.com</a><mailto:<a href="mailto:Jim.sifferle@tektronix.com">Jim.sifferle@tektronix.com</a>><br>
<div class="Ih2E3d">><br>
><br>
><br>
><br>
><br>
> ________________________________________________________________<br>
> Were you helped on this list with your FreeNX problem?<br>
> Then please write up the solution in the FreeNX Wiki/FAQ:<br>
><br>
> <a href="http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ" target="_blank">http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ</a><br>
><br>
> Don't forget to check the NX Knowledge Base:<br>
> <a href="http://www.nomachine.com/kb/" target="_blank">http://www.nomachine.com/kb/</a><br>
><br>
> ________________________________________________________________<br>
> FreeNX-kNX mailing list ---<br>
</div>> <a href="mailto:FreeNX-kNX@kde.org">FreeNX-kNX@kde.org</a><mailto:<a href="mailto:FreeNX-kNX@kde.org">FreeNX-kNX@kde.org</a>><br>
<div class="Ih2E3d">> <a href="https://mail.kde.org/mailman/listinfo/freenx-knx" target="_blank">https://mail.kde.org/mailman/listinfo/freenx-knx</a><br>
> ________________________________________________________________<br>
><br>
><br>
> ________________________________________________________________<br>
> Were you helped on this list with your FreeNX problem?<br>
> Then please write up the solution in the FreeNX Wiki/FAQ:<br>
><br>
> <a href="http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ" target="_blank">http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ</a><br>
><br>
> Don't forget to check the NX Knowledge Base:<br>
> <a href="http://www.nomachine.com/kb/" target="_blank">http://www.nomachine.com/kb/</a><br>
><br>
> ________________________________________________________________<br>
> FreeNX-kNX mailing list --- <a href="mailto:FreeNX-kNX@kde.org">FreeNX-kNX@kde.org</a><br>
> <a href="https://mail.kde.org/mailman/listinfo/freenx-knx" target="_blank">https://mail.kde.org/mailman/listinfo/freenx-knx</a><br>
> ________________________________________________________________<br>
><br>
<br>
</div><font color="#888888">--<br>
View this message in context: <a href="http://www.nabble.com/Cannot-use-Windows-Desktop-tp22235128p22240499.html" target="_blank">http://www.nabble.com/Cannot-use-Windows-Desktop-tp22235128p22240499.html</a><br>
Sent from the freenx-knx mailing list archive at Nabble.com.<br>
</font><div><div></div><div class="Wj3C7c"><br>
________________________________________________________________<br>
Were you helped on this list with your FreeNX problem?<br>
Then please write up the solution in the FreeNX Wiki/FAQ:<br>
<br>
<a href="http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ" target="_blank">http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ</a><br>
<br>
Don't forget to check the NX Knowledge Base:<br>
<a href="http://www.nomachine.com/kb/" target="_blank">http://www.nomachine.com/kb/</a><br>
<br>
________________________________________________________________<br>
FreeNX-kNX mailing list --- <a href="mailto:FreeNX-kNX@kde.org">FreeNX-kNX@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/freenx-knx" target="_blank">https://mail.kde.org/mailman/listinfo/freenx-knx</a><br>
________________________________________________________________<br>
</div></div></blockquote></div><br>