From: sauer@technologists.com (Charles H Sauer)
Subject: [TUHS] X->VNC->RDP experience [was Re: X, Suntools, and the like
Date: Fri, 17 Mar 2017 16:39:00 -0500 [thread overview]
Message-ID: <DA776143C9A6490296D7DFC201A3155C@studyvista> (raw)
In-Reply-To: <20170317162107.GI5720@mcvoy.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 4331 bytes --]
It has been almost 20 years since I seriously used X remotely. Even then it
was mostly xterms. Almost everything I do in Linux is from bash. I run X
locally mostly if I'm trying to figure out how a new release of Fedora has
changed configuration files -- I run the settings apps to see what they do
to the files. What follows is a bit off-topic from TUHS perspective.
About 1999 I began to need to administer a bunch of Windows servers, mostly
on a local network, sometimes across town, sometimes farther away. I
gravitated to using VNC for Windows and soon used it occasionally for Linux
and, eventually, OS X. My primary desktop environment became Windows, using
PuTTY for ssh.
Back then, my remote access was mostly across POTS (56k) and BRI (128k)
connections.
Since then, I've tried most of the Windows clients and servers. For my
purposes UltraVNC (uvnc.com) is much superior to the others. The client is
robust across remote connections using ssh tunnels. The server was the first
to work reasonably on Vista and tends to keep up with Microsoft better than
the others, in my experience. Tiger (Tight) was my second favorite(s), and I
still use them occasionally, mostly on older machines that I setup before
using Ultra.
The biggest VNC drawbacks from my perspective have been
- security (alleviated by ssh tunneling)
- lack of macOS versions as robust as UltraVNC on Windows
- Windows with RDP interfering with VNC server
With recent macOS, Apple includes a pretty good basic VNC client, “Screen
Sharing”, and a very good VNC server as “Apple Remote Desktop”. Screen
Sharing doesn’t feel as responsive as the better clients on Windows, e.g.,
TightVNC and UltraVNC, and omits refresh options and other useful features.
(Reportedly, there are plans for UltraVNC for macOS. There is a Java version
of TightVNC that will run on macOS, but overall doesn’t seem as responsive
as Screen Sharing. I just discovered while writing this that there is a
TigerVNC dmg, so I plan to try that.)
When I upgraded an XP Pro machine to Vista Pro, I discovered that Vista Pro
wouldn't allow the UltraVNC server to run. That forced me to get acquainted
with RDP, and I was pleasantly surprised.
I knew that RDP had existed, but also knew that RDP was based on ITU-T
T.128. With all the complexity associated with T.120, I had stayed away from
RDP. (20+ years ago I wrote a chapter in Mainstream Videoconferencing,
http://notes.technologists.com/notes/2008/02/14/mainstream-videoconferencing-available-again/,
trying to make T.120 more accessible than the ITU-T docs. The T.128 doc is
at http://www.itu.int/rec/T-REC-T.128-200806-I/en.)
T.120 work started when the principals assumed that videoconferencing over
POTS (H.324) would become prominent, and T.120 was intended to work on POTS
connections. So it is not surprising to think of RDP as "snappy" on cascaded
WiFi connections.
I use RDP quite a bit to access Windows machines that don't allow/interfere
with UltraVNC server. (Just now I tried to get UltraVNC server to work on a
machine running Windows 10 Pro, and failed.)
Besides that Windows VNC interference, the main disadvantage of RDP in my
experience is lack of (freely available?) servers for Windows Home, macOS
and Linux.
When my primary Windows laptop failed, I decided to try a MacBook Pro.
Mostly I've liked it and have liked the RDP client. Some people disparage
the (Microsoft supplied) RDP client as inferior to the Windows client. The
specifics of their complaints don't matter on my MacBook, but I can imagine
they would be bothersome on an iMac or other larger screen.
Charlie
-----Original Message-----
From: Larry McVoy
Sent: Friday, March 17, 2017 11:21 AM
To: Arthur Krewat
Cc: tuhs at minnie.tuhs.org
Subject: Re: [TUHS] X, Suntools, and the like
On Fri, Mar 17, 2017 at 10:39:21AM -0400, Arthur Krewat wrote:
>
> On 3/16/2017 8:13 PM, Larry McVoy wrote:
> >I'd be stoked if X11 had an RDP extension or something. I have no idea if
> >that makes sense but RDP is the shit.
>
> Check out VNC - you run a "server" on the remote side, and the VNC client
> on
> the client side. The advantage is that everything you run stays running on
> the remote side.
Unless VNC has evolved it's just nowhere near as snappy as RDP. Can anyone
speak to that?
next prev parent reply other threads:[~2017-03-17 21:39 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-14 18:49 [TUHS] " Ron Natalie
[not found] ` <CAH1jEzY5g6zGSxsXEHc+Q7mYyegU+aSr-zpfJ0cwRfSGSUdgCg@mail.gmail.com>
[not found] ` <CAH1jEzb7eSr0xcoBX8bfzL6batBfxOF+8jhbVFs=x1CFWAJ65g@mail.gmail.com>
[not found] ` <CAH1jEzY38dmbASRLMrQnoX0-eANA0YBW=j=LLC1y1axi=672yg@mail.gmail.com>
[not found] ` <CAH1jEzbYS8fJgNGFMa+2SoLUWCQQAxVSuxrZp-z2uunXS+R8GQ@mail.gmail.com>
[not found] ` <CAH1jEza89JHeTZBQ6y_wvu7iVjW+qV2_Ucg1gWbWnhG2Jc9rLg@mail.gmail.com>
[not found] ` <CAH1jEzaZxATj5BPu2+d213PpUQqH8Q0LnA2syXxCm4LvpXPqYg@mail.gmail.com>
[not found] ` <CAH1jEza6NO3UcZsR4foQwqFosJWRdYCn5FQfxDy596Nj_+SKdA@mail.gmail.com>
[not found] ` <CAH1jEzYK04=fDQ8FAu2PvKS=heZK_Da=LB=cQ4g9nZybM-DsMA@mail.gmail.com>
[not found] ` <CAH1jEzYMRu_e4Az1+Ns7JA0K5FUjRCrvjOkWVC85WodtLaB52g@mail.gmail.com>
[not found] ` <CAH1jEzZQXAS+bwqV76J8_WkUD-3tR7P_z-mQrRkFv-Khm-R4Eg@mail.gmail.com>
[not found] ` <CAH1jEzY2L1k4_QNUFtscovpD1_gORPRVY_=n47dmBY3fh=JUXA@mail.gmail.com>
[not found] ` <CAH1jEza5F4oyQ8bByypWevLW3RwZ4Q4Zfz-roiGi5ksyGup9Zw@mail.gmail.com>
[not found] ` <CAH1jEzb9Rv+iER45NSCGfFerrXaD1v8PN=j92iOg7oU=4q62Rw@mail.gmail.com>
[not found] ` <CAH1jEzav9Y0vM75GaVqVBj=0nXmjdjucF+mx=FBkRO4QP8Soeg@mail.gmail.com>
2017-03-15 1:13 ` Nick Downing
2017-03-15 10:15 ` Tim Bradshaw
[not found] ` <CAH1jEzb7tKSa5H_k-pCT_7x6xzJHdavm4dZySnhkmYL7WG2HEA@mail.gmail.com>
[not found] ` <CAH1jEza9jmb09SDvQi5cQV_g6oO97dgx-VsQobMG=RddqRBxsA@mail.gmail.com>
2017-03-15 11:03 ` Nick Downing
2017-03-15 12:03 ` tfb
2017-03-15 13:12 ` Nick Downing
2017-03-15 14:37 ` tfb
2017-03-15 16:40 ` Kurt H Maier
2017-03-15 16:52 ` Arthur Krewat
2017-03-16 23:04 ` Josh Good
2017-03-16 23:29 ` Robert Swierczek
2017-03-17 1:15 ` Nick Downing
2017-03-16 23:29 ` Lyndon Nerenberg
2017-03-17 0:05 ` Lyndon Nerenberg
2017-03-17 5:55 ` arnold
2017-03-17 12:56 ` Ron Natalie
2017-03-17 15:19 ` Tim Bradshaw
2017-03-17 20:17 ` Josh Good
2017-03-17 20:30 ` Ron Natalie
2017-03-17 20:44 ` Lyndon Nerenberg
2017-03-17 21:08 ` Dan Cross
2017-03-17 22:50 ` Lyndon Nerenberg
2017-03-17 22:58 ` Dan Cross
2017-03-17 23:17 ` Lyndon Nerenberg
2017-03-17 23:22 ` Lyndon Nerenberg
2017-03-18 15:45 ` Steffen Nurpmeso
2017-03-18 16:59 ` Andy Kosela
2017-03-18 23:05 ` Steffen Nurpmeso
2017-03-18 23:32 ` Nick Downing
2017-03-19 7:20 ` Jason Stevens
2017-03-17 0:13 ` Larry McVoy
2017-03-17 3:16 ` jsteve
2017-03-23 19:16 ` Michael Parson
2017-03-17 12:39 ` Steffen Nurpmeso
2017-03-17 12:45 ` Steffen Nurpmeso
2017-03-17 16:49 ` Tony Finch
2017-03-18 15:43 ` Steffen Nurpmeso
2017-03-17 14:39 ` Arthur Krewat
2017-03-17 16:21 ` Larry McVoy
2017-03-17 16:29 ` Tim Bradshaw
2017-03-17 17:42 ` Steve Nickolas
2017-03-17 21:39 ` Charles H Sauer [this message]
2017-03-19 6:11 ` Robert Brockway
2017-03-19 11:56 ` Josh Good
2017-03-15 20:48 ` Ron Natalie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DA776143C9A6490296D7DFC201A3155C@studyvista \
--to=sauer@technologists.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).