Error in tightvnc viewer no security types supported windows

I enabled VNC through screen sharing in Gnome. I think this runs the vino as the VNC server.

From a Windows computer, I used various VNC clients (e.g. TightVNC, RealVNC, etc.).

All of them return an error message indicating no security types supported.

Did some research and it seems that vino requires TLS encryption. The workaround is to bypass encryption by disabling it

gsettings set org.gnome.Vino require-encryption false

I tried that and restarted machine. However, I still get the same error.

Any ideas on how to get VNC working?

Just install the tigervnc server package and configure it properly.
I prefer to tunnel VNC traffic through ssh.

For details check the documentation

I followed the instructions in the article.

I was able to configure the VNC server for a single user and can remote into it fine by remoting with [IP of machine}:[display number]

However, I wanted to setup VNC based on xinetd with XDMCP for GDM also referenced in the article. I completed the steps required. However, when I tried to remote in with [IP of machine]:5950 — I received a message that the machine actively refused it.

It looks like xinetd never loaded the new services. Am I missing a step?

So I did an update today on my Pi 3 running Raspbian. Now when I try to connect to it using VNC from my PC, the VNC viewer goes «No matching security types». That’s with RealVNC. I get the same error when running vncviewer in Solaris 10. If I try TightVNC on the PC, I get «No security types supported». Oddly enough, the VNC Viewer app for Android works fine.

I tried restarting the Pi’s vncserver with «vncserver -Encryption AlwaysOff» but that didn’t help. There seems to be no shortage of questions about this error on the web, but no answers that helped. I searched the forum here and came up empty. Does anyone know what the problem is here?

Update

For the benefit of anyone else with this problem, here’s the solution.

Using the Android VNC Viewer app, I was able to open a connection to the Pi. From there I opened the VNC server window. From there I went to the Options menu, set Authentication to «VNC password» and Encryption to «Prefer off». I then clicked OK and that was that. I can now log into the Pi using RealVNC and TightVNC from my PC’s again.

kdebruine wrote:Thanks. This fixed it on my RPi 3 running Jennie. I use TightVNC Viewer.

Did you mean «Jessie» on your Pi3?

Michele31415 wrote: ↑

Mon Mar 06, 2017 5:59 am

set Authentication to «VNC password» and Encryption to «Prefer off».

Thanks, it worked! I used Chrome VNC from Windows to set that config. Now I can connect using RealVNC.

You can use following steps:
Step 1: If you have VNCServer already running just kill it. Use «vncserver -kill :windowNumber». You can find your window number in the raspberry pi terminal. Generally, you can use 1.

Step 2: Now you should start your VNCServer by the following command «vncserver -Encryption PreferOff -Authentication VncAuth». Hit Enter.

Step 3: This would also prompt you to provide the password just enter a simple one like «raspberry».

Step 4: Go to the VNC Viewer client on your client PC. Enter the IP address of your Raspberry Pi followed by the display number. Ex: «192.168.43.0:1» Click on Connect. Enter the specified password. And you are logged into your VNCServer.

Hope this would help.

Hi PiPilotDi.ink.ar,
Your solution is working for me. However, once the Pi re-started, I have to run the command «vncserver -Encryption PreferOff -Authentication VncAuth» again. How can I add the command some where in Pi so the command will run once the Pi starts?

Thank you!