Re: ssh

[Ed Greshko]

On 9/18/19 5:09 AM, Garry T. Williams wrote:
> > ssh 192.168.1.12 22
> > time out
>
> Ed has told you what is wrong here.

But, not in the way you're suggesting.

It is obvious that a connection is not being established.  Had it been the error would not have been "time out".
It would have been.

[egreshko@meimei ~]$ ssh 192.168.1.55 22
bash: 22: command not found

Also, to further comment on the "no route to host" issue.  When you read later posts you would have discovered that I missed one thing and another person (Richard) caught that when asked to telnet to port 22 the OP didn't follow instructions and left off the "22" at the end of the command.