Ubuntu – How to configure Remmina for VNC desktop sharing

12.04remminavnc

I'm trying to connect two PCs for desktop sharing, I was able to set up ssh shell and file sharing but I failed to connect to VNC server.

There are additional packages that I need to install on my machines?

And how should I fill this dialog:

Best Answer

To use VNC, you must have a VNC server installed and running on the machine.

sudo aptitude install vnc4server

Follow the instructions

You will require a password to access your desktops.

Password:
Verify:
Password too long - only the first 8 characters will be used
xauth:  creating new authority file /home/server/.Xauthority

New 'server:1 (root)' desktop is server:1

Creating default startup script /home/server/.vnc/xstartup
Starting applications specified in /home/server/.vnc/xstartup
Log file is /home/media/.vnc/media:1.log

Now you can connect to this machine using Remmina on the other machine.

Reference: Install VNC Server and VNC Client on Ubuntu

Related Solutions

Ubuntu – Gnome 3.10 sharing desktop — how to configure the security type for VNC

Real solution: I am now using SSVNC on the windows machine and x11vnc on the linux server. Works with bVNC on android too. You need a bit of expertise to make it work, so terse instruction here:

On Linux (follow the instruction that x11vnc is giving you, is verbose but worth reading):

x11vnc -storepasswd
x11vnc -forever -repeat -usepw -ssl -autoport 6000

(you will have to put the last one in one of your login startup scripts, or whatever. Do not use a passphrase on the generated SSL certificate. I am using port 6000 to not mess with vino).

On Windows: Install the binary client from here.

Connect and enjoy a (slowish...) encrypted connection.

Partial answer: (posted for sake of helping other people, NOT RECOMMENDED); I hope there will be other answers to the question --- I will mark this answer as the right one as there are no solution by now).

The problem surfaced when the Vino project decided to switch to require encryption by default --- unfortunately, the only kind of encryption supported by the vino server (type 18) is not supported by most of the Windows, Android, and iOS viewer. For what I know, only the Linux-based vinagre viewer supports it.

I have reported a bug to the Vino project, both upstream and in launchpad about this issue; look there for more details. Basically, it seems that there is no sufficient developer power to implement more encryption types to the server (fair enough).

That means that you can go back to the previous, unsafe behavior by disabling encryption for the whole VNC layer by using dconf-editor like this:

No Encryption for VNC

Big fat notice that means that all what you type is visible in clear in the network. Passwords included.

I can do it because the connection is really through an encrypted SSH tunnel and there are no other local users on the remote machine --- but even in this case, if someone manage to get access to your machine, they can read all your secrets by sniffing 127.0.0.1...

Best Answer

Related Solutions

Ubuntu – Gnome 3.10 sharing desktop — how to configure the security type for VNC

Related Question