Avalanche/RealVNC Server
Richard Ashbery (8349) 42 posts |
Unable to get Avalanche (V 0.28) to talk to RealVNC Server (V 6.8.0) on Windows 10. Has anyone got this combination to work please? |
Paolo Fabio Zaino (28) 1882 posts |
@ Richard I normally use it the other way around, however few things come to mind: 1) Have you disabled encryption on the RealVNC Server? More info on the RealVNC Server parameter lists here: https://help.realvnc.com/hc/en-us/articles/360002251297-VNC-Server-Parameter-Reference- Avalacnhe, AFAIK, handles VNC Protocol 3.3, 3.7 and 3.8. I am not aware if later protocols support has been added, sorry. Hope this helps! |
Richard Ashbery (8349) 42 posts |
Thanks for your reply Paolo. Ref your questions – following changes made: 1. Set for ‘Always off’ The link to RealVNC Server parameter list was very useful even if I couldn’t get it to work – what a long and complicated list! No matter although not so secure I’ve downloaded TightVNC and it worked first time. |
Paolo Fabio Zaino (28) 1882 posts |
Indeed! |
Paul Sprangers (346) 524 posts |
On my setup Avalanche stopped listening to RealVNC months ago. I’ve tried numerous things (mostly without knowing what I was doing), to no avail. This weekend I decided to install the TightVNC server on the Windows side: same problem. But then per accident, I had a look at Avalanche’s title bar and saw that it was using port 5901, rather than port 5900. And only then, after some blind tries, I suddenly realised that the mysterious ‘Screen’ button was responsible for that. Setting it to 0 brought back the long missed connection. I haven’t re-installed the RealVNC server, but I suppose that it would work as well, since it has done so for many years. |
David J. Ruck (33) 1635 posts |
That always catches people out, a VNC server can support 10 or more screens on the 59xx ports, the problem is some start at 0 and others at 1 (although I have seen one which 5910 is the default). |