Re: ssh

[Richard]

> Date: Saturday, September 14, 2019 22:13:11 +0800
> From: Ed Greshko
> > > On 9/14/19 9:34 PM, Patrick Dupre wrote:
> > > From the remote system, what do you get when you try to "telnet"
> > > to port 22?
> >
> > 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.

Actually, it looks like you did a telnet to the (default) telnet port
(23):
> telnet 192.168.1.12

rather than the ssh port (22), as Ed suggested:
> telnet 192.168.1.12 22

which is what is needed to get meaningful results.

Try the telnet to the ssh port and see what you get. It may be a
firewall issue, but the results you showed don't appear to be a test
of the issue.

ssh

[Ed Greshko]

On 9/14/19 11:41 PM, Richard wrote:
> Actually, it looks like you did a telnet to the (default) telnet port
> (23):
> > telnet 192.168.1.12
>
> rather than the ssh port (22), as Ed suggested:

Thanks!  Good Catch.

I only looked at the end result.  Gotta get out of the habit of expecting someone to do as requested.  :-) :-)

ssh

[Patrick Dupre]

Here is the bizarre thing:
from a gnome-shell
telnet 192.168.1.12 22
Trying 192.168.1.12...
Connected to 192.168.1.12.
Escape character is '^]'.
SSH-2.0-OpenSSH_8.0

Invalid SSH identification string.
Connection closed by foreign host.

ssh 192.168.1.12 22
time out

But
from a terminal (ttx)
the ssh works perfectly well!

What is wrong with the gnome environment?
> > Date: Saturday, September 14, 2019 22:13:11 +0800
> > From: Ed Greshko
> > > > On 9/14/19 9:34 PM, Patrick Dupre wrote:
> > > > From the remote system, what do you get when you try to "telnet"
> > > > to port 22?
> > >
> > > 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.
>
> Actually, it looks like you did a telnet to the (default) telnet port
> (23):
> > telnet 192.168.1.12
>
> rather than the ssh port (22), as Ed suggested:
> > telnet 192.168.1.12 22
>
> which is what is needed to get meaningful results.
>
> Try the telnet to the ssh port and see what you get. It may be a
> firewall issue, but the results you showed don't appear to be a test
> of the issue.
>
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/[e-mail]

ssh

[Ed Greshko]

On 9/15/19 1:19 AM, Patrick Dupre wrote:
> Here is the bizarre thing:
> from a gnome-shell
> telnet 192.168.1.12 22
> Trying 192.168.1.12...
> Connected to 192.168.1.12.
> Escape character is '^]'.
> SSH-2.0-OpenSSH_8.0
>
> Invalid SSH identification string.
> Connection closed by foreign host.

That's good.  Shows port 22 is open.
> ssh 192.168.1.12 22
> time out
>
> But
> from a terminal (ttx)
> the ssh works perfectly well!
>
> What is wrong with the gnome environment?

First, the format of the command is wrong.  The "22" is a command to be executed on the remote side.
Do "man ssh" and "man telnet" to learn about the format of the command.

Now, as for what is wrong with the "gnome environment"/

What is the output of "which ssh"?  It should be

[egreshko@meimei ~]$ which ssh
/usr/bin/ssh

ssh

[Garry T. Williams]

On Saturday, September 14, 2019 1:19:05 PM EDT Patrick Dupre wrote:
> Here is the bizarre thing:
> from a gnome-shell
> telnet 192.168.1.12 22
> Trying 192.168.1.12...
> Connected to 192.168.1.12.
> Escape character is '^]'.
> SSH-2.0-OpenSSH_8.0

This means you have a route and that sshd is listening on port 22.  Of
course, you cannot establish a session from the command line, but it
does show that you can reach the remote and that the remote will
answer on that port.
> ssh 192.168.1.12 22
> time out

Ed has told you what is wrong here.

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.