CentOS 7.4
Hi,
I've installed x2go using yum on a new server (yum --enablerepo="epel" install x2goserver, and yum --enablerepo="epel" install x2goserver-xsession) and rebooted it. I also installed MATE and Xfce packages.
However when I try to connect with x2go client (4.1.1.1 on windows 10), I get a timeout. Connecting to our old x2go server works.
I've disabled the firewall for testing but it still times out.
I can successfully ssh using x-forwarding to the new x2go server.
/var/log/messages doesn't show anything useful.
Any thoughts about what might be happening?
Thanks
-M
Am 23.03.2018 um 22:10 schrieb Michael Stauffer:
I've installed x2go using yum on a new server (yum --enablerepo="epel" install x2goserver, and yum --enablerepo="epel" install x2goserver-xsession) and rebooted it. I also installed MATE and Xfce packages.
However when I try to connect with x2go client (4.1.1.1 on windows 10), I get a timeout. Connecting to our old x2go server works.
I've disabled the firewall for testing but it still times out.
I can successfully ssh using x-forwarding to the new x2go server.
/var/log/messages doesn't show anything useful.
Any thoughts about what might be happening?
Please install the debug version of x2goclient.exe (it's a checkbox option when running the installer), then run
x2goclient.debug.exe 2>&1 >x2goclient.log
and post that log.
Kind Regards, Stefan Baur
-- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243
- On 03/23/2018 10:10 PM, Michael Stauffer wrote:
CentOS 7.4
However when I try to connect with x2go client (4.1.1.1 on windows 10), I get a timeout. Connecting to our old x2go server works.
I've disabled the firewall for testing but it still times out.
Such issues come up every now and then and mostly relate to different address families being used.
libssh doesn't pick a host to connect to at random, so it'll use the first entry that is returned by your DNS system.
In some instances, this leads to libssh (and hence X2Go Client) always trying to connect to the remote server via IPv6, while...
I can successfully ssh using x-forwarding to the new x2go server.
OpenSSH's implementation seems to prefer IPv4 addresses some of the time (but not always) - and may even try the next address in the list if connecting to the current one failed. libssh doesn't seem to have this fallback.
Please check your IPv6 setup.
You can have X2Go Client connect to an IPv4 address directly, but that's finicky. Essentially, to avoid having to do this for every session definition, you could define a new shortname in ~/.ssh/config named host-v4, hardcode the IPv4 address there and use that shortname in X2Go Client. That should work on UNIX-based platforms and theoretically also on Windows, but I don't know the correct path for the file on this platform.
As a quick test, try using the v4 address anyway.
Mihai
-
Michael Stauffer -
Mihai Moldovan -
Stefan Baur