Article 6P2JC ssh: port 22: No route to host

ssh: port 22: No route to host

by
mfoley
from LinuxQuestions.org on (#6P2JC)
I've rebooted a server that was powered off for a while, then tried to ssh into it. I'm getting the following error:
Code:$ ssh -vv mfoley@webserver
OpenSSH_9.8p1, OpenSSL 1.1.1w 11 Sep 2023
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Authenticator provider $SSH_SK_PROVIDER did not resolve; disabling
debug2: resolving "webserver" port 22
debug1: Connecting to webserver [192.168.0.3] port 22.
debug1: connect to address 192.168.0.3 port 22: No route to host
ssh: connect to host webserver port 22: No route to hostI'm not sure what's happened, but I believe this was working before I powered the computer a week-ish ago. Domain Resolution works from 192.168.0.3. Both sshd and sendmail are listening on 192.168.0.3, but I can't telnet to either:
Code:netstat -tunlp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN 1371/sendmail: acce
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1241/sshd: /usr/sbi
tcp 0 0 0.0.0.0:587 0.0.0.0:* LISTEN 1371/sendmail: acceFrom another computer on the LAN, nmap shows no ports open on 192.168.0.3.

No firewall is running on any computers.

There is nothing in messages, syslog or secure when trying to ssh to 192.168.0.3.

What's wrong here? Thanks
External Content
Source RSS or Atom Feed
Feed Location https://feeds.feedburner.com/linuxquestions/latest
Feed Title LinuxQuestions.org
Feed Link https://www.linuxquestions.org/questions/
Reply 0 comments