I recently pulled my hair out for a couple of hours on a problem that was really simple…I just was overlooking a setting. To help other people save time on this exercise I wanted to share my experience.

I have OpenSuSE 11.1 virtual machine. I installed the NXServer on that machine so that I could control it from my Mac laptop and Windows 7 Desktop. I needed to change the ports to allow me to communicate from outside of my home. In order to do this, I knew that I needed to change my SSH port as well as my NX Server port.

Here is what you have to do:

• Edit your sshd_config file
  Edit the /etc/ssh/sshd_config file changing the line that says “Port 22″ to “Port {your_number}”
• Edit your ssh_config file (Please note, you’ll only want to do this step if you are controlling the port your client on this machine will always look for in a connection) –
  Edit the /etc/ssh/ssh_config file by changing the line that says “Port 22″ to “Port {your_number}”
• Edit your server.cfg file
  1. Edit the /usr/NX/etc/server.cfg file by changing TWO lines. This is where I messed up and had a hard time figuring out my problem.
  2. The first line you need to edit is: ‘#SSHDPort = “22″.’ You need to change that to (first, remove the # sign to make it active instead of being a comment): ‘SSHDPort = “{your_number}”.’
  3. The second line you need to edit is: ‘#SSHDAuthPort = “22″.’ You need to change that to (first, remove the # sign to make it active instead of being a comment): ‘SSHDAuthPort = “{your_number}”.’ If you don’t change this line, your NX Client will give a error saying: “Authentication failed for user {username}”.
• Edit your node.cfg file
  Next, edit your /usr/NX/etc/node.cfg file by changing one line: ‘#SSHDPort = “22″.’ You need to change that to (first, remove the # sign to make it active instead of being a comment): ‘SSHDPort = “{your_number}”.’

• Restart your Services
  Restart SSH by issuing the following Command: “/etc/init.d/sshd restart”
  Restart the NX Server by issuing the following Command: “/etc/init.d/nxserver restart”

There you have it. You should be able to connect via a non-standard, non-default port with the nxclient.

find $directory_to_clean -mtime +$days_old -exec rm {} ;

This bash command will look in the $directory_to_clean location and delete all files that are $days_old old.

If you are paranoid about the command and want to try it out first, use this one:

find $directory_to_clean -mtime +$days_old -exec ls -l {} ;

That command will list all the files instead of delete them.

Well, throw directory commitment out the door with Linux’s built-in tools, pushd and popd.

Lets say you are in directory x, but you need to do a few things in directory y in order to then complete your tasks in directory x. Simply, type in “pushd y”. Now you are in directory y. Stay a little while and do what you needed to do. Have your fun, but when it is time to get out and you want to be back with x, simply type “popd”. You’re back with x in no time.

With these tools you are simply pushing a directory onto a stack of directories. When you call the popd command, you just pop the current directory off the stack and return to the previous one. Easy!

Note: It is hazardous to your help to implement these tools in your own personal life – I recommend you only use these with directories – not people.

Screen lets you multiplex between console sessions.

Here are the commands I use the most:

screen -S —> lets you create a terminal session that is viewable when you ssh into the machine from somewhere else

screen -dr —-> detaches the other terminal from the screen session with that name and gives it to you

screen -x —-> lets you share the other terminal with the others using that same screen session.

2. Open up a cygwin shell and ssh into the remote device (R1)

3. Open up another cygwin shell on the host (H1) and run startx

4. Open up another cygwin shell on the host (H2) and run “xhost +”

5. On R1 set the environment variable DISPLAY to be the IP address and display number

• eg. export DISPLAY=151.155.171.31:0.0

6. Run the x-based program on the remote device.

SLES10 does a remote desktop feature built in, but it does not let you share the desktop across different computers. This scenario fixed it for me.