On Wed, Jun 19, 2024 at 5:10 AM Dark Corner <darkcorner...@gmail.com> wrote:
> It doesn't connect with RealVNC. > The original Viewers and Servers need the account on realvnc.com, then a > second password must be set on the server for the connection. > > Yeah, I did a little digging on this, and it looks like RealVNC has pretty well made their solution a proprietary one - even if you start a RealVNC server with -Authentcation=None, the negotiation between client and server shows that the server supports several security types - 13, 133, 5, and 129, IIRC - none of which libvncclient support ([1]). I don't know if other VNC clients, like (Tight, Tiger, Ultra) are capable of connecting to RealVNC, but I'd be a bit surprised - RealVNC seems to be taking their product in the direction of TeamViewer, AnyDesk, NoMachine, etc., where they want you to subscribe to and broker through their cloud service, and aren't interested in actually providing a RFB-compatible server. > I tried both the Xubuntu user credentials and the RVNC username plus the > connection password. > It does not work. > I could install another VNC, but I can't remove the RVNC because it is > already needed by a technician. > > You might still be able to install another VNC server and use a different port number. But, hard to say how well (or poorly) multiple VNC servers will cooperate together. > I installed xrdp following the reported guide. > I then cloned an RDP connection to a Win10 PC already tested as working. > I then changed the IP Address and using the credentials of a Xubuntu user, > but when I try to connect I am immediately disconnected. > The "Security mode" option must always be on NLA (Network Level > Authentication)? > I do not believe that xrdp supports NLA - I think you need TLS. > Should "Ignore server certificate" be On or Off? > > For testing, you can turn it on so that the certificate validity isn't an issue - in Real Life, you should make sure you trust your server certificates. -Nick
