I am only able to keep one session of x2go open at a time. When I start a new client, the first session terminates by itself. I restart it, and the other session terminates. These are to two separate hosts. On both ends is Debian Testing, kept current. [1]merc1984@f-m.fm
References
- mailto:merc1984@f
-- http://www.fastmail.fm - Access all of your messages and folders wherever you are
I am only able to keep one session of x2go open at a time. When I start a new client, the first session terminates by itself. I restart it, and the other session terminates. These are to two separate hosts. On both ends is Debian Testing, kept current.
Could be a TCP port conflict. Try changing the value for SSH_PORT to 30200 in /usr/bin/x2gostartagent on one of the target machines so they are using different port ranges. End all X2Go sessions (not just disconnect, log out) before you try again.
Cheers, Daniel
On Mon, Jul 9, 2012, at 06:32, Daniel Lindgren wrote:
Could be a TCP port conflict. Try changing the value for SSH_PORT to 30200 in /usr/bin/x2gostartagent on one of the target machines so they are using different port ranges. End all X2Go sessions (not just disconnect, log out) before you try again.
I don't see how it could be a port conflict, as one is addressed at 192.168.1.3:22 and the other at 192.168.1.4:22.
Unless the problem is on the client end trying to access the two through some common channel. But if this were the case, it wouldn't have worked before and it did. I could have two sessions open on the laptop to two different destination machines.
I don't think it's that SSH can only do one session as I can ssh to a target while the x2go client is running, and anyway the ssh servers are on different machines.
-- http://www.fastmail.fm - Access all of your messages and folders wherever you are
On Mon, Jul 9, 2012 at 12:09 AM, <merc1984@f-m.fm> wrote:
On Mon, Jul 9, 2012, at 06:32, Daniel Lindgren wrote:
Could be a TCP port conflict. Try changing the value for SSH_PORT to 30200 in /usr/bin/x2gostartagent on one of the target machines so they are using different port ranges. End all X2Go sessions (not just disconnect, log out) before you try again.
I don't see how it could be a port conflict, as one is addressed at 192.168.1.3:22 and the other at 192.168.1.4:22.
Unless the problem is on the client end trying to access the two through some common channel. But if this were the case, it wouldn't have worked before and it did. I could have two sessions open on the laptop to two different destination machines.
I don't think it's that SSH can only do one session as I can ssh to a target while the x2go client is running, and anyway the ssh servers are on different machines.
How does x2go handle the display numbers? I know that with freenx/nx, I have to set the DISPLAY_BASE to different values on each host to be able to have concurrent sessions to multiple hosts from the same nx client at least when I am the 1st session on each.
-- Les Mikesell lesmikesell@gmail.com
On Sun, 2012-07-08 at 22:09 -0700, merc1984@f-m.fm wrote:
On Mon, Jul 9, 2012, at 06:32, Daniel Lindgren wrote:
Could be a TCP port conflict. Try changing the value for SSH_PORT to 30200 in /usr/bin/x2gostartagent on one of the target machines so they are using different port ranges. End all X2Go sessions (not just disconnect, log out) before you try again.
I don't see how it could be a port conflict, as one is addressed at 192.168.1.3:22 and the other at 192.168.1.4:22.
Unless the problem is on the client end trying to access the two through some common channel. But if this were the case, it wouldn't have worked before and it did. I could have two sessions open on the laptop to two different destination machines.
I don't think it's that SSH can only do one session as I can ssh to a target while the x2go client is running, and anyway the ssh servers are on different machines.
It's a problem on the client side. That's why changing the port to be different on one host from another host fixes the problem.
However, it was not always this way. The older clients (e.g., 3.0.1-4) accidentally supported multiple connections without having to fiddle with the server settings.
We would very much like to see a reversion to the old behavior. We have been pushing the concept of Content Networks, i.e., rather than have a single computer in which one tries to shoe horn all one's activities, have multiple virtual desktops for major, e.g., engineering firms providing outsourced services to multiple firms, PR and advertising firm with account managers handling multiple accounts - wherever intensive collaboration needs to happen across corporate boundaries.
Not being able to run multiple X2Go clients with default server settings is a real pain for us. Thanks for pointing it out - John
On Mon, Jul 9, 2012, at 06:32, Daniel Lindgren wrote:
I am only able to keep one session of x2go open at a time. When I start a new client, the first session terminates by itself. I restart it, and the other session terminates. These are to two separate hosts. On both ends is Debian Testing, kept current.
Could be a TCP port conflict. Try changing the value for SSH_PORT to 30200 in /usr/bin/x2gostartagent on one of the target machines so they are using different port ranges. End all X2Go sessions (not just disconnect, log out) before you try again.
Yes that did fix it. Thanks Daniel.
-- http://www.fastmail.fm - IMAP accessible web-mail
-
Daniel Lindgren -
John A. Sullivan III -
Les Mikesell -
merc1984＠f-m.fm