From Newsgroup: alt.os.linux

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.


... Why did kamikaze pilots wear helmets?
--- MultiMail/Linux v0.52
--- Synchronet 3.21a-Linux NewsLink 1.2
Palantir BBS - telnet://palantirbbs.ddns.net
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On Fri, 6 Jun 2025 19:50:33 -0500, Gamgee wrote:

Looking for some suggestions on what works well for RDP/VNC connections between two Linux boxes, both running GUI (X).

Are you wanting some kind of remote control over the GUI screen on the
remote machine? Because it’s common, in a server-type situation particularly, not to bother with a GUI on the remote machine at all.
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On Fri, 6/6/2025 8:50 PM, Gamgee wrote:

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.

The people who use these things, seem to get pretty excited about them.

"performant remote desktop for Mac/Linux?"

https://news.ycombinator.com/item?id=32526108

Paul
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

To: Lawrence D'Oliveiro

Lawrence D'Oliveiro wrote to alt.os.linux <=-

Looking for some suggestions on what works well for RDP/VNC connections between two Linux boxes, both running GUI (X).

Are you wanting some kind of remote control over the GUI screen on the remote machine? Because itrCOs common, in a server-type situation particularly, not to bother with a GUI on the remote machine at all.

Well, yes, I know that, but ..... that's what I asked. Yes, remotely controlling the GUI on the "server" is what I'm trying to do.



... Never assume the obvious is true!
--- MultiMail/Linux v0.52
--- Synchronet 3.21a-Linux NewsLink 1.2
Palantir BBS - telnet://palantirbbs.ddns.net
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

To: Paul

Paul wrote to alt.os.linux <=-

Looking for some suggestions on what works well for RDP/VNC connections between two Linux boxes, both running GUI (X).-a Not interested in
anything for Windows, just Linux-to-Linux.
What's your favorite?-a Thanks for ideas.

The people who use these things, seem to get pretty excited about them.

"performant remote desktop for Mac/Linux?"

https://news.ycombinator.com/item?id=32526108

Good info, thanks.



... Gone crazy, be back later, please leave message.
--- MultiMail/Linux v0.52
--- Synchronet 3.21a-Linux NewsLink 1.2
Palantir BBS - telnet://palantirbbs.ddns.net
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On Sat, 07 Jun 2025 08:50:48 -0500, Gamgee wrote:

To: Lawrence D'Oliveiro

Lawrence D'Oliveiro wrote to alt.os.linux <=-

Looking for some suggestions on what works well for RDP/VNC connections between two Linux boxes, both running GUI (X).

Are you wanting some kind of remote control over the GUI screen on the remote machine? Because itrCOs common, in a server-type situation particularly, not to bother with a GUI on the remote machine at all.

Well, yes, I know that, but ..... that's what I asked. Yes, remotely controlling the GUI on the "server" is what I'm trying to do.

I assume that you know that X servers use the X network protocol to automatically
(without additional tools) run a program on one machine and have that program's windows open on another machine, and you chose RDP/VNC because it matters to you
(for some reason) that Microsoft Windows doesn't natively support the X network protocol.

But, just for the record, you don't need VNC or RDP to show a remote system's "desktop" (or even interact with GUI programs running on a remote system); you just need a network between the two and the networking support of the X server enabled.

HTH
--
Lew Pitcher
"In Skills We Trust"
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On 07/06/2025 02.50, Gamgee wrote:

Looking for some suggestions on what works well for RDP/VNC connections

If you have X already up and running on the "hosts", then I would go fo
Xnest, you need to enable XDMCPServer on the host, this is configured in
the Display Manager, say you run lightdm then in lightdm.config you
uncomment so that you have:

[XDMCPServer]
enabled=true
port=177

restart the lightdm service.

then from the clinet you just connect with the following command:

Xnest -query host1.local -geometry 1920x1080 :1

The host1.local you change to the hostname you have in your network or
to the ip-number.

The geometry you to change to the size you want on the window.

The ":1" tells that I want to run this on display 1 on the remote
machine, display in this case has nothing to do with the monitor, it's
the display handled by X which starts on :0 and then goes up depending
on how many sessions you have.
You can't have two displays with the same id open at the same time, so
if you open two connection to the remote machine, then first one may
have :1 and then you need to have at least :2 on the second one.

When the window opens, you will be at the login prompt on the remote
machine, you login with credentials, username and password, as if you
sat at that computer.
--
//Aho


--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

To: J.O. Aho

Looking for some suggestions on what works well for RDP/VNC connections

If you have X already up and running on the "hosts", then I would go fo Xnest, you need to enable XDMCPServer on the host, this is configured
in the Display Manager, say you run lightdm then in lightdm.config you uncomment so that you have:

[XDMCPServer]
enabled=true
port=177

restart the lightdm service.

then from the clinet you just connect with the following command:

Xnest -query host1.local -geometry 1920x1080 :1

The host1.local you change to the hostname you have in your network or
to the ip-number.

The geometry you to change to the size you want on the window.

The ":1" tells that I want to run this on display 1 on the remote machine, display in this case has nothing to do with the monitor, it's
the display handled by X which starts on :0 and then goes up depending
on how many sessions you have.
You can't have two displays with the same id open at the same time, so
if you open two connection to the remote machine, then first one may
have :1 and then you need to have at least :2 on the second one.

When the window opens, you will be at the login prompt on the remote machine, you login with credentials, username and password, as if you
sat at that computer.

Thank you. Very helpful information, and I appreciate you taking the
time to post it.



... Gone crazy, be back later, please leave message.
--- MultiMail/Linux v0.52
--- Synchronet 3.21a-Linux NewsLink 1.2
Palantir BBS - telnet://palantirbbs.ddns.net
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

To: Lew Pitcher

Looking for some suggestions on what works well for RDP/VNC connections between two Linux boxes, both running GUI (X).

Are you wanting some kind of remote control over the GUI screen on the remote machine? Because itrCOs common, in a server-type situation particularly, not to bother with a GUI on the remote machine at all.

Well, yes, I know that, but ..... that's what I asked. Yes, remotely controlling the GUI on the "server" is what I'm trying to do.

I assume that you know that X servers use the X network protocol to automatically (without additional tools) run a program on one machine
and have that program's windows open on another machine, and you chose RDP/VNC because it matters to you (for some reason) that Microsoft
Windows doesn't natively support the X network protocol.

Well, I mentioned RDP/VNC because I thought that's how you connected to
a remote GUI from a local GUI. I don't care about any Windows details,
as I don't have/use Windows.

But, just for the record, you don't need VNC or RDP to show a remote system's "desktop" (or even interact with GUI programs running on a
remote system); you just need a network between the two and the
networking support of the X server enabled.

I'll assume you're talking about X-forwarding over SSH, which I do know
about but don't wish to use in this instance. Thanks for the reply.



... Gone crazy, be back later, please leave message.
--- MultiMail/Linux v0.52
--- Synchronet 3.21a-Linux NewsLink 1.2
Palantir BBS - telnet://palantirbbs.ddns.net
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On 7/06/2025 11:50 pm, Gamgee wrote:

 To: Lawrence D'Oliveiro

Lawrence D'Oliveiro wrote to alt.os.linux <=-

Looking for some suggestions on what works well for RDP/VNC connections between two Linux boxes, both running GUI (X).

Are you wanting some kind of remote control over the GUI screen on the remote machine? Because itrCOs common, in a server-type situation particularly, not to bother with a GUI on the remote machine at all.

Well, yes, I know that, but .....  that's what I asked.  Yes, remotely controlling the GUI on the "server" is what I'm trying to do.

I know bugger all about Servers .... but I would HAVE to ask .... If you
are REMOTE from the server, WHY do you need any Display at the server??

Sure, when you are AT the Server, doing maintenance or whatever, sure,
but if you're not there .......!
--
Daniel70
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On Sun, 6/8/2025 4:55 AM, Daniel70 wrote:

On 7/06/2025 11:50 pm, Gamgee wrote:

  To: Lawrence D'Oliveiro

Lawrence D'Oliveiro wrote to alt.os.linux <=-

Looking for some suggestions on what works well for RDP/VNC connections >>  > between two Linux boxes, both running GUI (X).

Are you wanting some kind of remote control over the GUI screen on the >> LD> remote machine? Because itrCOs common, in a server-type situation
particularly, not to bother with a GUI on the remote machine at all.

Well, yes, I know that, but .....  that's what I asked.  Yes, remotely controlling the GUI on the "server" is what I'm trying to do.

I know bugger all about Servers .... but I would HAVE to ask .... If you are REMOTE from the server, WHY do you need any Display at the server??

Sure, when you are AT the Server, doing maintenance or whatever, sure, but if you're not there .......!

The best way for you to investigate this, is set up a Ubuntu Server
on one machine, and a client OS on another machine, and try and
maintain the Ubuntu Server. The server could be set up headless.
It could be without a DE. If you install Ubuntu Server, that
has a few things missing compared to a Client Install. I used to
add Xorg to that for example, and build up the client stack, as
practice.

Remote could mean, in a COLO, and at a much longer distance.
The computer in that case, is under lock and key and you never
ever get to see the rental computer in person. Unless the
building burned up (which did happen to one datacenter and
I couldn't imagine what the fuel load for the fire was in
that case). People in COLOs, seem to lack backups. That's
one of the advantage of home computing, YOU CAN MAKE BACKUPS :-)
Have at least one spare drive for emergencies. Two spare
drives, for data recovery operations (eg. your laptop right now).

Server motherboards usually have an AST graphics chip, which
is a frame buffer. If you pull out a tray in the rack with a monitor on it,
you can plug into the AST and have graphics. But the graphics
might only consist of a terminal session. Not unless you've added
the software you're not supposed to add, does the server get a GUI.

Paul
--- Synchronet 3.21a-Linux NewsLink 1.2