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

[Chris Duncan]

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.

At first, I thought that there was a problem with my nxserver setup on
my SUSE 9.3 box in my home network. I searched the Nomachine knowledge
base and FreeNX forums and the popular suggestion seemed to be to
include the line -

ENABLE_1_5_0_BACKEND="1"

in the node.cfg file on the server. I did this but still got the same
error in the client session log which was -

Info: Proxy running in client mode with pid '536611'
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

To check whether the problem was with my server configuration I got an
account on the Nomachine testdrive server in Italy and tried to
connect from my Windows Me machine. It still did not work and gave me
a similar error.

I then tried to connect to the testdrive server from my Suse 9.3 box
using the Nomachine client for Linux with the "Enable SSL encryption
of all traffic" option and it worked with no problems.

These tests lead me to believe that the configuration of the NX Client
on my Windows Me box is where the problem lies. The output in one of
the failed session files on my Suse 9.3 server from the user's .nx
directory is as follows -

NXAGENT - Version 1.5.0

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

Info: Agent running with pid '26612'.
nxagentProcessOptionsFile: Option file is
[/home/jessica/.nx/C-linux-1009-8BD5D902DA5BA1BED7106E9CCAA3B2EB/options].
nxagentProcessOptionsFile: Option file is 215 bytes long.
nxagentParseOptionString: Warning ignored option 'cache' = '1M'.
nxagentParseOptionString: Warning ignored option 'images' = '0M'.
nxagentParseOptionString: Warning ignored option 'link' = 'modem'.
nxagentParseOptionString: Warning ignored option 'type' = 'unix-kde'.
nxagentParseOptionString: Warning ignored option 'cleanup' = '0'.
nxagentParseOptionString: Warning ignored option 'accept' = '127.0.0.1'.
nxagentParseOptionString: Warning ignored option 'cookie' =
'993889041543C5D74E59D59B9FA295FE'.
nxagentParseOptionString: Warning ignored option 'nodelay' = '1'.
nxagentParseOptionString: Warning ignored option 'keybd' = '1'.
Info: Proxy running in server mode with pid '26612'.
Info: Waiting for connection from '127.0.0.1' on port '5009'.
Info: Accepted connection from '127.0.0.1' on port '16344'.
Info: Connection with remote proxy established.
Info: Aborting the procedure due to signal '15', 'SIGTERM'.

Fatal server error:
NXAGENT: Fatal IO error on display
"nx/nx,options=/home/jessica/.nx/C-linux-1009-8BD5D902DA5BA1BED7106E9CCAA3B2EB/options:1009".

This output is from the Nomachine nxserver, but the same problem
occurs when I use the FreeNX nxserver.

Can anyone please tell me what the problem is or at least get me
moving in the right direction towards a solution? I have run out of
ideas!

--
Regards

Chris