[FreeNX-kNX] Using freenx to connect to a Windows Desktopserver (aka Terminalserver)
Tobias Bäumlin
tobias.baeumlin at gymneufeld.ch
Thu Dec 6 10:23:06 UTC 2012
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi
I have found an issue in the freenx implementation that I think might
be a bug:
When using freenx to connect to a Windows terminalserver I always got
an error from that, saying that it couldn't find a program named
/usr/bin/nxdesktop_helper and the user was logged out immediately,
whereas connecting to a normal Windows workstation worked fine.
After some digging I came up with the following line in the script
/usr/bin/nxdesktop_helper on the freenx server:
set -- -u "$agent_user" -k "$agent_keyboard" -d "$agent_domain" -f -s
"$windows_app" $AGENT_EXTRA_OPTIONS_RDP "$agent_server"
and the value of $windows_app apparently is
"/usr/bin/nxdesktop_helper", so the terminal server tries to run the
said program on login and pathetically fails to do so... voilà the
user is immediately logged out.
As a workaround I just deleted the '-s "$windows_app"' bit in the
above line and connecting to my terminal server works fine:
set -- -u "$agent_user" -k "$agent_keyboard" -d "$agent_domain" -f
$AGENT_EXTRA_OPTIONS_RDP "$agent_server"
I fail to see though whether there are scenarios where the -s
parameter for rdesktop is actually useful?
(Trying to run '/usr/bin/nxdesktop_helper' on a windows machine
obviously isn't...)
Regards
Tobias
- --
Tobias Bäumlin / ID Gymnasium Neufeld / Bremgartenstrasse 133 / 3012 Bern
+41 31 635 30 46
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/
iEYEARECAAYFAlDAcgoACgkQVwzN1zwEPJD0MwCfbF/xSC9Hn8IslepAPG0Wf9CH
x6wAnisHuVYFgvCqZgyp2vwMqUwnaYDE
=fNdR
-----END PGP SIGNATURE-----
More information about the FreeNX-kNX
mailing list