Guides & Solutions (No Questions)Post your guides here (No links to Blogs accepted). You can also append your comments/questions to a guide, but don't start a new thread to ask a question. Use another forum for that.

With this approach, a VNC session will be created independent of console X session.
Can be used at init runlevel 3 or 5, means you don't have to run desktop at console. Very handy for server especially at remote location.

Install VNC-server

Code:

# yum install vnc-server

Configure VNC-server

I recommend running VNC-server as system service. Edit /etc/sysconfig/vncservers, the configuration file used by vncserver service.

specify hostname:1 to attach as user1 -or- hostname:2 to attach as user2

specify hostname:0 to connect to Vino. (See step 3 later)

When prompted, enter the vncpasswd, and you are set.

Good luck!

3. Install and configure Vino:

With this approach, client's vncviewer will attach to the running console X session at server.

Must be init runlevel 5 and login, and I think it only works for gnome. (???)

Installing vino

Code:

# yum install vino

Configure and start vino

Login console desktop, in your gnome-terminal, execute the following:

Code:

$ vino-preferences
[x] Allow other users to view your desktop
[x] Allow other users to control your desktop
When a user tries to view or control your desktop
[ ] Ask you for confirmation
[x] Require the user to enter this password
Password: xxxxxx

When "Close," vino will start a vnc session at port 5900, (firewall need to open port 5900). IMO, don't check "Ask you for confirmation", but use "password" option instead, unless you will be at console to answer "Y" when connecting remotely.

Follow Step 2 to install vncviewer.

To connect remotely, use vncviewer to open hostname:0

Do not use vncviewer within gnome session to connect to yourself, or you will have "nested" windows.

****F9 Gnome may need some fixing up in dbus configuration before it can be used. Edit /etc/dbus-1/system.d/gdm.conf , insert the 2 lines in red. Restart messagebus service (may kill gnome session), or simply reboot. gui response in Gnome may be a bit sluggish. Your mileage varies.

I always uses secure tunnel with TightVNC.
When using the java version, I noticed encryption is grayed out, pass that, and now see the colors looks funny. I see everything like you see in TightVNC.
Am I doing something wrong with encrytion or colors?

Last edited by marcrblevins; 12th July 2008 at 09:50 PM.
Reason: Show my appreciation of the guide.

Color palette is chosen based on network speed. Higher-bit colors are used for higher speed and vice versa. I get this low-bit color when accessing over a slow internet link. I think Java version just use lower-bit palette for some reason.

Perhaps RealVNC will have encrypt version for Java desktop in the future.