ssh (client): No route to host
Saturday, May 31st, 2008ssh is driving me CRAZY right now... On an almost stock CentOS 5.1 install (inside a Xen VPS, though), I changed sshd to listen on 2222 instead of 22 and restarted sshd.
All of a sudden:
I should note that I'm actively logged into that IP in another window, and that it responds to ping. There most certainly is a route. Yes, I've quadruple-checked that I have the right IP. And I use the -p2222 daily to connect to another machine. This is a virgin CentOS install; I just changed the "Port 22" line to "Port 2222" and restarted sshd (/etc/init.d/sshd restart).
I am not behind any sort of firewall, unless CentOS installs one that I don't know about. (I own the physical hardware, not just the virtual machine.)
I figured it had to do with this error in /var/log/secure
So I changed (uncommented) the ListenAddress directive to:
and restarted sshd again.
Still no luck... Anyone? :confused:
Edit: ssh works fine if I ssh into the server from the server's console (e.g., don't actually go out onto the network.) But where is this port 2222 block coming in? I have definitely not blocked the port, and the main host listens on 2222 with no problems... Meaning that the trouble reaching the port is happening on the server itself.
All of a sudden:
Code:
matt@t60:~$ ssh -p2222 64.191.108.xxx
ssh: connect to host 64.191.108.xxx port 2226: No route to hostI am not behind any sort of firewall, unless CentOS installs one that I don't know about. (I own the physical hardware, not just the virtual machine.)
I figured it had to do with this error in /var/log/secure
Code:
May 31 19:18:39 relay120 sshd[23359]: Server listening on :: port 2222.
May 31 19:18:39 relay120 sshd[23359]: error: Bind to port 2222 on 0.0.0.0 failed
: Address already in use.Code:
ListenAddress 64.191.108.xxxStill no luck... Anyone? :confused:
Edit: ssh works fine if I ssh into the server from the server's console (e.g., don't actually go out onto the network.) But where is this port 2222 block coming in? I have definitely not blocked the port, and the main host listens on 2222 with no problems... Meaning that the trouble reaching the port is happening on the server itself.