Install vnc server centos 5.6

Once authenticated, a x window should open using Larry's default window manager. The vncviewer client will connect to port X where X is an offset of 1,2,3 for Larry, Moe, and Curly respectively, so these ports must be open in the firewall for the IP addresses or subnets of the clients.

The following sections are optional refinements to enhance security and functionality. VNC encrypted through an ssh tunnel You will be connecting through an ssh tunnel. You will need to be able to ssh to a user on the machine. For this example, the user on the vncserver machine is: larry That account username needs to exist on the target machine, and either password, or keyed ssh access needs to be functional.

The Linux and VNC system usernames and passwords are not required to be identical and are 'not' automatically synchronized. That is, remote users able and baker may each have differing credentials to set up the ssh tunnel to the remote VNC server, but if each uses the larry account, they will use the same VNC password. If not, performance may be very poor!

Recovery from a logout Not implemented for CentOS 6 If you logout of your desktop manager, it is gone! We added a line to xstartup to give us an xterm where we can restart our window manager. For gnome, enter gnome-session.

For kde, enter startkde. Remote login with vnc-ltsp-config To allow remote login access via a vnc-client to the Centos system, the RPM packages named vnc-ltsp-config and xinetd can be installed. When a vnc-client connects to one of the configured ports, the user will be given a login screen. When a user logs out, the session is gone.

A major advantage of using the vnc-ltsp-config setup is the reduction of system resource utilization compared to the standard "per-user setup". No user processes will be started or memory consumed until a user actually logs into the system. Also, no pre-thought for user setup is needed eg skip all of the manual individual user setup for vnc-server.

Also, there is no session persistance! Once the vnc-client closes, the vnc-ltsp-config session will terminate by default and all running processes will be killed. This option can be combined with ssh tunnelling using a slightly modified version of the "vncviewer -via" command noted above: vncviewer -via remoteUser remoteHost localhost:vncSinglePortNumber For the default vnc-ltsp-config install, the "vncSinglePortNumber" is the last digit only of the port number.

Port x 16bit would just be "0", for example. Note: you will need to be aware of possible interaction issues if you enable either selinux or iptables. If you are not running a display manager runlevel 3 for example , you will need to start one or you will only get a black screen when you connect. Or you will need to help another user remotely with an GUI or visual issue.

You will need either "vnc-server" or "x11vnc". The vnc-server option will be a module added to X11 for "allways on" vnc support, while x11vnc will allow for adhoc vnc support. To make it easy, follow these steps: 1. Install, as root, via the yum or rpm programs on the host you want the vnc-client to connect to: yum install x11vnc Start the x11vnc process on the host you want the vnc-client to connect to. Please take a long look at the possible options from the x11vnc website.

By default, x11vnc will allow connections from all interfaces. Host based firewall settings may need to be modified.

You can combine this with ssh tunneling: ssh -C -t -L localhost [remote ip] 'x11vnc -usepw -localhost -display :0' Note that the -C flag is for compression, so may not be required 6. On the the system you want to run vnc-server, install vnc-server as noted above. SELinux is preventing tigervnc-server from starting, as we notice on fedora, selinux denial prevents daemon from starting, so we run setenforce 0.

Create new service file vncserver. Now reload systemd and start the VNC server. Finally we make the VNC service permanently available. The command open up a tunnel between your localhost and the VNC server. The port on localhost will be forwarded to the VNC server Now open vnc viewer application and start a new connection, type the VNC server address with the Please remember, the password is what we have previously entered with vncpasswd.

The following ports should be listening on, determine which ports active listening are with this:. If appears a black screen after successful connect from vncviewer, this cause often at the X11 cache, solve this by shutdown all vncserver instances and reset the X11 server cache, like use the command below:.

Modify SELinux to permissive that prints warnings instead of enforcing. Vote count: 0. No votes so far! Be the first to rate this post.

Your email address will not be published. How useful was this post? Click on a star to rate it! We are sorry that this post was not useful for you! Let us improve this post!