Am 01.09.2014 um 15:14 schrieb Mike Gabriel:
Nope, there is no one else than him on the connection. He is using an ethernet cable to his cable-modem, wifi is turned off, and no other applications than X2go client is running on his computer. The issue can be reproduced any time we like, but only on this particular ISP connection.
Are hardware issues ruled out already?
For example, you could try to use scp or rsync (which uses ssh by default, just as X2Go) to transfer a sufficiently large file back and forth and see if the line/cable-modem performs according to specs.
I've seen wonky hardware act up once the upstream was actually maxed out (no issues during casual surfing, pinging etc. - only when a higher load towards the upstream router was present).
Hint: If you test using the particular client and server that you want to use for the X2Go connection, you'll see a more realistic result than by running some obscure speed test on a web site.
-Stefan