Dear Mr. Bauer,
thanks for your immediate response!
On 05.08.2015 12:30, Stefan Baur wrote: ...
Since you're using a custom-built Linux distribution, it would most likely be helpful to know what it is based on - Debian, Ubuntu, Fedora Core, Red Hat, ... and the corresponding version number.
Our system is build from scratch, no package manager. I used x2goclient-4.0.5.0 x2goserver-4.0.1.19 nx-libs-3.5.0.32.tar.gz
System environment: gcc-5.2.0 glibc-2.21 linux-4.1.3
Another thing to check: Are you using banners, like, for example in /etc/hosts.allow?
No banners, no .profile, no /etc/profile
Would be really great if you have a look at client-sessions1:
Proxy: Identified message of 14 bytes for FD#6 channel ID#1. handleWrite: Called for FD#6. handleWrite: Decoding messages for FD#6 with 14 bytes in the buffer.
a working connection shows
Proxy: Identified message of 50 bytes for FD#6 channel ID#1. handleWrite: Called for FD#6. handleWrite: Decoding messages for FD#6 with 50 bytes in the buffer.
I assume that the fake cookie can't be set. Di you have any hint where to look for this?
Kind regards,
H.-A. Arnolds
On 05.08.2015 12:30, Stefan Baur wrote:
Am 05.08.2015 um 12:05 schrieb Heinz-Ado Arnolds:
I'm trying to integrate the x2go system into our own (MPA-)Linux system which we are using and developing for centuries now (it's used non commercial in an research institute). While the client connection from my (MPA-)system to a pre-installed Ubuntu server works without a problem, the connection to a (MPA-)Linux server doesn't work yet.
Since you're using a custom-built Linux distribution, it would most likely be helpful to know what it is based on - Debian, Ubuntu, Fedora Core, Red Hat, ... and the corresponding version number.
Did you use one of our repositories for .deb or .rpm packages, or did you build x2goserver from source?
Also, are you using stable or nightly builds?
A list of installed packages, if you have some sort of package management on your self-built distribution, would be helpful to spot any missing packages required by X2Go.
Another thing to check: Are you using banners, like, for example in /etc/hosts.allow?
Something like "sshd: <list of IPs here> : banners /etc/banners" maybe? If yes, disable that and see if it helps.
Kind Regards, Stefan Baur
x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev