I can no longer make client connections (neither from home/ubuntu nor from localhost) to nxserver on . The gripe is “no subscription information found on server”" but the server.lic (chmod=400) and is clearly the perpetual free 2-user license. Authentication completes successfully. From the “details” window:
NX> 148 Server capacity: not reached for user: rsargent
NX> 105 Start session with: --link=“lan” --backingstore=“1” --encryption=“1” --cache=“16M” --images=“64M” --shmem=“1” --shpix=“1” --strict=“0” --composite=“1” --media=“0” --session=“local” --type=“unix-gnome” --geometry=“3360x1024” --client=“linux” --keyboard=“pc102\057us” --screeninfo=“3360x1024x24+render”
NXSERVER - Version 3.4.0-8 - LFE
Fri Sep 3 08:21:05 2010 running as user: ‘nx’ (uid: 110, pid: 3262) on ‘am-rjs’
Info: user login is rsargent (NXShell)
Info: user password is ‘******’ (NXShell)
Info: using ‘sshd authentication’ (NXShell)
Info: selected user ‘rsargent’ is authenticated (NXNodeExec)
Info: password for selected user is in ‘text’ mode (NXNodeExec)
Info: preferred auth method is ‘’ (NXNodeExec)
Info: selected NX Node with host name ‘localhost’, port ‘22’ (NXNodeExec)
Info: selected publickey method to login NX Node (NXNodeExec)
Info: nxssh command line is ‘/usr/NX/bin/nxssh -nxservermode -l rsargent localhost -p 22 -x -2 -i /usr/NX/etc/keys/node.localhost.id_dsa -o ‘PubkeyAuthentication yes’ -o ‘RSAAuthentication yes’ -o ‘RhostsAuthentication no’ -o ‘PasswordAuthentication no’ -o ‘RhostsRSAAuthentication no’ -o ‘StrictHostKeyChecking no’ /usr/NX/bin/nxnode’ (NXNodeExec)
Info: nxssh child pid is: 3298 (NXNodeExec)
Info: received data in out channel from NX Node: 'NX> 611 No subscription information found. Please visit the
NX> 611 NoMachine web site at NoMachine NX - Desktop Virtualization and Remote Access Management Software
NX> 611 to acquire a valid subscription.
NX> 611 The NX node can’t perform the requested operation.
’ (NXNodeExec)
Info: NX Node out channel was closed (NXNodeExec)
Info: NX Node err channel was closed (NXNodeExec)
Info: closing nxssh’s in, out, err FDs (flagfinished is: 0) (NXNodeExec)
Error: no ‘CONNECTED’ message from NX Node (NXNodeExec)
NX> 280 Exiting on signal: 15
Linux am-rjs 2.6.31.12-0.2-desktop #1 SMP PREEMPT 2010-03-16 21:25:39 +0100 x86_64 x86_64 x86_64 GNU/Linux
openSUSE 11.2 (x86_64)
VERSION = 11.2
There might be something broken indeed. I use both (nomachine and freenx) with different Linux distros, but on openSUSE 11.3 (it was OK under 11.2), I wasn’t able to make any connection either. The only solution I found was to uninstall all nomachine packages (except the client) and use FreeNX only (it is better anyway).
Ah ha. Installed 3.4.0-14 on my ubuntu10.4 “server” and connected just fine from my laptop. Tunnelled in to work, and with the magic of rpm and wget install this same version on my Suse desktop and am now re-connected. (Maybe even have my control/caps-lock swap respected? That would be too much to expect.)
But this version doesn’t work either. The one I use is version 0.7.3-5.1 but I don’t remember from where I got it … maybe from Mandriva.
Unfortunately I have some trouble with that one too (on a new install, works on some other machines under 11.3). I constantly have problems with NX, solve them after a while and forget how. I might start a thread about it pretty soon.
The nice thing with FreeNX (when it works) is that you can have an unlimited number of connections and it can forward connections on another port to a nomachine server (which will accept only one in its free version)
# FreeNX with ENABLE_NOMACHINE_FORWARD_PORT="1" will automatically forward all
# connections to the commercial NoMachine nxserver installed on the same
# machine, which go in by port NOMACHINE_FORWARD_PORT. This feature is introduced
# to enable the usage of FreeNX and NoMachine NX side by side on the same machine
# without conflicts.
#
# Note: You need to let SSHD listen to several ports to make use of this
# directive.
ENABLE_NOMACHINE_FORWARD_PORT="1"
NOMACHINE_FORWARD_PORT="9123"
NOMACHINE_SERVER="/usr/NX/bin/nxserver"
NOMACHINE_NX_HOME_DIR="/usr/NX/home/nx"
Interesting! How did you fix it? Strange thing in my case: nxserver 3.4.0.14 works just fine on OpenSuse 11.2. I can log on from 11.3 (nxclient 3.4.0.7) without any problem, but the other way around does just not work (client 11.2 -> server 11.3). Relevant packages/configs should be the same on both systems.
Hello, I think I am having the same problem (nxclient 3.4.0.7,node 3.4.014,server 3.4.014): 1 laptop with o.S.11.2, the other with 11.3.
The connection 11.3>11.2 can be established, vice versa 11.2>11.3 not.
E.K.
Hello, I am back, may be it’s helpful: i am running both machines with Win XP7 and I just tried to connect from Win NXclient to o.S. server:
it worked from Win (with o.S.11.3) to server on o.S.11.2.; it did not connect from Win (with 11.2 ) to server on o.S.11.3.
The info about the failure by NX menu exactlty the as above: fatal error occured on NX server.
Sopmething to do with o.S.11.3 ?
Confirmed:sshd status on both machines running. In addtion I checked fish and sftp in both directions : everything o.k
E.K.
After a lot of unsuccessful tweaking in the configuration files I finally gave up. Whatever the reason is, I just do not have the time to play around for days. Anyway, I thought I would give ‘freenx’ a try. So I removed the nomachine nxserver (I kept the client since it worked out of the box) and installed freenx available from opensuse repositories. I had to create the missing directory for cups (on 64bit systems), and just to be sure I added the md5sum command in node.cfg (both issues are described here: SDB:FreeNX server - openSUSE). Then, everything worked out of the box! Just for tradition and because it already worked I keep the nomachine nxserver on the 11.2 system.
While in this case it is surely not Opensuse’s fault, I, myself using Suse since 7.3, would in general very much like to see more bug fixes for issues known for years instead of throwing a new, nowadays less properly tested, distribution on the market every half a year.