Looking for some suggestions on what works well for RDP/VNC
connections between two Linux boxes, both running GUI (X). Not
interested in anything for Windows, just Linux-to-Linux.
What's your favorite? Thanks for ideas.
Looking for some suggestions on what works well for RDP/VNC
connections
between two Linux boxes, both running GUI (X). Not interested in
anything for Windows, just Linux-to-Linux.
What's your favorite? Thanks for ideas.
Gerrit Kuehn wrote to Dan Clough <=-
Looking for some suggestions on what works well for RDP/VNC
connections
between two Linux boxes, both running GUI (X). Not interested in
anything for Windows, just Linux-to-Linux.
What's your favorite? Thanks for ideas.
Do you want persistent logins? Do you want access to the physical X display (:0), virtual ones, or both? Looking for the client or the
server end (or both)?
If VNC and RDP above are not a requirement (but merely examples): I am using x2go for a couple of years now (and try to avoid the other two,
if possible).
Karel Kral wrote to Dan Clough <=-
Looking for some suggestions on what works well for RDP/VNC
connections between two Linux boxes, both running GUI (X). Not
interested in anything for Windows, just Linux-to-Linux.
What's your favorite? Thanks for ideas.
"both running X" - for that I am using X forwarding via ssh.
Looking for some suggestions on what works well for RDP/VNC connections between two Linux boxes, both running GUI (X). Not interested in
anything for Windows, just Linux-to-Linux.
What's your favorite? Thanks for ideas.
Mike Powell wrote to DAN CLOUGH <=-
Looking for some suggestions on what works well for RDP/VNC connections between two Linux boxes, both running GUI (X). Not interested in
anything for Windows, just Linux-to-Linux.
What's your favorite? Thanks for ideas.
Have you tried Remmina? Seems to work well here. It requres that an
RDP server be running on the machine you want to make the connection
to. I use xrdp for that.
So far the majority of issues I have had are either user error or a network glitch.
Do you want persistent logins? Do you want access to the physical X
display (:0), virtual ones, or both? Looking for the client or the
server end (or both)?
Don't even know enough about it to answer the first two questions...
If VNC and RDP above are not a requirement (but merely examples): I
am using x2go for a couple of years now (and try to avoid the other
two, if possible).
I'm assuming you avoid VNC/RDP for security reasons...
I've added x2go to my list of candidates, and it looks pretty good.
"both running X" - for that I am using X forwarding via ssh.
Ahhhh yes, that may be the simplest approach. Thank you.
Gerrit Kuehn wrote to Dan Clough <=-
Hello Dan!
07 Jun 25 08:50, Dan Clough wrote to Gerrit Kuehn:
Do you want persistent logins? Do you want access to the physical X
display (:0), virtual ones, or both? Looking for the client or the
server end (or both)?
Don't even know enough about it to answer the first two questions...
There is a difference if you want to share your physical display, i.e., the session that is displayed on the monitor connected to the server,
or if you want a "virtual" session that is running on the server with
no monitor hardware attached. Some software can do one, some the other, some both.
Which software you want depends on what you want to achieve: using the physical display remotely is more or less required if you want to give users in front of the machine remote help, i.e., see their screens,
move their mouse, type for them. OTOH, running virtual session enables
you to hook up several remote users to a server, everyone running their own session. This way, you could, for example, use a more powerful
server to run several (virtual) desktop environment sessions, each of these being displayed by a less powerful thin client.
Having "persistent" logins means that your virtual session (with all software running) is not automatically terminated when your client disconnects. Instead, it is waiting on the server until your client reconnects (which could be days later). If you are familiar with tools like "screen" or "tmux" on the commandline (or in xterm): persistent virtual X sessions are pretty much the same concept, just using X
sessions (including your full desktop if you like) instead of a
textmode terminal.
If VNC and RDP above are not a requirement (but merely examples): I
am using x2go for a couple of years now (and try to avoid the other
two, if possible).
I'm assuming you avoid VNC/RDP for security reasons...
Well, depends on the actual setup and software you use, I guess. I probably would not recommend the original VNC ("realvnc") to anyone
these days. TightVNC or TigerVNC usually perform better, provide more features and better security. RDP, on the other hand, was invented by
MS. At least for me, especially the server part always felt tedious to
set up and clumsy to operate. This is probably caused by its "alien"
(from *ix-perspective) origin. Admittedly, I have not used it for quite some time, maybe it improved meanwhile. I am using it on *ix systems as
a client (remmina being my default client there) when I have to talk to
MS servers. However, I would avoid the server on *ix systems if I have other choices.
I've added x2go to my list of candidates, and it looks pretty good.
I have used x2go in various scenarios over the last years, usually
running the server on Linux machines to be able to operate their
software from Windows, MacOS, *BSD oder other Linux boxes. It is reasonably fast, tunnels over ssh by default, supports using SSH key authentication and SSH jump hosts (so you do not have to mess with firewall rules and port forwarding if you already have an ssh port
open), offers session management, persistance, access to the physical X display. On top of that, it is OpenSource and easy to set up, so for me there is not much more to ask for. You have to take care a bit when
using "fancy" desktop environments that come with compositors, transparency and stuff like that. My default desktop is xfce, x2go
usually works fine with it.
Regards,
Gerrit
Hello Dan!
06 Jun 25 19:50, you wrote to All:
Looking for some suggestions on what works well for RDP/VNC
connections between two Linux boxes, both running GUI (X). Not interested in anything for Windows, just Linux-to-Linux.
What's your favorite? Thanks for ideas.
"both running X" - for that I am using X forwarding via ssh.
Karel
But X is slow as a protocol, and really only feasible with a network connection. RDP works better over the internet.
Thank you for your VERY informative post - I found it extremely
helpful indeed. Appreciate you taking the time to explain all of that.
If VNC and RDP above are not a requirement (but merely examples): I am using x2go for a couple of years now (and try to avoid the other two, if possible).
Sysop: | altere |
---|---|
Location: | Houston, TX |
Users: | 69 |
Nodes: | 4 (0 / 4) |
Uptime: | 07:02:59 |
Calls: | 1,188 |
Files: | 8,242 |
Messages: | 302,518 |