NOTE: The method for accessing FreeNX in the Design Center has changed. The contents of this document have been updated to reflect that change. Please follow them carefully to be able to use the new, simplified configuration.
Date of last revision: 2/13/2007
FreeNX is a server that allows remote graphical access to Unix systems
in the Design Center in a secure and bandwidth efficient way. (It'll
even work over a modem)
FreeNX 0.6.0 help index:
- Currently available on all Linux workstations.
- Currently available on all Solaris workstations.
- Due to design limitations in the Windows OS, FreeNX server functionality is not available on Windows.
- Handheld Linux (Sharp Zaurus/HP iPaq)
On the machine from which you wish to connect (ie, your home computer) you'll need to download the appropriate NX client for either:
(You want the client to match the OS you're running on the computer you're connecting from, not the computer you're connecting to.)
Now install the client as you would any program on your client OS.
Running FreeNX 0.6.0
When starting up the NX client for the first time, you'll be entered into the setup wizard. The important settings are:
- Session - This is an arbitrary name you give to the session. Call it whatever you like. (Something like "SCUDC Linux" or "SCUDC Solaris" would be good)
- Host - This is the hostname of the OS you want to connect to.
For Linux, use "nx-linux.engr.scu.edu"
For Solaris, use "nx-sol.engr.scu.edu"
- Port - Leave this at the default of 22
- Type of Connection - Set this to modem, even if you're on a faster connection, to enable the highest level of compression.
- You can leave the defaults here if you're setting up a Linux connection. (Unix | KDE) You can also choose "Gnome" if that's your preference.
- If you're setting up a Solaris connection, change this to "Unix | CDE".
- Be sure to check "Enable SSL encryption of all traffic"
Now you're sitting at the NX session/login prompt.
- Be sure to check "Show the Advanced Configuration Dialog"
Click "Login" and you should be authenticated and see the graphical
environment you set up. (KDE by default) Use the system as you would if
you were sitting locally on a DC workstation.
- Login - Enter your Design Center username.
- Password - Enter your Design Center password.
- Session - Select the session you created previously.
Windows Clients - (Needs to be done only once)
- Start "NX Client for Windows"
- Select the appropriate session
- Click the "Configure..." button
- Select the "Environment" tab
- Check "Use font server"
- Set "Host" to "fontserver.engr.scu.edu"
- Set "Port" to "7100"
- Select the "About" tab
- Verify that you are running a version >= 1.5.0-138 (If not, upgrade now)
- Click the "Save" button
- Click the "Ok" button
- Log into NX as you normally would
Unix Clients - (Needs to be done each time you run nxclient)
- $ xset +fp tcp/fontserver.engr.scu.edu:7100
- $ xset fp rehash
- $ nxclient
- Log-in to NX normally
- Start a terminal in the NX session
- (Do normal mentor graphics stuff here)
- (Anything else you want to do in NX)
- Logout of NX
- $ xset fp default
- $ xset fp rehash
Suspending Sessions - It is currently possible to suspend your session by not logging out and just closing the NX window. This functionality will be disabled in future upgrades to FreeNX in the Design Center and suspended sessions will be subject to unnotified termination. Do NOT suspend sessions.
- When connecting,
any firewalling software you have running must allow the NX client to
make outbound connections. It is up to you to figure out how to
configure your firewall to do this. (Most pop-up a prompt when an
unknown program tries to initiate an outbound connection)
connecting to a host for the first time, you'll receive a message
beginning: "The authenticity of host..." click "Yes" as this is your
computer asking you if you want to trust the key you're getting from
the host. From then on, the host you're connecting to will only be
trusted if the key matches. Otherwise your system will assume there is
a man in the middle attack going on and refuse to connect. This is a
good thing as it ensures the cryptographic security of your connection.
- If you get a "Connection Error" message when connecting,
click the "Detail" button to see a log of errors. Some of the more
common ones are listed below:
NX> 105 /opt/freenx-0.6.0/bin/../sol2.9-sun4u-64/bin/nxserver: line 849: 3646 Terminated sleep $AGENT_STARTUP_TIMEOUT
NX> 596 Session startup failed.
You're trying to connect to a Solaris host and have a malformed ~/.cshrc file. The simplest solution is to login to your unix account using telnet or ssh and run the command:
$ mv ~/.cshrc ~/cshrc-backup
NX> 202 Authenticating user: nx
You've not correctly imported the SCUDC NX key. Please check the directions above.
Other Information Resources
Other Topics of Interest