Error in tightvnc viewer no security types supported windows

ssxitoperations

Posts: 2
Joined: 2019/06/06 14:14:07

Windows VNC client cannot access due to no security types supported

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.
Image

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

Code: Select all

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?


hunter86_bg

Posts: 2019
Joined: 2015/02/17 15:14:33
Location: Bulgaria
Contact:

Re: Windows VNC client cannot access due to no security types supported

Post

by hunter86_bg » 2019/06/06 16:24:05

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

For details check the documentation


ssxitoperations

Posts: 2
Joined: 2019/06/06 14:14:07

Re: Windows VNC client cannot access due to no security types supported

Post

by ssxitoperations » 2019/06/12 15:07:15

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?


The following steps can be executed from an SSH session:

1. Edit the RealVNC server configuration file:

sudo vi /root/.vnc/config.d/vncserver-x11

2. Insert, edit, or replace the following lines:

Authentication=VncAuth

Encryption=AlwaysOff

3. Choose a VNC server authentication password (does not require sudo):

vncpasswd -print

4. Copy the ENTIRE «Password=…encrypted password…» line and PASTE or REPLACE it into the file:

/root/.vnc/config.d/vncserver-x11

5. RESTART the RealVNC server:

sudo systemctl restart vncserver-x11-serviced

You should now be able to establish a VNC session using TightVNC or any other viewer. Use the password chosen in step 3.

I know this solution is 2 years late, but I’m pissed that nobody else figured it out, because it only took me 4 hours.

As a new comer to Fedora 20 after years on Ubuntu, I had a hard time enabling remote desktop connection (VNC).

The solution is below:

1) Settings -> System -> Sharing – enable Sharing then for Screen Sharing enable it and then enable all checkboxes and set the password.
2) Add port to firewall as root:

firewall-cmd --add-service=vnc-server

If you now try to connect using TightVNC Viewer, you’ll get an error that “No security types supported. Server sent security types, but we do not support any of their”.

tightvnc error

Checking journalctl I see:

Feb 11 18:49:33 biggie gnome-session[1333]: 11/02/2014 06:49:33 PM [IPv4] Got connection from client 192.168.0.105
Feb 11 18:49:33 biggie gnome-session[1333]: 11/02/2014 06:49:33 PM other clients:
Feb 11 18:49:33 biggie gnome-session[1333]: 11/02/2014 06:49:33 PM 192.168.0.105
Feb 11 18:49:33 biggie gnome-session[1333]: 11/02/2014 06:49:33 PM Client Protocol Version 3.7
Feb 11 18:49:33 biggie gnome-session[1333]: 11/02/2014 06:49:33 PM Advertising security type 18
Feb 11 18:49:38 biggie gnome-session[1333]: 11/02/2014 06:49:38 PM Client 192.168.0.105 gone

Now, it seems that vino-server only advertises TLS security (type 18).

Listing the parameters of the server:

gsettings list-keys org.gnome.Vino

we have:

[root@localhost ~]# gsettings list-keys org.gnome.Vino
alternative-port
authentication-methods
disable-background
disable-xdamage
enabled
icon-visibility
lock-screen-on-disconnect
mailto
network-interface
notify-on-connect
prompt-enabled
require-encryption
use-alternative-port
use-upnp
view-only
vnc-password

require-encryption caught my eye, so let’s see:

[root@localhost ~]# gsettings get org.gnome.Vino require-encryption
true

Aha!

TightVNC does not support that so let’s disable that (but since I’m on a local network, I don’t care about encryption).

[root@localhost ~]# gsettings set org.gnome.Vino require-encryption false

You have to set this from a terminal within Gnome – since if you’re trying to execute it from a remote ssh connection you’ll get:

(process:14322): dconf-WARNING **: failed to commit changes to dconf: Error spawning command line 'dbus-launch --autolaunch=ef20763b7e33442b8a7947074a1858cd --binary-syntax --close-stderr': Child process exited with code 1

Now, you can connect as long as you accept the connection from the PC itself. I still have to figure out how to support unattended connections without using tightvncserver alternative ..

vasily86

Обновил дистриб убунты, выставил подключение по удалёнке, а подключение по TightVNC не получается, пишет «No security types supported. Server sent security types, but we do not support any of their «, Решение
1) $ sudo apt-get install dconf-editor
2) $ dconf-editor
org > gnome > desktop > applications > remote-access
3) снимаем флаг напротив «REQUIRE-ENCRYPTION»
Теперь TightVNC отлично подключается

remote desktoptightvncubutnu

LJ Video

Перейти к контенту

I’m having trouble accessing Linux Mint 17 Cinnamon from tightVNC or realVNC on Windows 7 or 8 on the same LAN. The errors I’m getting seem to be related to security or encryption.

So far on the Mint desktop I have opened Desktop Sharing in Preferences and ticked: Allow other users to view your desktop, allow other users to control your desktop, require the user to enter this password xxxx

I’ve toggled the password setting with no success.

The error message from TightVNC is: Error in TightVNC Viewer: No Security types supported. Server sent security types, but we do not support any of their.

I have successfully gained VNC access from Windows to a Mint 16 Cinnamon on a USB stick so I’m guessing I’m missing some extension or security setting.

I have tried installing sudo apt-get install xrdp from this article http://forums.linuxmint.com/viewtopic.php?f=42&t=154150 Opens a new window but with no luck.

I’m confident there isn’t a firewall on my windows machine blocking the VNC port, hopefully the Linux savvy members are able to make a suggestion as to where I’m going wrong?

Thanks in advance.

ssxitoperations

Posts: 2
Joined: 2019/06/06 14:14:07

Windows VNC client cannot access due to no security types supported

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.
Image

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

Code: Select all

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?


hunter86_bg

Posts: 2019
Joined: 2015/02/17 15:14:33
Location: Bulgaria
Contact:

Re: Windows VNC client cannot access due to no security types supported

Post

by hunter86_bg » 2019/06/06 16:24:05

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

For details check the documentation


ssxitoperations

Posts: 2
Joined: 2019/06/06 14:14:07

Re: Windows VNC client cannot access due to no security types supported

Post

by ssxitoperations » 2019/06/12 15:07:15

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?


Michele31415

Posts: 20
Joined: Sat Dec 10, 2016 10:22 pm

VNC viewer: «No matching security types»

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?


Michele31415

Posts: 20
Joined: Sat Dec 10, 2016 10:22 pm

Re: VNC viewer: «No matching security types»

Mon Mar 06, 2017 5:59 am

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.


User avatar

DougieLawson

Posts: 42324
Joined: Sun Jun 16, 2013 11:19 pm
Location: A small cave in deepest darkest Basingstoke, UK

Re: VNC viewer: «No matching security types»

Mon Mar 06, 2017 7:15 am

Languages using left-hand whitespace for syntax are ridiculous

DMs sent on https://twitter.com/DougieLawson or LinkedIn will be answered next month.
Fake doctors — are all on my foes list.

The use of crystal balls and mind reading is prohibited.


Michele31415

Posts: 20
Joined: Sat Dec 10, 2016 10:22 pm

Re: VNC viewer: «No matching security types»

Mon Mar 06, 2017 4:50 pm

That’s the one I’m using. It’s lucky it worked too, as the procedure for changing this via ssh looked a lot more complex. And as I have no HDMI cable, that’s my only access.



User avatar

jahboater

Posts: 8489
Joined: Wed Feb 04, 2015 6:38 pm
Location: Wonderful West Dorset

Re: VNC viewer: «No matching security types»

Wed Mar 22, 2017 6:41 pm

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

Did you mean «Jessie» on your Pi3?


estufa8

Posts: 3
Joined: Wed Jul 20, 2016 1:59 pm

Re: VNC viewer: «No matching security types»

Sun Dec 10, 2017 2:53 pm

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.


PiPilotDi.ink.ar

Posts: 1
Joined: Thu May 30, 2019 6:04 pm

Re: VNC viewer: «No matching security types»

Thu May 30, 2019 6:27 pm

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.


cwclee

Posts: 1
Joined: Tue Nov 26, 2019 7:30 am

Re: VNC viewer: «No matching security types»

Tue Nov 26, 2019 7:36 am

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!


Return to “Troubleshooting”

As a new comer to Fedora 20 after years on Ubuntu, I had a hard time enabling remote desktop connection (VNC).

The solution is below:

1) Settings -> System -> Sharing – enable Sharing then for Screen Sharing enable it and then enable all checkboxes and set the password.
2) Add port to firewall as root:

firewall-cmd --add-service=vnc-server

If you now try to connect using TightVNC Viewer, you’ll get an error that “No security types supported. Server sent security types, but we do not support any of their”.

tightvnc error

Checking journalctl I see:

Feb 11 18:49:33 biggie gnome-session[1333]: 11/02/2014 06:49:33 PM [IPv4] Got connection from client 192.168.0.105
Feb 11 18:49:33 biggie gnome-session[1333]: 11/02/2014 06:49:33 PM other clients:
Feb 11 18:49:33 biggie gnome-session[1333]: 11/02/2014 06:49:33 PM 192.168.0.105
Feb 11 18:49:33 biggie gnome-session[1333]: 11/02/2014 06:49:33 PM Client Protocol Version 3.7
Feb 11 18:49:33 biggie gnome-session[1333]: 11/02/2014 06:49:33 PM Advertising security type 18
Feb 11 18:49:38 biggie gnome-session[1333]: 11/02/2014 06:49:38 PM Client 192.168.0.105 gone

Now, it seems that vino-server only advertises TLS security (type 18).

Listing the parameters of the server:

gsettings list-keys org.gnome.Vino

we have:

[root@localhost ~]# gsettings list-keys org.gnome.Vino
alternative-port
authentication-methods
disable-background
disable-xdamage
enabled
icon-visibility
lock-screen-on-disconnect
mailto
network-interface
notify-on-connect
prompt-enabled
require-encryption
use-alternative-port
use-upnp
view-only
vnc-password

require-encryption caught my eye, so let’s see:

[root@localhost ~]# gsettings get org.gnome.Vino require-encryption
true

Aha!

TightVNC does not support that so let’s disable that (but since I’m on a local network, I don’t care about encryption).

[root@localhost ~]# gsettings set org.gnome.Vino require-encryption false

You have to set this from a terminal within Gnome – since if you’re trying to execute it from a remote ssh connection you’ll get:

(process:14322): dconf-WARNING **: failed to commit changes to dconf: Error spawning command line 'dbus-launch --autolaunch=ef20763b7e33442b8a7947074a1858cd --binary-syntax --close-stderr': Child process exited with code 1

Now, you can connect as long as you accept the connection from the PC itself. I still have to figure out how to support unattended connections without using tightvncserver alternative ..

Symptoms

While trying to access Mac Client via TightVNC in SCCM Console the error occurs:

alttext

Resolution

On the Mac do the following:

  1. Open Sharing preferences if it isn’t already open (choose Apple menu > System Preferences, then click Sharing), then select the Remote Management checkbox.

  2. Do one of the following:

    • Select “All users” to let all users on your network connect to your Mac using Apple Remote Desktop.

    • Select “Only these users,” click Add , then select the users who can share your Mac using Apple Remote Desktop.
  3. Click Options, then select the tasks remote users are permitted to perform.

  4. Click Computer Settings, then select options for your Mac. If people connect using a VNC viewer, you need to set a password.

If there were active VNC sessions on the Mac, you may need to restart it to apply the changes.

For more information, please refer to: OS X Yosemite: Allow access using Remote Desktop

  • Ex machina для windows 10 64 bit
  • Error loading operating system windows 10 при запуске
  • Error load settings windows 10
  • Ex machina unhandled exception expcode 0xc8000003 windows 10
  • Error legacy boot of uefi media при установке с флешки windows 10 как исправить