Mathis,<br> Have you checked in the "Advanced" settings to make sure "Disable encryption of all traffic" is unchecked? I've found that clients with this checked fail to connect similar to your issue.<br>
Also, you should be aware that NXClient 3.3.0 has changes that do not work well with freenx 0.7.3. We've seen a mouse issue for a specific application when it will skip and shift the actual pointer to the lower right corner of the cursor icon. Try to get an earlier copy of NXClient (ie 3.0.0) if possible. <br>
<br>-Lorenzo<br><br><div class="gmail_quote">On Mon, Apr 20, 2009 at 3:28 AM, <span dir="ltr"><<a href="mailto:mathis.schmieder@daimler.com">mathis.schmieder@daimler.com</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><font face="sans-serif" size="2">Hello everyone,</font><br><br><font face="sans-serif" size="2">I am currently experiencing lots of
problems setting up a working FreeNX configuration. The usecase is connecting
from Windows clients to Linux workstations running RedHat Enterprise Linux
5. Our Windows and Linux networks are heavily firewalled (one reason why
we chose FreeNX), but SSH connections are allowed. I have no problems whatsoever
connecting to the Linux network using my own account or the "nx"-account,
public key authentication works, too. When I try to connect using NoMachine's
NX Client, I get stuck at "Negotiating link parameters". Looking
into the SSH log file, every time NX Client reaches the negotiating part
I get a "channel 2: open failed: administratively prohibited: open
failed". I tracked this down to some ssh tunneling problems but the
only solution I found was adding AllowTcpForwarding to the sshd_config,
which I did, but the problem still exists.</font><br><font face="sans-serif" size="2">Even trying to connect from one Linux
machine to another fails, I get the same errors. The only way I could ever
get a connection to work was connecting locally with encrypt all traffic
disabled.</font><br><font face="sans-serif" size="2">To be honest I am absolutely out of
ideas where to search and what to try, so if anyone of you got a suggestion
- that would be awesome!</font><br><br><font face="sans-serif" size="2">Finally some versions:</font><br><font face="sans-serif" size="2">RedHat Enterprise Linux 5</font><br><font face="sans-serif" size="2">Freenx-server 0.7.3-11.el5</font><br>
<font face="sans-serif" size="2">NXClient 3.3.0</font><br><br><font face="sans-serif" size="2">Thanks in advance,</font><br><font face="sans-serif" size="2">Mathis Schmieder</font><font face="sans-serif"><font color="#808080" face="sans-serif, Arial, Helvetica" size="-1"><br>
If you are not the intended addressee, please inform us immediately that you have received this e-mail in error, and delete it. We thank you for your cooperation.
<br>
</font></font><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></blockquote></div><br>