Excellent. My windows station is able to see my linux Deb 9 station on the network, and knows that there's an open VNC port.Now, I fire up VNC and try to connect to my Deb 9, and I get an error message :

"Unable to connect to VNC Server using your chosen security setting. Either upgrade VNC Server to a more recent version from RealVNC, or select a weaker level of encryption."

Any idea why I get this error, and how may I VNC to my Deb 9 ? This would be a tremendous help to me.

Edit: For our corporate use, we have an Enterprise version of RealVNC server and viewer for use from RealVNC (4.6.3). And it by default asks/takes our corporate logins (which it checks to make sure are valid corporate logins, though can also be configured to use other passwords as well). Here, in my case, I don't know that's matters, is required.

Last edited by white_tee_shirt on 2018-02-09 14:09, edited 1 time in total.

I am still relatively new to Linux and Debian in general and am not sure if it is an option, but perhaps you could install RealVNC on your Debian machine? I use RealVNC to connect to a Raspberry Pi 3 setup that I have and RealVNC VIewer on a Desktop and the two work perfectly together under that setup. I found this https://www.realvnc.com/en/connect/docs ... emove.html that may help get you setup. Again, I am new to all of this and apologize if it has nothing to do with your issue but hopefully it will help.

pekwalker wrote:I am still relatively new to Linux and Debian in general and am not sure if it is an option, but perhaps you could install RealVNC on your Debian machine? I use RealVNC to connect to a Raspberry Pi 3 setup that I have and RealVNC VIewer on a Desktop and the two work perfectly together under that setup. I found this https://www.realvnc.com/en/connect/docs ... emove.html that may help get you setup. Again, I am new to all of this and apologize if it has nothing to do with your issue but hopefully it will help.

Peter

I don't want to download RealVNC from their website and then unpack the tarball and have it's files installed in my ~/Downloads directory. I wish to have it installed in the right directory. Ideally I want a .deb file so that I can add it to my repository and install the package. RealVNC site doesn't give any info about how to install that way. To answer, I haven't tried realvnc, I couldn't find much help online and I have written them an email this morning ask how may I install and use without tarballs.

by white_tee_shirt »I don't want to download RealVNC from their website and then unpack the tarball and have it's files installed in my ~/Downloads directory. I wish to have it installed in the right directory.

Unpack it there. Just because it is in the Download directory , (which is normal for downloaded files) does not meant you have to unpack it there, or leave it. The same if you download a .deb file, unless you specify a different directory, it is going to go to the Downloads directory, however with the .deb , if you use gdebi, or 'dpkg', it will install to the appropriate directories and libraries as needed.

by white_tee_shirt »Then, when I go to my Windows station ---- snip------

Sorry , I have never used,and never will be using Windows, so I can't help with that. But this seems straightforward and clear enough:

"Unable to connect to VNC Server using your chosen security setting. Either upgrade VNC Server to a more recent version from RealVNC, or select a weaker level of encryption."

Any idea why I get this error, and how may I VNC to my Deb 9 ? This would be a tremendous help to me.

The error message tells you why : Your choosen security setting is not acceptable. It also tells you quite clearly: "Either upgrade VNC Server to a more recent version from RealVNC, or select a weaker level of encryption." That is not hard to understand even for me, and I am not very smart. 2 choices, upgrade it to a more rent version, or select weaker encryption.

GarryRicketson wrote: So, why don't you create the directory you want to have it in ?

Hi Garry, I agree w. you 100%. It was a continuation of some my gripe with some other packages who doesn't offer a standard directory to install, and I didn't know where `anydir` should be. If I moved them to `/etc/opt` then I am needed to be in root to execute, which I don't desire to. As for why not .deb , and use gdebi, or 'dpkg', While it is true that it will install to the appropriate directories and libraries as needed, I was un-successful in finding a .deb from RealVNC for their server and client.

GarryRicketson wrote: Sorry , I have never used,and never will be using Windows, so I can't help with that. But this seems straightforward and clear enough:

I have no choice but use Windows workstations at my work environment as thats what IT provided us with here. The security I chose was a normal vnc password setup. As for the version, it was indeed a latest version of the VNC server and client available to me, just not a version the Windows client wanted it to be. So I think thats' where the issue lie. Thanks for replying.

The following instructions apply to all UNIX and Linux platforms. Where an example is given, the syntax is valid for Ubuntu 8.10 Linux.

Open a Terminal window and switch to root, or to a user with equivalent permissions. Extract and decompress the contents of the tarball, for example tar -xvzf <tarball>, where <tarball> is the full path to the downloaded .tar.gz file. A new sub-directory is created with the root name of the .tar.gz file. Navigate to this newly-created directory and run the vncinstall script, for example ./vncinstall.

The vncinstall script installs programs into default system directories; examine the script for details. To specify different directories, run vncinstall with the following parameters:

vncinstall <program-dir> <manual-dir> <module-dir>

where <program-dir> is the full path to a directory for VNC programs, <manual-dir> is the full path to a directory for VNC man documentation pages, and <module-dir> is the full path to a directory for the vnc.so module. Note that all three parameters are mandatory; if you specify one you must specify them all.

When VNC Enterprise Edition has successfully installed you can delete the newly-created directory.

It should create a sub directory in the /home/garry/VNC dir, it will be the name that the "tar.gz" file has. I prefer moving the file to the directory I created first, but in any eventsince it creates it's own sub dir when you unpack it, it is no big deal, if it is not where you want it, you can delete or remove the same dir, and try again.

Navigate to this newly-created directory and run the vncinstall script, for example ./vncinstall.

The vncinstall script installs programs into default system directories; examine the script for details. To specify different directories, run vncinstall with the following parameters:

vncinstall <program-dir> <manual-dir> <module-dir>

where <program-dir> is the full path to a directory for VNC programs, <manual-dir> is the full path to a directory for VNC man documentation pages, and <module-dir> is the full path to a directory for the vnc.so module. Note that all three parameters are mandatory; if you specify one you must specify them all.

I don't think you should or need to do this part, it is hard to say on that, I would try it with out changing anything first. If you get errors, and don't understand , we would need to see the script as well.

After all said and done, I think it would be easier and better if you just used some VNC packages that are in the Debian repositories , instead of this, but that is your option.