Hi John,

and hello to all others in the list,
Here are some hints from my side.
Did you change some Network Hardware? I had it in the past
with ltsp (which I used before) that somehow a change of network hardware
causes in this error. (change of network card, router/switch, additional clients?)

Maybe you can install iptraf (traffic monitor)
apt-get install iptraf

It seems to be that the network stream break down and the session still exist, and after a timeout
you can connect again. Now we have to find out why this happen ...

How often does this happen? (After 10 minutes connection ... or once a day?)

Did you tail -f /var/log/syslog on the server when you try to connect with this error message?

Best regards
T.

 









Am 17. Januar 2012 04:09 schrieb John A. Sullivan III <jsullivan@opensourcedevel.com>:
On Mon, 2012-01-16 at 21:22 -0500, Richard Strysniewicz wrote:
> On 01/16/2012 07:42 PM, Richard Strysniewicz wrote:
> >
> >
> > On 01/16/2012 07:28 PM, John A. Sullivan III wrote:
> >> <Snip>
> >> Just a hunch - I wonder if there is an underlying SSH problem - John
> >>
> > I cannot say for sure, but I do believe basic ssh is working fine...
> > I have public/private keys set up and I do ssh between the machines
> > frequently.  I have never had a failure to connect or any other error
> > using ssh from the command line.  Is there something I can try besides
> > plain old command line ssh to more closely emulate what is going on
> > with x2go connections?
> ><snip>
I'm wondering if it has nothing to do with establishing a new session
but confusion about an existing session.  When that existing session
finally times out, then you can magically connect.  Just an off the cuff
guess - John

_______________________________________________
X2go-User mailing list
X2go-User@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/x2go-user