[FreeNX-kNX] Problem with Windows Me NX Client and SSL encryption

[Hans-Helmut Bühmann]

Chris Duncan <celldee at gmail.com> schrieb:

> I am having a recurring problem trying to connect to any nxserver
> machine from a laptop running Windows Me if I use the "Enable SSL
> encryption of all traffic" option on the Advanced configuration tab in
> the NX Client (version 1.5.0-106). I can connect when I do not have
> this option selected. I have also tried version 1.5.0-114, but with no
> success.
> 

Hello!

I have a similar problem. I'm using FreeNX 0.4.4 and libraries 1.5.0 as
delivered with SuSE 10. On one Windows XP the NX-Client 1.5.0-114 is working
as expected. So I belive, my problem is not related to the server. On the
other Windows Client I got the following error, using the option "Enable SSL
encryption of all traffic":

NXPROXY - Version 1.5.0

Copyright (C) 2001, 2005 NoMachine.
See http://www.nomachine.com/ for more information.

Info: Proxy running in client mode with pid '4760'.
Error: Failure negotiating the session in stage '7'.
Error: This means that we probably didn't provide a valid cookie.
Error: The remote NX proxy closed the connection.

In the sshlog also an error is displayed:

NX> 285 Identified internal connection
NX> 285 Using default mode encrypted
NX> 285 Identified options:
nx,options=/cygdrive/C/DOCUME~1/ADMINI~1/NX73F8~1/S-LINU~1/options:1000
NX> 285 Switching descriptors: 4 and: 5 to: 7
NX> 286 Failed to set TCP_NODELAY on descriptor: 4
NX> 286 Failed to set TCP_NODELAY on descriptor: 5

NX> 287 Redirected I/O to channel descriptors

Without enabling the option "Enable SSL encryption of all traffic" everything
works fine.

I also tried to enable "Disable no-delay on TCP connection", but this option
has no effect.

I have no solution for it, but this seems to be a NX-Client related problem.
Could you please check, weather you have the same error message into your
sshlog or not? May be, something has changed the
IP-Stack. Here a Zone Labs firewall is also installed.

Perhaps this this information may help to find the error, and I know,
nomachine.com ist reading here too ;-)

Greetings
Hans-Helmut