Installing FreeNX 2.0 on SuSE Linux
If you have tried to install FreeNX on SuSE Linux recently you may of had some trouble. This because on the 22 of June, NoMachine released an updated NX suite. SuSE 10.0 and 10.1 shipped with an older version of the NX Server. As a result, you cannot use the 1.5 NX Server that ships with SuSE Linux and the 2.0 NX Client . Instead, you should download the latest RPM’s from the NoMachine website. If you do not know what NX is all about then here is the description from their website:
NoMachine NX is a Terminal Server and Remote Access solution based on a comprising set of enterprise class open source technologies. Thanks to the outstanding compression, session resilience and resource management developed on top of the X-Window system, and the integration with the powerful audio, printing and resource sharing capabilities of the Unix world, NoMachine NX makes it possible to run any graphical application on any operating system across any network connection as if you were sitting in front of your computer.
All 3 of the following packages must be installed on the machine you wish to be the server. for any client machines, you need only install the NX Client.
Upgrading from NX 1.4 or 1.5
If you are upgrading your current NX Server to version 2.x from version 1.4 or 1.5, then you must completely uninstall NX from your machine before you proceed. I removed my current NX packages by opening Smart, searching for NX, and telling it to remove ‘NX’ and ‘freenx’, if I remember the package names correctly. Once they were removed, I deleted my ‘.nx’ directory in the home directory of my NX server machine. I then rebooted, not because I had too, but because I was too lazy look for a running service or other obstacles to proceeding. Once my server was rebooted, I proceeded with the following instructions without any hassle.
Installing NX for the First Time
If this is your first time installing NX server, you can simply open a root console, then change to the directory where the above packages were downloaded (most likely your users home directory) and install them with the following command:
rpm -Uvh nx*.rpm
This will install the NX Server, NX Node, and NX Client. The last thing you see before being returned to prompt should be something along the lines of:
NX> 700 Bye.
If this is the case, you are ready to install NX Client on your client machines and attempt to connect to the server. There used to be a setup command that you ran after installing the server. It would appear that this is all handled at the end of the RPM’s install script.
Running NX Client
After installing the NX Client on a Linux box running KDE, you can find the shortcuts for it here:
KMenu -> Internet -> NX Client for Linux
Put in the IP of the machine acting as the NX Server and attempt to make a connection. If this works, you are done. If it was unable to connect, then there is still some work to be done. As things went smoothly for me, It is hard to know what issues you might have. Be sure that If you are running the SuSE Firewall, and you are unless you specifically turned it off, you need to be sure that you poked a hole in it allowing SSH traffic.


Note that if you run NIS on the nx server machine, you will need to turn NIS off prior to installing nxserver. You can reenable NIS after install. If you don’t do this, the nxserver install script will complain about existing nx user and fail.
Also note for those going from nx 1.5 to 2.0, that the config is now in /usr/NX/etc instead on in /etc/nxserver. And if you use custom sshd ports on your machine, you will need to edit both node.cfg and server.cfg
Regards,
Mark
Any experience with running the NX client on Windows, and connecting to Suse? I have version 2 client and server, and SLES 10. I can successfully connect to localhost using the client on Suse, but the Windows client continually times out. I can ssh into the suse box from the windows box using putty. Where does one begin to troublshoot the windows client?
I’ve had no problems using the Windows client to connect to a SLES 9 server. Since NX sends quite a few packets to the client, there is more possibility for timeouts. I would ensure that your security software isn’t getting in the way, and that your ethernet port isn’t extremely busy if your having timeout problems.
Greetings - just wanted to share that i disabled the zen updater by Novell and now my computer is at idle within a min and a half after start up. Before with the zen on it would be busy for approx 10 - 20 min. I’m running a t22 thinkpad with 900 PIII and 256 ram.OpenSUSE runs sweet on here. don’t have video player working yet but not impossible i think, this is my first use of linux and love it.