If I invoke rdesktop from GNOME Command Line using the '-a 16' flag and connecting to a windows workstation, rdesktop launches properly. <br><br>When I try to then connect remotely, I am met with a 256 color screen. where do I need to add the -a flag to make it work for a Windows --> Linux --> Windows setup? nxdesktop_helper? If so, where?
<br><br>My nxdesktop_helper looks like this:<br>#####################################################<br>#!/bin/sh<br>#<br># nxdesktop_helper - Small helper for external rdesktop program as needed by NX 3.0.0 backend.<br>
#<br># Copyright (c) 2007 by Fabian Franz <<a href="mailto:freenx@fabian-franz.de">freenx@fabian-franz.de</a>><br>#<br># License: GPL, v2<br>#<br># SVN: $Id $<br>#<br><br>[ -z "$COMMAND_RDESKTOP" ] && COMMAND_RDESKTOP="rdesktop"
<br><br># setup commandline<br>set -- -f -u "$agent_user" -k "$agent_keyboard" -d "$agent_domain" "$agent_server"<br><br>if [ -n "$agent_password" ]<br>then<br> echo $agent_password | $COMMAND_RDESKTOP -p - "$@"
<br>else<br> $COMMAND_RDESKTOP "$@"<br>fi<br>###### End nxdesktop_helper ###############<br><br>Thanks for your help,<br><br>Steve<br><br><div><span class="gmail_quote">On 11/13/07, <b class="gmail_sendername">
Konrad J Hambrick</b> <<a href="mailto:konrad@jax01.payplus.com">konrad@jax01.payplus.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Steve --<br><br>When you invoked rdesktop from within GNOME,<br>did you include the -a flag ?<br><br> rdesktop -a 16 # man rdesktop<br><br>-- kjh<br><br>On 11/13/2007 09:44 AM, Stephen Kent wrote:<br>> Ok. That worked great. I had to learn a few new things but that is
<br>> a good thing. Now my issue is that I'd like the connections to be in<br>> full color. In the setup of NX Client for Windows 3, I have checked<br>> the custom settings and selected 16M colors. Connecting then still
<br>> only gives me 256 colors.<br>><br>> Any ideas on this?<br>><br>> Thanks,<br>><br>> Steve<br>><br>> On Nov 12, 2007, at 4:55 PM, Iain Paton wrote:<br>><br>>> Stephen Kent wrote:<br>
>>> I am trying to get FreeNX configured on CentOS 5 so that I can<br>>>> tunnel RDP sessions through. I have followed all of the<br>>>> instructions at<br>>>> <a href="http://wiki.centos.org/HowTos/FreeNX">
http://wiki.centos.org/HowTos/FreeNX</a><br>>> those instructions are somewhat dated, you may want to do some more<br>>> digging when using a 3.0.0 backend.<br>>><br>>>> I can easily connect to my GNOME desktop on the CentOS computer
<br>>>> but when I try to change the connection type to Window RDP, it<br>>>> looks like it is going to connect but the window disappears I get<br>>>> the following when I try to connect:<br>>> freenx isn't the greatest at logging failures, I had lots of
<br>>> problems with the window simply closing with no clue as to the<br>>> error while getting 3.0.0 running.<br>>><br>>> Here's what I did:<br>>><br>>> 1. grab the latest freenx from svn, some stuff for
3.0.0 backend is<br>>> missing in 0.7.1<br>>> 2. install rdesktop: <a href="http://www.rdesktop.org/">http://www.rdesktop.org/</a> or potentially<br>>> whatever comes with your distro. This seems to have changed with
<br>>> the 3.0.0 backend, it wants the external rdesktop prog and not the<br>>> nxdesktop variant. I'm using rdesktop 1.5.0.<br>>> 3. make sure your freenx has nxdesktop_helper installed in the<br>>> appropriate place
<br>>> 4. in node.conf add/change to the following:<br>>> # The key that contains the name of the complete path of the<br>>> 'rdesktop' command.<br>>> COMMAND_RDESKTOP=rdesktop<br>>><br>
>> and possibly also<br>>><br>>> # If nxdesktop cannot be found this is set automatically to "1".<br>>> ENABLE_EXTERNAL_NXDESKTOP="1"<br>>><br>>> although I didn't need that as I killed off nxdesktop when I
<br>>> removed the previous version.<br>>><br>>> YMMV, but this works for me using the !M 3.0.0-84 client from linux<br>>> and has worked for others using the !M windows client.<br>>><br>>> HTH,
<br>>> Iain<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>> <a href="http://openfacts.berlios.de/index-en.phtml?title=FreeNX_FAQ">http://openfacts.berlios.de/index-en.phtml?title=FreeNX_FAQ</a><br>> Don't forget to check the NX Knowledge Base:<br>>
<a href="http://www.nomachine.com/kb/">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">https://mail.kde.org/mailman/listinfo/freenx-knx</a><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> <a href="http://openfacts.berlios.de/index-en.phtml?title=FreeNX_FAQ">
http://openfacts.berlios.de/index-en.phtml?title=FreeNX_FAQ</a><br> Don't forget to check the NX Knowledge Base:<br> <a href="http://www.nomachine.com/kb/">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">
https://mail.kde.org/mailman/listinfo/freenx-knx</a><br>________________________________________________________________<br></blockquote></div><br>