Hi Mike,
My usecases are:
I am working on computer A. Then I change room and want to continue working from computer B on the desktop of computer A. So that would be your case (a).
I am working on computer A. I want to show some results on my screen to my colleague in the U.S. or in the next cubical, in any case in the same network. I think that would be exactly your case (b).
Summarized you described exactly my usecases. Now the interesting question: How can I do that? Did I overlook something in the Wiki or is there another documentation?
Thank you for your patience. Best regards Axel
Hi Axel,
x2godesktopsharing can be used to
(a) view and use (full access) your own desktop session from two or more
locations
(b) to view someone else's desktop session (view-only mode)As your former posting did not hint to any of the above use cases, I suggest you describe what you want to do with X2go more precisely. There will definitely be a solution for your needs, but I need more details to help.
Greets, Mike
Hi Axel,
On Di 12 Apr 2011 19:23:48 CEST Axel Klein wrote:
Hi Mike,
My usecases are:
- I am working on computer A. Then I change room and want to
continue working from computer B on the desktop of computer A. So
that would be your case (a).
Currently, it is not possible to start X2go sessions on localhost. So
your usecase 1) could be:
You sit at computer A and start an X2go session on server S. Then you
suspend your session and start and resume the same X2go session on
computer B. This is X2go default functionality.
In the process of starting a session, suspending it, resuming it from
another PC - do you have any difficulty with any of these?
Note again: sitting at computer A and starting an X2go session on
computer A is currently not possible.
- I am working on computer A. I want to show some results on my
screen to my colleague in the U.S. or in the next cubical, in any
case in the same network. I think that would be exactly your case (b).Summarized you described exactly my usecases. Now the interesting question: How can I do that? Did I overlook something in the Wiki or is there another documentation?
The second usecase is more tricky than the first. X2go shadow session
(that's what the guest user sessions are called) have only been
implemented quite recently. They are not available in the lenny
repositories. Use these two (both!) line in /etc/apt/sources.list (on
server and linux clients):
deb http://x2go.obviously-nice.de/deb lenny main deb http://x2go.obviously-nice.de/deb heuler main
On the server you currently have to install (this will change in the
near future):
Debian:
apt-get install x2goserver-one x2godesktopsharing x2gognomebindings
x2goplasmoid
Ubuntu:
apt-get install x2goserver-home x2godesktopsharing x2gognomebindings
x2goplasmoid
On the client you simply need the x2goclient package:
apt-get install x2goclient
YOU:
On the server you have to start the x2godesktopsharing util that will
dock to your systray panel. Make sure you allow other to knock on your
door.
YOUR GUEST:
The guest user first of all needs an SSH account on the X2go server.
Hope, this is not a hurdle. The guest user then has to start a
shared/shadow session from his local x2goclient app. The session name
for this in the session profile preference is:
,,Connect to local desktop'' ,,Zugriff auf lokalen Desktop'' in Deutsch
So, instead of using GNOME or KDE your guest user has to use either of
the above with the hostname, port, username etc. of your X2go server.
If the guest user then starts a session, he/she will knock on your
x2godesktopsharing icon virtual door and you can decide to let him/her
in or not.
Greets & good luck, Mike
PS: as an exchange of time and energy you could test the described
above, fix bits and pieces and then post it back to the list so that
we can set up a Wiki page for x2godesktopsharing... :-)
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
On Tue, 2011-04-12 at 20:56 +0200, Mike Gabriel wrote:
Hi Axel, <snip> The second usecase is more tricky than the first. X2go shadow session
(that's what the guest user sessions are called) have only been
implemented quite recently. They are not available in the lenny
repositories. Use these two (both!) line in /etc/apt/sources.list (on
server and linux clients):deb http://x2go.obviously-nice.de/deb lenny main deb http://x2go.obviously-nice.de/deb heuler main
On the server you currently have to install (this will change in the
near future):Debian: apt-get install x2goserver-one x2godesktopsharing x2gognomebindings
x2goplasmoidUbuntu: apt-get install x2goserver-home x2godesktopsharing x2gognomebindings
x2goplasmoidOn the client you simply need the x2goclient package:
apt-get install x2goclient
YOU:
On the server you have to start the x2godesktopsharing util that will
dock to your systray panel. Make sure you allow other to knock on your
door.YOUR GUEST:
The guest user first of all needs an SSH account on the X2go server.
Hope, this is not a hurdle. The guest user then has to start a
shared/shadow session from his local x2goclient app. The session name
for this in the session profile preference is:,,Connect to local desktop'' ,,Zugriff auf lokalen Desktop'' in Deutsch
So, instead of using GNOME or KDE your guest user has to use either of
the above with the hostname, port, username etc. of your X2go server.If the guest user then starts a session, he/she will knock on your
x2godesktopsharing icon virtual door and you can decide to let him/her
in or not. <snip> We take a slightly different approach - and that is exactly what it is - different - not better or worse. In our case, we want our users working in their virtual desktops all the time and the virtual desktops are all accessed across the Internet. Thus, we did not want users to have to leave their virtual desktops to open another X2Go session in shadow mode. Instead, we placed "share desktop" and "View Another Desktop" icons on their virtual desktops which use X11VNC to share the active desktop. Thus, all activity is from within the virtual desktops.
Since the VNC connection is inside the LAN (between virtual desktops), the performance is very good and we gain the Internet boost from NX for VNC just like we do for RDP when we push Terminal Server sessions through NX. Just another way for those with environments similar to ours - John
On Di 12 Apr 2011 21:32:23 CEST "John A. Sullivan III" wrote:
We take a slightly different approach - and that is exactly what it is - different - not better or worse. In our case, we want our users working in their virtual desktops all the time and the virtual desktops are all accessed across the Internet. Thus, we did not want users to have to leave their virtual desktops to open another X2Go session in shadow mode. Instead, we placed "share desktop" and "View Another Desktop" icons on their virtual desktops which use X11VNC to share the active desktop. Thus, all activity is from within the virtual desktops.
Since the VNC connection is inside the LAN (between virtual desktops), the performance is very good and we gain the Internet boost from NX for VNC just like we do for RDP when we push Terminal Server sessions through NX. Just another way for those with environments similar to ours - John
This sounds nice!!!!
Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
On Tue, 2011-04-12 at 21:50 +0200, Mike Gabriel wrote:
On Di 12 Apr 2011 21:32:23 CEST "John A. Sullivan III" wrote:
We take a slightly different approach - and that is exactly what it is - different - not better or worse. In our case, we want our users working in their virtual desktops all the time and the virtual desktops are all accessed across the Internet. Thus, we did not want users to have to leave their virtual desktops to open another X2Go session in shadow mode. Instead, we placed "share desktop" and "View Another Desktop" icons on their virtual desktops which use X11VNC to share the active desktop. Thus, all activity is from within the virtual desktops.
Since the VNC connection is inside the LAN (between virtual desktops), the performance is very good and we gain the Internet boost from NX for VNC just like we do for RDP when we push Terminal Server sessions through NX. Just another way for those with environments similar to ours - John
This sounds nice!!!!
Mike
It's actually very similar to the X2Go desktop sharing as I believe that also uses VNC rather than NX for the shadow session. The main difference is whether one shadows from one's physical desktop or one's virtual desktop. Thanks - John
Hi John,
On Di 12 Apr 2011 22:00:15 CEST "John A. Sullivan III" wrote:
On Tue, 2011-04-12 at 21:50 +0200, Mike Gabriel wrote:
On Di 12 Apr 2011 21:32:23 CEST "John A. Sullivan III" wrote:
We take a slightly different approach - and that is exactly what it is - different - not better or worse. In our case, we want our users working in their virtual desktops all the time and the virtual desktops are all accessed across the Internet. Thus, we did not want users to have to leave their virtual desktops to open another X2Go session in shadow mode. Instead, we placed "share desktop" and "View Another Desktop" icons on their virtual desktops which use X11VNC to share the active desktop. Thus, all activity is from within the virtual desktops.
Since the VNC connection is inside the LAN (between virtual desktops), the performance is very good and we gain the Internet boost from NX for VNC just like we do for RDP when we push Terminal Server sessions through NX. Just another way for those with environments similar to ours - John
This sounds nice!!!!
Mike
It's actually very similar to the X2Go desktop sharing as I believe that also uses VNC rather than NX for the shadow session. The main difference is whether one shadows from one's physical desktop or one's virtual desktop. Thanks - John
Hmmm... AFAIK the X2go shadow session stuff is actually an NX feature
that is just utilized by X2go. But that, though, is internally
probably some VNC'ish stuff...
Greets, Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
-
Axel Klein -
John A. Sullivan III -
Mike Gabriel