RealVNC users may see the following error message when connecting to their PC:
"VNC Server Error - No configured security type is supported by 3.3 viewer"
To fix this you'll need to change the way RealVNC authenticates the VNC client. Follow the steps below:
- Double click the RealVNC icon in the notification area of the taskbar (bottom right hand corner of your Desktop). This should show you the RealVNC configuration window.
- Click the 'Configure' button.
- Make sure Authentication is set to 'VNC Password'.
- Click the 'Configure' button in the Password. Enter a new password in there, then Apply your settings.
- Make sure Allow connections from legacy VNC Viewer users is also checked. If you don't see the option there try this: Set Encryption to Prefer off. Clear the VNC passwords (by selecting Unix password) and then re-enable VNC password authentication. When specifying the new password the dialog box will then offer a checkbox for Allow connections from legacy VNC Viewers. Check this box Apply.
- Try connecting again.
This suggestion only works if I turn off encryption in my Enterprise RealVNC Server (Configure->Options->Encryption->Prefer Off).
However, I would like to use encryption. Will this be available in a future release of JumpDesktop?
Ryan, at this time we don't have plans to support RealVNC's encryption mechanism as RealVNC doesn't publish the specs for it's protocol. Jump does have it's own way to encrypt the connection if you use the automatic setup method (it uses SSL encryption).
I ran across this 6 year old post after trying to connect to the 5.3.2 VNC server in Raspberry Pi 4.4.21. Is the answer still accurate?
Yes, it is if you're using RealVNC server: You'll need to enable password based authentication for RealVNC. The method to enable it might vary on the Pi. The steps above are only for the PC.
Thanks, I did have to use a 6 character VNC password to get it to work.
My company REQUIRES 128 bit encryption for VNC....is this supported now in 2017?
Yes, encryption over VNC is supported. Are you connecting to a RealVNC server? If so, it uses proprietary encryption which NOT supported. The types of encryption supported for VNC are:
I would need the step-by-step settings for the jump config...thanks
Kerry - are you connecting to a Windows or Mac machine? If so, the best / easiest way to connect it using Jump's automatic setup - it'll take care of encryption for you. On the machine you want to connect TO just visit https://jumpdesktop.com/go and follow the instructions there.
If you're on Linux then shoot an email to email@example.com with details about your current configuration and we'll walk you through it.
RealVNC does not have a setpoint "Authentication" or anything resembling such a setpoint. One could change the encryption like off but not 'VNC Password'.
How does one use Jumps automatic setup on a headless machine?
For Raspberry PI configuration please take a look at this: https://support.jumpdesktop.com/hc/en-us/community/posts/214914923-raspberry-pi-support?page=1#community_comment_360000138486
This did not work for me as I had already got VNC password set. I can connect to my Ubuntu 16.04 box but to the 18.04 machine? What has changed in Ubuntu as I have given permission to receive VNC connections on both Ubuntu machines.
@Anthony - you may also need to set VNC Server's setting: 'VNC Encryption to 'Preferred on'.
Where should I set the VNC server setting - VNC Encryption ?
These steps above make no sense to me:
When I double click VNC as instructed I do not see any configure button
I see a dialog box with five tabs - Server, Extra Ports, Access Control, Video & Administration.
How can I connect to Ubuntu 18.04?
Your instruction "Make sure Authentication is set to 'VNC Password'.
Where? Please be specific.
This was also just now given to me as an answer for connection to VNC on Debian Bullseye 64 bit (Raspberry Pi). Irrelevant. Not a PC. All other VNC viewers I have tried on various platforms connect to this Raspberry Pi system fine, including the Real VNC app on the same iOS iPad. I like Jump but it's no longer working after a recent Linux system update/upgrade cycle.
This is relevant. It applies to PCs or Linux machines - VNC Viewer has the same UI everywhere.
Please see this: https://support.jumpdesktop.com/hc/en-us/community/posts/214914923/comments/14447962087949
The article you pointed to originally has completely different instructions. And the second one had to be updated by @Woodrow Stool just a couple of weeks ago. For those on Linux the instructions in the post below the one you just posted are the correct ones. The convoluted way to get to the "legacy" checkbox had completely eluded me.
The good news is that this worked!! But no other viewer needs to have the server configured for legacy, FYI.
Thanks. We've updated the above article.
Please sign in to leave a comment.