Hi Bob question on getting TurboVNC running

[Aaron D. Johnson]

Phil Marsh writes:

> You're right, but I have no need for the encryption ssh provides
> because my connection is tunneled through OpenVPN and encryption
> just adds overhead.  However, SSH also provides x11 forwarding which
> I don't get from Telnet of course.  So it can make sense to use ssh
> through the OpenVPN tunnel anyway and I'll try that.  If I use SSH
> as stand-alone, I'll be setting up a reverse SSH tunnel.

You're not required to do the X11 forwarding with SSH.  And I disagree
that the encryption "just adds overhead."  It provides not just
privacy of your communications, but also authentication of the
server's identity, passwordless logon, and still saves 3 characters of
typing when initiating a session.

Further, the encryption overhead is just not measurable in 2025 -- the
Intel CPU AES encryption acceleration instructions were introduced in
January 2010.  I've seen your current laptop and heard many
descriptions of your servers.  They are not so old that they lack this
feature.

Moving on to the actual problem, though...

> However, I still don't understand why I can start the Turbo VNC
> server (command vncserver) from a Telnet terminal on my other
> machines (Ubuntu 22.04) but not on the Ubuntu 24.04 machine I've set
> up for a small company here in CA at UCI.  If I could start the VNC
> server only on SSH, then I'd say that's the solution.  It doesn't
> matter whether the Telnet terminal window is remote or running on
> the local machine as per the results.  I'd be surprised if SSH
> helped here?

As I said last night...  There is some difference in the two servers'
configuration that is impacting you.  Compare logs from the TurboVNC
invocations on both machines.  Compare package lists.  Compare process
environment variables.  There will be differences, and one (or more)
of those differences is what is preventing your desired outcome.

- Aaron