As you've probably figured out by now, VNC connections by default use another X display, rather than using the native display, or the one you see when physically using the computer. This can be quite an annoyance if you were working on the computer before remoting into it and you want to resume with the applications you had opened on the computer itself. One of the easiest ways to remote into the native display is to use the x0vncserver instead of vncserver, which we'll discuss next. Another option that's more embracive but provides for better performance is using the vnc.so module.
One of the easiest ways to remote into the native display is to use the x0vncserver instead of vncserver. From the terminal you can type x0vncserver password=YOURPASSWORD SecurityTypes=none. This will start hosting the display 0 for remote connections, protected by the password you choose. Use a VNC viewer like discussed in the previous part, however you don't have to include a display number with the IP address.
We discussed how to use remote desktop connections between Linux and Windows. We also configured our firewalls to let the traffic flow and our router to forward the traffic onto the host computer. Plus we figured out how to secure the VNC connections that pass through the Internet. Lastly we discovered how to remote into the native X display, to see exactly what is shown on the computer rather than a virtual display.
For documentation on the Linux components, remember you can use the manual pages by running the following in Terminal:
Also, don't forget to review the FAQ and support pages on the website of the particular developer.
Eric Geier is an author of many computing and networking books, including Home Networking All-in-One Desk Reference For Dummies (Wiley 2008) and 100 Things You Need to Know about Microsoft Windows Vista (Que 2007).
This article was first published on LinuxPlanet.com.