Ok,
1. I did need to re-run the keygens, both ssh-keygen and ssh-keygen2
It appears that this new rpm I have has all the stuff for both ssh and
ssh2, and ssh2 is what's running by default.
If I telnet the "garnet" (the Red Hat box in question) I can then do "ssh2
192.168.0.80" and connect.
If I use ssh, I cannot connect.
Apparently that's why putty and SuSE are failing - they have the original
Ssh, I guess.
Time to upgrade :-)
In ps -auxw I now see sshd2, but not sshd.
I can live with this, but don't you think it should fall back to ssh 1? The
way I got it running was to enable it as a service in "setup" and there's
only one option.
Can I have them both running, or is there something I can edit that would
cause it to default to ssh1 when the client isn't ssh2 compatible?
JW
At 04:24 PM 8/29/2000 -0500, you wrote:
>On Tue, 29 Aug 2000, Jonathan Wilson wrote:
>
> > Howdy,
> >
> > I have downloaded the latest non-commercial ssh rpm from www.ssh.com 's
> man
> > ftp site, and it installed fine, and I used "setup" to make sure it will
> > start at boot up.
> >
> > I rebooted, and according to the initscripts (watching the console during
> > boot) it came on just fine, but if I try to use putty from windows I get a
> > can't-connect error, and if I try it from linux I get:
> >
> > jw@bismuth:~ > ssh 192.168.0.80
> > Connection closed by remote host.
> >
> >
> > also, ps -aux |grep ssh turns up nothing on the RH bax, whereas on my
> > [working] SuSE box it returns this:
> >
> > jw@bismuth:~ > ps -aux | grep ssh
> > root 206 0.0 0.8 1612 680 ? S Aug28 0:03
> /usr/sbin/sshd
> > root 2075 0.0 1.6 2016 1316 ? S 09:08 0:02
> /usr/sbin/sshd
> > root 2499 0.0 1.6 2000 1304 ? S 13:14 0:00
> /usr/sbin/sshd
> > jw 3006 0.0 0.6 1256 512 pts/1 S 14:55 0:00 grep ssh
> >
> >
> > also note:
> >
> > Aug 30 03:53:44 garnet sshd2[621]: connection from "192.168.0.70"
> > Aug 30 03:53:49 garnet sshd2[831]: DNS lookup failed for "192.168.0.70".
> > Aug 30 03:53:49 garnet sshd2[831]: FATAL ERROR: Executing ssh1 in
> > compatibility mode failed.
> >
> >
> > what's up with this? What do I need to do to get it working?
> >
>
>It seems to me that sshd is definitely not running in your Red Hat box,
>since it doesn't show in the process table. You may want to run the
>following command and reply with the output:
>
>ps auxw | grep sshd
>
>
>If the daemon is not running, I'd check the /var/log/messages for clues as
>to what is failing. Also keep in mind that putty may not be compatible
>with ssh2. I don't know whether it is or not, I'm just bringing that up
>as a possibility.
>
>Other things that you can try:
>
>telnet [redhatbox] 22
>
>Does it even establish a connection to the server? It should time out
>after a while because no encrypted keys are being exchanged, but it should
>at least establish a connection through that port.
>
>netstat | grep ssh
>
>This other command should show if there is any daemon listening on port
>22, and also if there is already any established connection.
>
>Just a few ideas...
>
>
>
>-------------------------------
>Nitebirdz
>http://www.linuxnovice.org
>Your place for tips, news, etc.
>
>
>
>_______________________________________________
>Redhat-list mailing list
>[EMAIL PROTECTED]
>https://listman.redhat.com/mailman/listinfo/redhat-list
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
