Looks like you've covered all the bases. You are running sshd2 for both
ssh1 and ssh2 correct? And you say ssh1 works correctly, right? If this
is all true maybe the host keys for sshd2 were not generated correctly.
Try to re-generate them by hand. You need to do that as root user, but
you probably know that.

I'm stumped if this isn't the problem.

Carl

On 22-Feb-00 Allan Andersen wrote:
> Blue Lang wrote:
>> 
>> > Did you swap your keys between machines? If not that's your problem.
>> > You
>> > need to add the ~/.ssh/identity.pub to ~/.ssh/authorized_keys on the
>> > other
>> > machine and visa-versa.
>> 
>> Really? This looks like a routing issue to me. Can you telnet to the
>> machine you're trying to reach with ssh? If so, is there a firewall,
>> and,
>> if so, is port 22 open?
> 
> Yes there is no problem reaching the machine with telnet, but also I
> can
> use
> ssh1 to connect with this machine (both machines are mine, and behind
> the
> same firewall on a LAN network.).
>  
>> Is the ssh daemon running on the remote host? Does the local host have
>> a
>> DNS entry? Can you look up that entry from the remote? etc, :)
> 
> Yes there is a ssh deamon running, actually it's sshd2 that's running.
> Both 
> of the machines are using the same DNS server, so this shouldn't be the
> problem - but yes I can ssh to this machine and also from the remote
> machine.
> And from the DNS server I can ssh to the machine also.
> 
>> Good luck,
> 
> Thanks :-)
> 
> /Allan

------------------------------------------------------------------------
E-Mail: Carl J. Nobile <[EMAIL PROTECTED]>
Date: 23-Feb-00                             Phone: 315-453-2912 Ex. 5336
Time: 08:27:10                                Fax: 315-453-3052

Software Engineering Group -- AppliedTheory Corp.
224 Harrison Street, 6th Floor, Syracuse, NY  13202
------------------------------------------------------------------------

Reply via email to