-
Notifications
You must be signed in to change notification settings - Fork 174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Authentication problems with RealVNC Server installed on Raspberry PI3 #134
Comments
Status: I"m able to see what happen, if no encrytion is needed we possible can implement it, no promises. |
@RudiDeVos thanks for your answer, maybe these links can help you: The strange thing is that, at the moment, on my server, the security encryption is set to AlwaysOff and the only possible options for the Authentication property are: |
Does someone has a linux image with a vncserver that support RA2NE. Updated tigervnc manual to 1.13, that should support it. SConnection: Client requests security type RA2ne(6) |
Spending to much time on server setup while i should be testing the viewer... |
I have a ubuntu server hosted on raspberry pi, I connect it using ssh instead of HDMI, I have enabled VNC on it but I am not sure if its supports RA2ne @RudiDeVos |
This isue is more or less the same as #133 |
branche RA2ne created. vnc server |
Thanks to Vladimir Vissoultchev extra AUthentication methods have been implemented in the viewer. Extra Info
eNCrypt authentication with TLS encrypted transport (#142)
|
Thanks a lot @RudiDeVos, now it works perfectly. |
Hello,
I've used UltraVNC Viewer for ages, with Windows, Linux and Rasbian systems.
With the last version 1.4.3.6 I have problems during the connection phase to my Raspberry device.
I want to start by saying that I moved from RealVNC 6 to RealVNC 7.8.0 but I have the same problem with both versions.
BTW, I'm going to try to briefly explain the problem and enclose to this request also the RealVNC logs captured from Raspberry Debian OS and some screenshots, about the UltraVNC messages, captured from my Windows PC.
I made three tests, one with RealVNC Viewer, one with TigerVNC, and obviously, one with UltraVNC Viewer.
Other important things to say is that RealVNC is configured with:
The other configuration properties are set to their standard values.
Despite the various guides that I read on the Internet in which this seems to be the configuration that enables the other viewers to talk with success with RealVNC, this communication is systematically interrupted by the UltraVNC side (but I tried also with TightVNC and the problem seems to be the same) with the "no supported authentication methods" message.
This doesn't happen when I use RealVNC viewer or TigerVNC.
Now I will paste the captured logs and the screens
UltraVNC with Authentication property set to VncAuth
UltraVNC with Authentication property set to None
TigerVNC with Authentication property set to VncAuth
RealVNC Viewer with Authentication property set to VncAuth
Following you can read the details about the RealVNC Server version.
Finally, I tried also different versions of UltraVNC and I obtained the same result with the VNC password authentication system enabled.
The text was updated successfully, but these errors were encountered: