Freenx setup guide

Info: Using pack method '16m-jpeg-7' with session 'unix-gnome'. Info: No suitable cache file found. Info: Listening for font server connections on port ''.

Session: Session started at 'Mon Oct 1 '. Info: Established X server connection. Session: Terminating session at 'Mon Oct 1 '. Info: End of NX transport requested by signal '15'. Info: Waiting the cleanup timeout to complete. Info: Shutting down the NX transport. Warning: Parent process appears to be dead. Exiting watchdog. I can not confirm these instructions, particularly the server installation, will work on Gusty.

I have not tried this, nor has anyone reported a successful or unsuccessful result. I dont think the client would cause any problems, since its distributed for multiple architectures. I wish I had a better answer for you. Youve got to give me more info that that. Usually its an ssh problem.

Can you connect via ssh from the command line from different locations?? At what stage in the login process is everything choking?? Again not meaning any insults but: 1. Check that port 22 on the router if you use one is forwared to your machine. Turn off firestarter or flush the Iptables on the server for now. Can add them back in once things are working 3.

Make sure openssh server is running probably is 4. From remote locations can you telnet to port 22 or ssh into the server? If you can not, it specifically at this point is not a FreeNx server since it needs to set up an ssh connection first before starting the client visualization package. Hi all, I finally got everything setup with my NX server to where I am able to connect, but once the client connects and opens up, it will promptly crash while trying to open x windows I believe.

The authentication goes through and I am able to SSH with putty just fine. Any suggestions on why it is crashing at the graphical portion of loading? Ive seen this behaivor on my machine before -- which makes me think freenx is somewhat unstable. You need to clean out all the old session variables on both server and client. I cant exactly remember where these are located right now but they are prefaced with C or S and then a big long number.

When I get back to the buntu box I will have to check. This is the only thing that really ticks me off with FreeNx. If you can point me to the files to delete that would be great, I haven't actually been able to get with it for the first time yet, so would I still have those files? Hmm, no those files will not be there since you never have established a session. For test purposes when I set it up, I simply connected from localhost to the server.

I kept getting a bunch of problems getting the X server to start, so hence in my tutorial the problems with the font settings which eventually solved the problem for me.

Definitely check the font path. With the server settings there is a way to set the log level to log nearly everything about the connection. I would definitely up the log level and make sure you consult these, since these eventually gave me hints that I was having a font problem after hours of taking the information in the logs and looking on the internet.

If you're trying to connect to your machine from somewhere else on the internet, you need to use your public IP. If that works, then you can try NX. Definitely check the font patll h. I can't seem to find any issues with the logs from what I can tell. I am using the nomachine windows xp client btw. Below is a copy of my logs. What do all the parameters like "geometry" etc stand for at the beginning? Can you bump up the log level???

Im not sure why its not working with you. Geometry has to do with the Xserver -- its normal and you shouldnt have to really mess with those settings. Where do I bump up the log level? Not real familiar witih where to do that. What level should I set it to? Ive heard rumors that the name of the conf file has changed. I had set it to 6 before I just remembered, but I am still getting the same output. Do you have any old sessions that are stored or are trying to resume a session??

As you can see Im not offering much advice since I dont know anything right now. I would manually delete this file or any such files that look like this.

Before connecting from your windows XP client, you have confirmed that you can connect from localhost first?? And I dont mean to be redundant but youve modified your iptables possibly through firestarter to open port 22 on the server?? I have decided to wipe a clean slate and try 7. I will then try nxserver from there. I think the root of my problem is something with my graphics as I had done some modificaiton to try and get Beryl working.

I will update you with what is going on! It could be -- like I stated so many times I had a problem with the fonts -- who would have thought that would have crashed the nxserver -- but it had something to do with tunneling the X session throught ssh to the client.

Im no expert on the X windowing system, so it took me hours to troubleshoot. In fact on your new install, immediately make a backup copy of the xorg. I think likely that is the culprit in your case, as you now remind me about beryl, compiz. I also am having troubles with setting up freenx server on both my laptop and server. Both are running amd64 cpus The laptop is single core and the server is X2.

Both of them stop at the same place when setting up the session. I can connect to my computer running the i edition of ubuntu, but these 64bit editions don't seem to work.

Do I need to install the version 3. The server log is here. The key entry is localhost that I'm trying to log into. Xauthority nextract - Can you deactivate all firewalls or at least open all ports on the client computer for testing purposes. Update for all. I have found that freenx server and the nomachine client past 2. I downloaded the 1. I ended up switching over to Nomachine's free server, but am having issues with logging in a second time after disconnecting. I believe i will switch back to freenx and the 1.

I encountered exactly the same trouble. In my environment, this workaround solved the problem. Im glad you guys have figured out the problem with the font paths, that was one of the problems I had way back in the original post. Is there anything that might be helpful to add to the original instructions that would help other users avoid this problem?? Hello, I'm trying to login to my gutsy server with the 1. Info: Not using NX delta compression. Info: Using pack method '16m-jpeg-9' with session 'unix-gnome'.

Info: Not using persistent cache. Info: Starting X protocol compression. Info: Using shared memory support in X server. Error: Lost connection to peer proxy on FD 8. Error: Connection with remote peer broken. Error: Please check the state of your network and retry. Can you briefly summarize what the solution was? Was it the font path? I have posted updated packages for Gutsy at the location mentioned above.

From the trouble I was having from an earlier post I gave up on the Seveas repos since they are still using an outdated package setup. Why use nxclient 1. Debian is the only Linux flavor this far behind sadly. I believe the title of the HowTo is labeled how to use seveas repositories on the Feisty -- not Nomachine's client on Gutsy.

I am sure there are better ways now of setting up freenx, however I was trying to recommend a way that used software that was not as restrictive as NoMachine's. I am not using any of NoMachine's commercial software on the forum except the client, which although commercial it is still free to use but not open source.

I am actually using freenx 0. All open source and free as in freedom. I do not have a repo yet, but I wouldn't mind someone offering to host the packages. Also, if you would like, I can offer up the sources and diffs for someone to compile I do not have Feisty anymore so that everyone here can update their feisty version as well.

Finally, I apologize if my post sounded condescending to your brilliant efforts to assist the community I have read most of the posts as you have done an excellent job, but I was just stating the fact that we in the Ubuntu Linux world are way behind and it's time to catch up. I do not mean to disrespect anyone.

Thanks for your edition to FreeNx -- anyone using FreeNx I would point them to your post as it is updated compared to mine. That is kind of the nature of Debian in general. I will try to install freenx server and client according to your instructions. Thanks for the updated instructions. I'm glad at least someone in the community provides updates to proposed solutions that worked in the past, but due to improvements may not be applicable for today's versions.

I currently connect to the computer name, but that doesn't work on the internet, I'm assuming? I can currently use the clipboard across computers, but not files. Thanks for a great howto! EDIT: I'm using Gutsy 64 bit on both server and client, and had to fiddle around with some stuff to get it working. For this two work, if you are behind a router, your computer should be assigned an IP address, the ssh port from the router needs to be forwarded to the server, and the iptables firewall modified using firestarter, guarddog, or manually to allow inbound connections.

I only can think of using scp. The easiest way I have found to copy files is to make an ssh connection directly with the Nautilus file browser. Open Nautilus, and if it's set to show individual buttons for each directory at the top of the window then you have to change to address mode. It will make the connection and prompt for your username and password. You can also use Places Connect To Server to create an SSH connection that will create an icon on your desktop for easy use in the future.

Thanks for that! I managed to SSH into it. This should get freenx installed. Adapt the following line to your release and add it to your sources. Update the list of available packages from the apt sources and install the FreeNX server. You can check if the server is running. NoMachine provides also an client and the Debian packages. NoMachine NX Client 2. No machine has posted installation instructions under [4].

NOTE: the links above are no longer being maintained. Select OK and you are all set. You should now be able to connect to the Server machine and open your desktop from the client. Installation of NoMachine's nxclient NoMachine does not allow the distribution of their client, so it must be downloaded from their website. Note: The 3. Pick the client for your OS and install it on your OS per the instructions on the No Machine site, then use the below instructions to connect to your NX server.

Open the NX Connection Wizard. Do not check the disable encryption box if you want SSL encryption. This means only the SSL port needs to be open to inbound traffic if you are connecting from outside a firewall. Please see NoMachine Support for more information. This problem seems to be known as the "backingstore" problem. This issue is now fixed in the 0. Which can be found in the Extras Repository. It should no longer be an issue, however we will leave the information as a reference for people still using the older versions.

Problem arouse as you try to connect to a 0. As Nomachine changed the behaviour of the backingstore-option. You can read all his message here: Backingstore or 2.

Disabling DirectDraw in the NX client is reported to fix the problem. Remove all.