Not necessarily. You can certainly get "No route to host", rather than "Connection failed" if the port is not open.

On September 17, 2019 9:05:34 PM UTC, "Garry T. Williams" <gtwilliams@gmail.com> wrote:
On Saturday, September 14, 2019 10:13:11 AM EDT Ed Greshko wrote:
On 9/14/19 9:59 PM, Patrick Dupre wrote:
On 9/14/19 9:34 PM, Patrick Dupre wrote:
telnet 192.168.1.12
Trying 192.168.1.12...
telnet: connect to address 192.168.1.12: No route to host

I guess that I need to reestablish the route.
How?


No, that is an indication that port 22 is not open.

No. That error is from an ICMP message and means exactly what it
says. It has nothing to do with what is or is not listening on the
remote host since the attempt to connect to 192.168.1.12 never got
that far.

You do not have a route to 192.168.1.12 from the host that you
used to run the telnet command.

--
Sent from my mobile device. Please excuse my brevity.