Help with TeraTerm SSH

[bpeary]

Does anyone have experience with this Windows Telnet client? All I get is
a 'connection refused' error when trying to connect to a linux (Debian)
server. I'm using TeraTerm Pro 2.3 and TTSSH 1.5.1 Connection is to port
22. Non-SSH connection to port 23 works fine.

Once a non-SSH connection is established, I can use the server's SSH
(version 1.2.26) to telnet to other linux/unix servers, so
it appears that SSH is working properly on the server.

********************************************************************
NO SPAM: To email me use the name bpeary and the domain my-deja.com.
********************************************************************

[Richard E. Silverman]

It sounds like you've installed SSH but have not started the daemon. You
can run the "ssh" program to SSH (you said "telnet") out of the box, but
the program which provides incoming SSH service ("sshd") is not running.
Try running /usr/local/sbin/sshd as root.

- Richard Silverman
sl...@shore.net

[Richard E. Silverman]

> + Non-SSH connection to port 23 works fine.
> ^^^^^^^
> That's called "telnet" and has nothing to do with the ssh daemon or client.

TeraTermSSH also does Telnet; I believe that's what he means.

- Richard Silverman
sl...@shore.net

[Alan J. Flavell]

On 19 Apr 2000, Richard E. Silverman wrote:

> > + Non-SSH connection to port 23 works fine.
> > ^^^^^^^
> > That's called "telnet" and has nothing to do with the ssh daemon or client.
>
> TeraTermSSH also does Telnet; I believe that's what he means.

Of course; but the point seems to have been that the target
destination machine wasn't running an ssh server (sshd); the fact that
it responded to a telnet call does nothing more than prove that it's
running a telnet server, it doesn't prove anything about its ability
to accept an ssh call. But I think the questioner will have
understood that by an earlier followup to this thread.

[bpeary]

The ps command indicates that sshd is running:

188 ? S 0:44 /usr/sbin/sshd

Here's the config file for sshd:

Port 22
ListenAddress 208.13.56.50
HostKey /etc/ssh/ssh_host_key
RandomSeed /etc/ssh/ssh_random_seed
ServerKeyBits 768
LoginGraceTime 600
KeyRegenerationInterval 3600
PermitRootLogin yes
IgnoreRhosts no
StrictModes yes
QuietMode no
X11Forwarding yes
X11DisplayOffset 10
FascistLogging no
PrintMotd yes
KeepAlive yes
SyslogFacility DAEMON
RhostsAuthentication no
RhostsRSAAuthentication yes
RSAAuthentication yes
PasswordAuthentication yes
PermitEmptyPasswords yes
UseLogin no
# CheckMail no
# PidFile /u/zappa/.ssh/pid
# AllowHosts *.our.com friend.other.com
# DenyHosts lowsecurity.theirs.com *.evil.org evil.org
# Umask 022
# SilentDeny yes

********************************************************************
NO SPAM: To email me use the name bpeary and the domain my-deja.com.
********************************************************************

[Peiyu Hsu]

bpeary wrote:

> The ps command indicates that sshd is running:
>
> 188 ? S 0:44 /usr/sbin/sshd
>
> Here's the config file for sshd:
>
> Port 22
> ListenAddress 208.13.56.50

If my memorance is correct, ListenAddress should be just left as default valuem
which is 0.0.0.0 (?)

>
> HostKey /etc/ssh/ssh_host_key
> RandomSeed /etc/ssh/ssh_random_seed
> ServerKeyBits 768
> LoginGraceTime 600
> KeyRegenerationInterval 3600
> PermitRootLogin yes
> IgnoreRhosts no
> StrictModes yes
> QuietMode no
> X11Forwarding yes
> X11DisplayOffset 10
> FascistLogging no
> PrintMotd yes
> KeepAlive yes
> SyslogFacility DAEMON
> RhostsAuthentication no
> RhostsRSAAuthentication yes

^^^ no

>
> RSAAuthentication yes
> PasswordAuthentication yes

^^^ no

>
> PermitEmptyPasswords yes
> UseLogin no
> # CheckMail no
> # PidFile /u/zappa/.ssh/pid
> # AllowHosts *.our.com friend.other.com
> # DenyHosts lowsecurity.theirs.com *.evil.org evil.org
> # Umask 022
> # SilentDeny yes
>

I was just fooled by the same question as what you met. Bad luck...
Remember to start the ssh daemon. Good luck to you. :)

[Mark Nienberg]

Check also hosts.allow and hosts.deny to be sure ssh access is allowed from
the windows IP address. When I installed ssh using the rpm, I didn't
realize that it had been compiled to use tcp wrappers.

Mark Nienberg

"bpeary" <b...@the-dma.org> wrote in message
news:Pine.LNX.4.10.100041...@bioanalytical.com...

> Does anyone have experience with this Windows Telnet client? All I get is
> a 'connection refused' error when trying to connect to a linux (Debian)
> server. I'm using TeraTerm Pro 2.3 and TTSSH 1.5.1 Connection is to port
> 22. Non-SSH connection to port 23 works fine.
>
> Once a non-SSH connection is established, I can use the server's SSH
> (version 1.2.26) to telnet to other linux/unix servers, so
> it appears that SSH is working properly on the server.
>
>
>
>

[Peiyu Hsu]

Try ssh to other unix server and then ssh from other server back to the
localhost again, which can make sure your ssh and sshd both work.

[Richard E. Silverman]

>>>>> "Mark" == Mark Nienberg <m...@REMOVE.tipping.com> writes:

Mark> Check also hosts.allow and hosts.deny to be sure ssh access is
Mark> allowed from the windows IP address. When I installed ssh using
Mark> the rpm, I didn't realize that it had been compiled to use tcp
Mark> wrappers.

That's good advice in general, but unlikely to be the problem in this
case. The message "connection refused" usually means that nothing is
listening on the target port. SSH with TCP-wrappers doesn't behave that
way; it accepts the connection, does a getpeername to find out the client
address, and then drops the connection if the libwrap access check fails.

- Richard Silverman
sl...@shore.net