Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

My shop has been using the FreeNX server on Fedora 11 for a while now and mostly getting good results, especially with performance, but we have some annoying problems with client connections. There are two main issues:

  1. Client sessions sometimes freeze after a long time (seems to be at least 2 hours of having the session active)
  2. We often have to make multiple attempts to start a new client session, especially if a previous session was suspended rather than terminated. In qwuite a few cases, we've had to restart the NX server to get around this.

Our NX server configuration is the default except that we've enabled logging level 7 to /var/log/nxserver.log, and set the font server to "unix:/7100" so that it uses xfs.

Does anyone have any ideas for making things more stable ?

share|improve this question
I've had weird issues with NX as well. I went back to regular ssh X forwarding, and haven't bothered with NX since. – Ignacio Vazquez-Abrams Apr 9 '10 at 22:54
@Ignacio: were your 'NX' problems 'FreeNX' or 'NoMachine NX' problems? – Kurt Pfeifle Aug 6 '10 at 22:37
pipitas they were !M problems, as in certain keys would be mismapped, and the client would crash when switching workspaces. – Ignacio Vazquez-Abrams Aug 8 '10 at 17:17

I'd suggest using neatx as FreeNX tends to be unstable and is less actively maintained.

share|improve this answer

I would recommend moving to a newer, or at least better supported, distribution.

At this point (March '11) the "current" Fedora Core is 14, 11 is somewhat dated.

We run the FreeNX server on CentOS 5.x with good success. Yes, this base is also dated ('06 or '07) but RedHat is more actively porting fixes to this distribution.

share|improve this answer

It might be caused by the NX client, which client are you using ?

If you use the nomachine client, it might cause problems since you also use the freenx server, which isn't as up-to-date as the nomachine NX server. Maybe a rollback of the client to a know working version could help ?

share|improve this answer

I would like it noted that I haven't noticed any of these issues with the commercial nx server or client. Freenx on the other hand has had numerous issues, and neatx although a good alternative had some annoying quirks as well. If its a production machine it might be worth going the commercial route on this one.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.