Admin Rights Problems When Accessing PC Over VNC Connection

[trinidad]

Generally, and really generally because Windows 10 has been finally integrating SSH into the 1800 series builds, pretty much breaking most of the traditional solutions for what you are trying to do like TightVNC, PuTTY, even Teamviewer, etc., yes TigerVNC generates a new xserver instance for each user, thus in your case user  and root, and I believe you must have two ports enabled, 5900 and 5901 to the client and an SSL or SSH tunnel. That setting is defaulted on x11vnc. I do believe x11vnc is the best solution via an SSH tunnel, given that you can obtain a secure shell now from Windows SSH and start and stop x11vnc server remotely. Make sure the LL machine is set to autologin and it's SSH server is on. The old problems with older hardware running modern Windows 10 builds are still there however, like RAM hogging when using VNC, 4gig is almost not enough these days. You can use an alternative x server on Windows 10 that is more RAM efficient like xming but I haven't configured one since the 1600 build series and even that may not work correctly. Of course Linux to Linux, and Linux to Windows RDP servers work flawlessly most of the time, but Windows to Linux VNC is fraught with problems as always, on the Windows client side of the connection. I would run x11vnc server and SSH server on the Linux side, and check the most recent documentation on Windows 10 SSH client, and TightVNC, not Tiger VNC, using an SSH tunnel to get a secure shell on the Linux side from Windows. I would probably wait until after the problematic fall update to Windows 10 installs though.

https://www.zdnet.com/article/openssh-ar...ng-update/
https://blogs.windows.com/windowsexperie...-insiders/

TC