Trying to setup FreeNX

I've installed FreeNX server (SuSE version) and the NX client from
NoMachine, but I still can't get them to agree to talk to each other.
I'd like to use Vahis' no doubt excellent setup guide on his website,
but it's written in Finnish, a language not yet catered for by
BabelFish. Riikka, a nice lady at work, could probably translate it for
me, but I won't be seeing her again until Thursday, and I'd like to
start playing now ;)

Below is a copy of the failure as recorded by my NX client trying to
link to the server on localhost. And yes, I have copied the server's DSA
key to the client.

NX> 203 NXSSH running with pid: 12943
NX> 285 Enabling check on switch command
NX> 285 Enabling skip of SSH config files
NX> 285 Setting the preferred NX options
NX> 200 Connected to address: 127.0.0.1 on port: 22
NX> 202 Authenticating user: nx
NX> 208 Using auth method: publickey
HELLO NXSERVER - Version 1.4.0-44 OS (GPL)
NX> 105 hello NXCLIENT - Version 1.4.0
NX> 134 Accepted protocol: 1.4.0
NX> 105 SET SHELL_MODE SHELL
NX> 105 SET AUTH_MODE PASSWORD
NX> 105 login
NX> 101 User: bob
NX> 102 Password:
NX> 103 Welcome to: bhf user: bob
NX> 105 listsession --user="bob" --status="suspended,running"
--geometry="1280x1024x24+render" --type="unix-kde"
NX> 127 Sessions list of user 'bob' for reconnect:

Display Type Session ID Options Depth
Screen Status Session Name
------- ---------------- -------------------------------- -------- -----
-------------- ----------- ------------------------------


NX> 148 Server capacity: not reached for user: bob
NX> 105 startsession --link="adsl" --backingstore="1" --nodelay="1"
--encryption="1" --cache="8M" --images="32M" --media="0" --session="New"
--type="unix-kde" --cookie="******" --geometry="1280x977"
--kbtype="pc102/gb" --screeninfo="1280x977x24+render"

NX> 1000 NXNODE - Version 1.4.0-44 OS (GPL)
NX> 700 Session id: bhf-1000-C581AC6B41D28313AA41E6DB49B3B735
NX> 705 Session display: 1000
NX> 703 Session type: unix-kde
NX> 701 Proxy cookie: 5337d2b16529945be04e16c4f39aaa09
NX> 702 Proxy IP: 127.0.0.1
NX> 706 Agent cookie: 1da79e865f1a195c971e1399ddb20e74
NX> 704 Session cache: unix-kde
NX> 707 SSL tunneling: 1
NX> 105 /usr/bin/nxserver: line 880: 13107 Terminated (
sleep $AGENT_STARTUP_TIMEOUT; exit 1 )
NX> 504 Session startup failed.
NX> 1004 Error: nxagent failed to start with: Unrecognized option: 1
NX> 1001 Bye.
Killed by signal 15.

Can anyone debug the above, and advise where I might have gone wrong,
please?
--
Bob

SuSE Linux 10.1, KDE 3.5.1
.

Relevant Pages

  • Re: help on caller credentials !! :-(
    ... I am runing my client application under user BOB on an Windows 2000 ... machine Then my server component is hosted in a windows service ... under windows 2000 and prefer mode should be "Impersonate". ...
    (microsoft.public.dotnet.security)
  • Re: SSL/TLS & renegotiation and Internet Explorer
    ... When IE closes the connection with the server and prompts the user to choose ... recovery logic the SSL session is discarded. ... If the user only has one suitable client certificate, ...
    (microsoft.public.security)
  • Re: RDP Printing by station
    ... flagged as non-printing stations can not print for ANY users. ... multiple NIC's on the terminal server. ... I'd then just have to ensure that the client stations that are ... session is limited to NIC # 1. ...
    (microsoft.public.windows.terminal_services)
  • SSL and IPS (was RE: ssh and ids)
    ... How many simultaneous SSL sessions can be tracked?" ... I assume you're talking about a case in which the client constantly ... If you walk the possible session id space and ... The server chooses the session ID, ...
    (Focus-IDS)
  • Re: Problems logging on to Windows Based Server.
    ... This problem occurs because the Windows 2000-based server rejects your logon ... structure that is used to track the logon session. ... The client attempts to ... This problem does not occur in conjunction with Microsoft Windows NT-based ...
    (microsoft.public.security)