1. Enable XDMCP
then find this rule:
# The greeter for xdmcp logins, usually you want a less graphically intensive
# greeter here so it's better to leave this with gdmlogin
# RemoteGreeter=/usr/lib/gdm/gdmlogin
remove the '#' in the last line so there should be:
# The greeter for xdmcp logins, usually you want a less graphically intensive
# greeter here so it's better to leave this with gdmlogin
RemoteGreeter=/usr/lib/gdm/gdmlogin
Note: Before doing the next step, you need to make sure the extra repositories (e.g. universe) are enabled:
http://easylinux.info/wiki/Ubuntu#Ho...a_repositories
2. Install required packages (vncserver and xinetd)
Code:
Note to AMD64 users: The current version of vnc4server in the repositories has a bug, so you need to download and install the fixed vnc4 packages as shown below:
Code:
3. Set the VNC passwd
Code:
4. Add vnc service to xinetd:
Code:
Enter this into the new file:
Code:
5. Restart xinetd (usually there is no need to reboot, but occasionally it might be required)
Code:
6. That's it! To test that this is working first try to connect from the same machine (the machine we just set up the VNC server on):
Code:
You should be prompted for the VNC password, and then see the GDM login screen where you can login and start a new X session. If that works, you can now go ahead and try to connect from remote machine using your favorite VNC client (remember to first close the local vncviewer we started above). Remember to use the VNC server machine's domain name or IP address, followed by :1 (e.g. 192.168.0.100:1). If connecting locally as shown above works, but connecting remotely fails, then this means you have a problem with a firewall which is blocking some ports. See the notes below about how to deal with that.
Note about ports: The VNC server set up as shown uses TCP port 5901. If you are using firewall software (e.g. firestarter) on that machine, you need to allow incoming connections on this port. If you are using a router which assigns your machine a private address (e.g. 192.168.0.100) which is not accessible from the internet, then you need to forward TCP port 5901 from the router to this machine.
Note about security: This setup allows any user to start an X-session remotely by logging in using his regular password (after starting the VNC connection using the VNC password), so if the user disconnects without logging out, any other user which knows the VNC password can connect afterwards and resume the same session that the first user started. So if you do not want to log out before disconnecting, it's advisable to at least lock your VNC X-session screen. Also note that while a remote user is connected thru VNC, no other connection will be accepted. An idle VNC client will be disconnected after one hour, but this can be changed by using the "-IdleTimeout" option in the server_args line in /etc/xinetd.d/Xvnc. For example, you can add "-IdleTimeout 300" to change it to 5 minutes.
ps. This was copy/pasted from a few posts made by Tichondrius and elemental666. I simply putted them together and tested everything! It works here for me now.
additional :
enable remote login
system -> administration -> login Window
remote tab
choose "same as local"
problem:
get mine working
when I do: "vncviewer localhost:1"
I get:
vncviewer: ConnectToTcpAddr: connect: Connection refused
Unable to connect to VNC server
resolution:
System->Administration->Login Window
Click on Remote Tab
Changed style to "Same as Local"
Click on the "Configure XDMCP..." buton
Uncheck "Honor indirect request"
Click Close on both windows