I'm using the X2Go client build 3.99.1.1 on a Windows 7 x64 system. I can connect to individual servers just fine but when I try to run simultaneous client sessions the first session stops receiving data and eventually disconnects.
Is this a known limitation of the x2go client? Is there some trick to getting multiple sessions working correctly? Regards,
Shelby Cain
On Thu, 2012-03-22 at 11:11 -0400, scain@exgenesis.com wrote:
I'm using the X2Go client build 3.99.1.1 on a Windows 7 x64 system. I can connect to individual servers just fine but when I try to run simultaneous client sessions the first session stops receiving data and eventually disconnects.
Is this a known limitation of the x2go client? Is there some trick to getting multiple sessions working correctly?
<snip> Just to make sure I understand, I assume you are running multiple client instances on the same physical desktop but are your trying to connect those multiple clients to the same X2Go server (different users) or to different X2Go servers? Thanks - John
On March 22, 2012 at 12:28 PM "John A. Sullivan III" <jsullivan@opensourcedevel.com> wrote:
On Thu, 2012-03-22 at 11:11 -0400, scain@exgenesis.com wrote:
Is this a known limitation of the x2go client? Is there some trick to getting multiple sessions working correctly?
<snip> Just to make sure I understand, I assume you are running multiple client instances on the same physical desktop but are your trying to connect those multiple clients to the same X2Go server (different users) or to different X2Go servers? Thanks - John
Sorry for being unclear. I am running multiple client instances on the same physical desktop but they are each connecting to a different remote host. However, the user name is the same for each host if that is at all relevant.
Regards,
Shelby Cain
On Thu, 2012-03-22 at 13:12 -0400, scain@exgenesis.com wrote:
On March 22, 2012 at 12:28 PM "John A. Sullivan III" <jsullivan@opensourcedevel.com> wrote:
On Thu, 2012-03-22 at 11:11 -0400, scain@exgenesis.com wrote:
Is this a known limitation of the x2go client? Is there some
trick to
getting multiple sessions working correctly?
<snip> Just to make sure I understand, I assume you are running multiple client instances on the same physical desktop but are your trying to connect those multiple clients to the same X2Go server (different users) or to different X2Go servers? Thanks - John
Sorry for being unclear. I am running multiple client instances on the same physical desktop but they are each connecting to a different remote host. However, the user name is the same for each host if that is at all relevant.
<snip> Ok - I do wish X2Go handled that a little more elegantly. It may be on a to do list somewhere. In the meantime, the work around is to manually edit /usr/bin/x2gostartagent (and remember to edit it after every upgrade - it would be a little better if this was a configurable option) and change a couple of parameters:
#X2GO_PORT=49 #First port for X2GO=50 #SSH_PORT=30000 #First ssh port 30001 X2GO_PORT=59 SSH_PORT=30020
In other words, set the different X2Go servers to start on different SSH ports. I do not recall if different X2Go ports are necessary. Does that help? Good luck - John
On March 22, 2012 at 1:49 PM "John A. Sullivan III" <jsullivan@opensourcedevel.com> wrote:
Ok - I do wish X2Go handled that a little more elegantly. It may be on a to do list somewhere. In the meantime, the work around is to manually edit /usr/bin/x2gostartagent (and remember to edit it after every upgrade - it would be a little better if this was a configurable option) and change a couple of parameters:
#X2GO_PORT=49 #First port for X2GO=50 #SSH_PORT=30000 #First ssh port 30001 X2GO_PORT=59 SSH_PORT=30020
In other words, set the different X2Go servers to start on different SSH ports. I do not recall if different X2Go ports are necessary. Does that help? Good luck - John
I just tried your suggestion and modified only the SSH_PORT parameter and it appears to work perfectly - thanks!
I can certainly live with this work-around for the time being. If I get some free time I may fiddle with moving the SSH_PORT option into /etc/x2go/x2goconfig and submit a patch.
Regards,
Shelby Cain