action #9504
closed[desktop]Remote Desktop Testing
60%
Description
First, the "server side":
6 potential server flavors:
SLES system with ssh enabled
SLES system, with xvnc enabled (running yast2 remote management to
enable the VNC system part)SLES system, with xvnc already enabled. Then, install xrdp, to make
SLES being available as RDP server.SLES system with XDMCP enabled in gdm (we could also test xdm in
addition)
(the SLES system can be a single system with all possible remote access
enabled, it will work fine, you just need to be careful with VNC entry
point)
Windows (could be 7, 8 or 10, don't care). Need to do a install with
a password on the user and then enable RDP support in it. You need to
disable NLA (Network Authentication Layer) on Windows, we don't yet
support it in SP1, will do for SP2)SLED (or SLES + WE) system, with logged user, then enabling vino
desktop sharing from GNOME.
2 client flavors:
SLED system, with vinagre, tigervnc and Xephyr installed
Windows (can be the same as the server one)
test matrix:
XDMCP:
- from SLED system, try to run Xephyr -query to check if you get gdm prompt on the SLES server
X11 over SSH:
- from SLED system, login to SLES over ssh and try to run a graphical application (gedit for instance).
VNC:
- connecting from SLED to SLES XVNC: test with both vinagre and tigervnc
- connecting from SLED to SLES XVNC, but using Firefox and Java applet
- connecting from SLED to SLES over Vino: user must be first logged on SLES server, in order to SLED to take control of the desktop session on SLES (should be tested from vinagre in priority, but also test it from tigervnc)
RDP:
- connecting from Windows (as client) to SLES over RDP: use Windows built-in Remote desktop client and ensure you get sessman session chooser and try to login. This should bring up gdm, similar to XVNC
- connecting from SLED to Windows (as server): use vinagre to connect on Windows session => for this one, you will need to use "--no-nla" to connect to Windows, in the options field in Vinagre.