[FreeNX-kNX] Followup to Problem Connecting Windows Client to SuSE9.3FreeNX Server

[Alastair Johnson]

First step as always is to check the logs. Places to look on the server are:
/var/log/nxserver.log
pathto_users_home_dir/.nx/C_session_id/session and errors

The name of the session_id bit will change with each session, and by default 
will be removed when the session ends. To get it to stick around after the 
end of the session edit /etc/nxserver/node.conf and set SESSION_LOG_CLEAN=0
While you're there you may wish to increase the log level with NX_LOG_LEVEL=6 
or maybe even 7. If you don't have a node.conf just copy the sample and add 
the required settings.

With a bit of luck the logs should say why things aren't working, or give 
enough information for someone on the list to work it out. If all else fails 
and you're confortable with shell scripts, start looking at /usr/bin/nxnode. 
Echoing diagnostics to file, or redirecting stdout and/or stderr of a suspect 
tommand to file can get you a long way. 

On Tuesday 29 August 2006 17:15, Kaplan, Andrew H. wrote:
> Hi there -
>
>
>
> I was able to get to the Wiki website and made the suggested changes to the
> nxnode file. After the changes were made,
>
> I stopped and restarted the nxserver. When I try to connect now, I do get a
> connection, but the remote desktop does not
>
> appear. I did a ps -ef |grep nx on the Linux box and there are indeed
> daemons running that are associated with the connection.
>
>
>
> What are my next steps? Thanks.