35

I just bought raspberry pi 3 with Rapbian Jessi with Pixel and I have a Lenovo laptop with Ubuntu 14.04 64 bit on it.

I want to remote connect to it from my laptop. I enabled the VNC server on Raspberry Pi and I tried to connect to it from either Remmina 0.9.99.1, Remote Desktop Viewer, or even Gtk VNC Viewer. In Remmina it gives me the following error:

Unknown authentication scheme from VNC server: 13, 5, 6, 130, 192

I failed to make this work, although I can connect smoothly using SSH. Any ideas how can I make it work as it looks it should be a straight forward thing.

techraf
  • 4,353
  • 10
  • 32
  • 43
aibrahim
  • 757
  • 1
  • 5
  • 8

8 Answers8

19

later I found out another solution to make it work for Remmina 0.9.99.1. You can change the security authentication for the VNC server to be VNC Password instead of Unix password and create an admin user credentials so you can use it in the remote connection as the following:

On VNC Server side on Raspberry Pi 3

Go to the options on the VNC Server on Raspberry Pi 3 and you should have the sudo credentials when you started VNC server

Change the security authentication to VNC Password as shown belowenter image description here

Finally you need to add a user to use it to connect. In my case I created an administrator user (default username was admin)

On Remmina side on Ubnutu

You will create a new connection with the given IP address of the Raspberry Pi on your local network (you should be able to know it using ifconfig) and using the admin user credentials created on VNC server as the following: enter image description here

Please note that It worked with me while encryption was off, as it made some problems mentioned in other posts. I will try to see if it will work with encrypted on or no.

Community
  • 1
aibrahim
  • 757
  • 1
  • 5
  • 8
12

I've just encountered the issue too.

As an alternative to aibrahim's method if you are doing it remotely via ssh, here's my steps to VNC to display :0.

  1. Setup password using sudo vncpasswd -service
  2. Add the following lines to /root/.vnc/config.d/vncserver-x11 as described in RealVNC: Support legacy viewers 
    SecurityTypes=VncAuth
UserPasswdVerifier=VncAuth
  3. Start vncserver using command sudo vncserver-x11-serviced

This method allows me to login using Ubuntu's Remmina VNC client.

Luismi
  • 103
  • 3
sonofusion82
  • 304
  • 2
  • 5
6

The simplest solution is to install RealVNC Viewer. You can download it from here, and it is available for Linux, MacOS and Windows. The issue is with the encryption schemes used by different VNC servers.

Steve Robillard
  • 34,988
  • 18
  • 106
  • 110
4

The main problem is that the Raspberri Pi runs RealVnc as server. Lots of answers suggest to connect using RealVncViewer. But RealVnc is not really free, it has a free version, and uses special encryption schemes. Probably good ones, but this makes it harder to use other VNC clients.

Steps to find out about this:

  • aptitude search vnc
  • look for installed packages with i in the first column
  • on my PI it showed realvnc

The obvious solution, and I tried this with success, is to remove the RealVNC server from the Pi, and to switch to a 'regular' VNC server like x11vnc. Steps:

  • Go to Preferences, Pi Configuration, Interfaces, and disable VNC
  • In a terminal: sudo aptitude remove realvnc-vnc-server
  • sudo aptitude install x11vnc # or another vnc server
  • start the VNC server with: x11vnc -display :0 (see also man x11vnc)

On your ubuntu pc, you may now connect to the PI with e.g. Remmina

Todo: start the VNC server on the PI in the background

Roland
  • 238
  • 1
  • 7
3

I found out that with the current authentication on VNC using linux authentication, the only way to make it work is to use the RealVNC viewer settings of VNC viewer on Ubuntu 14.04

all what you need is to download the binary file (or GZ file and un-compress it and then make the file executable and so you can run it.

aibrahim
  • 757
  • 1
  • 5
  • 8
2

I had the same exact problem, after searching through I found that problem was related to authentication and following line helped me to resolve the issue. I forgot which Stack Exchange I found the answer from.

Here are the steps that I took:

  1. Connect to your Raspberry Pi through ssh command.

    ssh pi@your raspberry ip

    Then enter your password to your Raspberry Pi.

  2. Start your vncserver on your Raspberry Pi with the following command

    vncserver -Authentication VncAuth :1

  3. Go to your Remmina:

    1. Set your protocol to VNC
    2. Enter the IP address from your raspberry pi new desktop this should be in the last line after entering the code in step 2

  4. Put your username and password for Raspberry Pi

  5. If you set up different password for your VNC server you need to add to the prompt.

After this I was able to remote log-in to my Raspberry Pi.

I found bits and pieces of the info on different exchange and had to put it together.

Greenonline
  • 2,969
  • 5
  • 27
  • 38
Shahin Shirazi
  • 123
  • 4
0

I had a similar problem when trying to connect to Raspbian Buster and the instructions at the link below solved my problem without having to install a new VNC server.

https://gitlab.com/Remmina/Remmina/-/wikis/Problems-and-tweaks/Remmina-VNC-to-Raspbian-Stretch

alexpotato
  • 131
  • 3
0

I read tons of posts about this issue... and they all resulted in connection from my Mac via Remoter to a black screen on the Raspberry Pi.

DISPMANX was the ulimate solution to VNC into the Raspberry Pi running Raspbian Lite.

Here is the summary:

BASIC SETUP - RESULTS IN BLACK SCREEN FOR VNC

SSH Enabled via Raspi-Config on Raspberry Pi Remoter for Mac (VNC + SSH/Terminal Access) SETUP: https://computers.tutsplus.com/tutorials/take-control-of-your-raspberry-pi-using-your-mac-pc-ipad-or-phone--mac-54603

FINAL SETUP - TO ELIMINATE BLACK SCREEN FOR VNC

Desktop GUI for Raspbian Lite needs Additional Setup i.e. DISPMANX SETUP: http://raspmer.blogspot.ca/2015/07/vnc-server-for-raspberry-pi-with.html

START VNC VIA GUI - NOT REMOTE SSH sudo dispmanx_vncserver

CONNECT VIA REMOTER TO IP

ATSiem
  • 111
  • 3