-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Hi Liz,
if my previous message with the $(which sshd) line didn't produce any useful debug output, here's something else you could try. However, if you *did* get debug output from that previous step, there's no need to try the following as well. These are mainly connectivity tests.
On the client's commandline, execute:
ssh -L18935:128.149.23.102:22 128.149.23.102
If that connects, leave the ssh session running.
Then, change your X2GoClient session to point to 127.0.0.1:18935 instead of 128.149.23.102:22
Try and see if it connects. (Expected result: Protocol mismatch error message)
Close X2GoClient, close the SSH session, then repeat it like this:
ssh -L18935:127.0.0.1:22 128.149.23.102 # ^^^^^^^^^ note the different IP here
Try and see if it connects. (Expected result: Protocol mismatch error message)
Again, close X2GoClient, close the SSH session.
Repeat with
ssh -L18935:127.0.0.1:18935 128.149.23.102 # ^^^^^ note the different port number here
verify that an SSHD is listening on the server by using the command
netstat -ant | grep ':18935' | wc -l
on the *server*. It should return a number greater than 0.
Now, try to connect X2GoClient using 127.0.0.1:18935 again.
- -Stefan
Am 08.05.2015 um 00:23 schrieb Real, Elizabeth (392K):
RH7 server: setup debug and set sshd port 18935
Client: configured x2goclient to connect to port 18935 but got connection refused x2go-INFO-8> "Starting connection to server: 128.149.23.102:18935" x2go-ERROR-2> "Connection Error(Cannot connect to 128.149.23.102:18935): Connection refused"
On 5/7/15, 12:41 PM, "Mihai Moldovan" <ionic@ionic.de> wrote:
On 06.05.2015 11:55 PM, Real, Elizabeth (392K) wrote:
Any other ideas?
No new information and you have done nothing wrong.
Looks like you will need to get your hands dirty.
Please start sshd manually as root on the RH 7 machine:
sudo sshd -ddd -p 18935
It should be running in the foreground, outputting debug information and listening on port 18935 (feel free to change this to whatever you feel suitable, it doesn't matter as long it as the port is unused and not colling with anything else you might use.
Then, configure x2goclient to connect to that port and start a session.
You should see additional debug information printed by sshd... hopefully hinting at what might have gone awry.
Mihai
_______________________________________________ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
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 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2
iQEcBAEBCAAGBQJVTGXuAAoJEG7d9BjNvlEZPDAH/AsmNapduSl+qy5xEzc/r6Yg 72JylW7RGfWh0G6jf5OSGmgw2ciccvZSPWNdzHRjBuNlvOqF3ChxJ9FCKvkClU+x lgtuFsb0GHF09FtWUFw1pqyBxng8NII4J/eH69+ioifP+mQwpHpHB0lCuo2z/ezX CTHfVGIFYmT1aCcvqWLjU0T1S8GBp2+ZmAgoQ1FIqaSvon3ySYA2yALC1aHA9Ofe eP9qbIGrMUotY/AR709i6VRCVx4EajQeJgUNUDg04RxBmRvhgblEsxkPIKAJfDIk N4s4ItBmXqzwmwlShUV3gPWGPcvOWpFE74Cq4znIY+F+plgMUsVFw1cgd2EPr1c= =DB8x -----END PGP SIGNATURE-----