remote desktop solution

[seacliff]

Hello,

I am looking at a remote desktop solution for RHEL systems. I would need a solution similar to windows RPD where you can connect to the server, then log in using ldap credential. SSH isn't a solution since I need the desktop to show, neither vnc since I need 1 process per user and each user would have their own specific desktop number.

Is there such a thing?

[atreyu]

Actually, I believe VNC is what you want. VNC for Windows operates differently than VNC for Linux - the former allows you control of the local desktop display (:0), the latter starts a server on a separate display (:1 thru :N). These days, you can of course control the local desktop display in Linux, but that's not what you want.

Just set up your VNC sessions first (create VNC passwords for each user and optionally a custom VNC startup script), then populate /etc/sysconfig/vncservers properly, then start the VNC server, and you're done.

For example, to manually set up a couple VNC users, you might do:

su - user1
vncpasswd
vncserver :1
exit
su - user2
vncpasswd
vncserver :2
exit

Normally, I would create/edit the ~/.vnc/xstartup script to run a light-weight window manger (fluxbox, blackbox, etc.) instead of the default (gnome, kde, etc.).

[seacliff]

I tried the vnc route, but it's not quite what I want. I don't want to manage the desktop display for each user.

The reason behind this is, I've got a couple of thinclient, and I don't want to have multiple connection to reflect all users, or have a specific thinclient for each user. I would rather have a bunch of thinclient and a bunch of users, and have a single instruction on how to connect to their RHEL desktop.

[seacliff]

After digging a little more, I found a way. The XDMCP protocol does exactly what I want. GDM manage the desktop display number and any user who can log in to the machine can log in using XDMCP. That means 1 configuration, no management.

[atreyu]

Yes, good call. I've actually got that set up myself, right now, but I rarely use it b/c I'm always VNCing everywhere...forgot about it, d'oh.

[seacliff]

Yes, good call. I've actually got that set up myself, right now, but I rarely use it b/c I'm always VNCing everywhere...forgot about it, d'oh.

No problem there, I found it and that's all what's matter

[Siddly]

No problem there, I found it and that's all what's matter

Just what I would have recommended. I have used it over many years to manage multiple domains on large Solaris systems, assigning each to :1, :2, :3 and switching between them with CTRL-ALT-F8, CTRL-ALT-F9, etc. and CTRL-ALT-F7 back to my linux desktop.

[jselover]

A caveat to XDMCP is its very poor WAN performance. If your users are connecting from distant locations, look into the NX desktop server/client.
Look for these, or newer, free version NX server rpms for your RHEL release:
nx-3.3.0-38.el6
freenx-server-0.7.3-18.el6

Install the rpms and run as root:
export PATH=/usr/libexec/nx;$PATH # so nxsetup can find its files
/usr/share/doc/freenx-server-0.7.3/nxsetup # to create keys and config files.

The NX client is available for Mac, Linux, and Windows, so your clients can be almost anything. NX works fine over any connection LAN or WAN.
Just search for NXClient download, and you will find the client install packages.

[seacliff]

Just what I would have recommended. I have used it over many years to manage multiple domains on large Solaris systems, assigning each to :1, :2, :3 and switching between them with CTRL-ALT-F8, CTRL-ALT-F9, etc. and CTRL-ALT-F7 back to my linux desktop.

I wouldn't mind doing so myself, but I can't ask multiple users to change desktop manually

A caveat to XDMCP is its very poor WAN performance. If your users are connecting from distant locations, look into the NX desktop server/client.
Look for these, or newer, free version NX server rpms for your RHEL release:

This is not an issue. I am on a 1G network with 10G backbone.

The NX client is available for Mac, Linux, and Windows, so your clients can be almost anything. NX works fine over any connection LAN or WAN.
Just search for NXClient download, and you will find the client install packages.

I've looked that direction, but I can't since thinclient have a limited amount of protocol implemented.

[Siddly]

A caveat to XDMCP is its very poor WAN performance. If your users are connecting from distant locations, look into the NX desktop server/client.
Look for these, or newer, free version NX server rpms for your RHEL release:
nx-3.3.0-38.el6
freenx-server-0.7.3-18.el6

Install the rpms and run as root:
export PATH=/usr/libexec/nx;$PATH # so nxsetup can find its files
/usr/share/doc/freenx-server-0.7.3/nxsetup # to create keys and config files.

The NX client is available for Mac, Linux, and Windows, so your clients can be almost anything. NX works fine over any connection LAN or WAN.
Just search for NXClient download, and you will find the client install packages.

Quite true about xdmcp - I experienced this when I tried to connect from home over a VPN link to a Solaris console some 100 miles away to look at logs.
It took an age and I had to cancel it.