Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 3 Mar 2006 09:37:38 -0800
From:      "Ted Mittelstaedt" <tedm@toybox.placo.com>
To:        "Kurt Buff" <kurt.buff@gmail.com>, "Alex Zbyslaw" <xfb52@dial.pipex.com>,  <freebsd-questions@freebsd.org>
Subject:   RE: SSHD working in a funky fashion
Message-ID:  <LOBBIFDAGNMAMLGJJCKNIEHLFDAA.tedm@toybox.placo.com>
In-Reply-To: <a9f4a3860603011318l177165f0je96a0e7695d1ed35@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help

Check your ssh key size, the newer versions of FreeBSD went from
a 1024 bit key to a 2048 bit kay and some ssh clients can't deal
with that big a one.  Also check reverse DNS records for the
IP's involved.

Ted

>-----Original Message-----
>From: owner-freebsd-questions@freebsd.org
>[mailto:owner-freebsd-questions@freebsd.org]On Behalf Of Kurt Buff
>Sent: Wednesday, March 01, 2006 1:18 PM
>To: Alex Zbyslaw; freebsd-questions@freebsd.org
>Subject: Re: SSHD working in a funky fashion
>
>
>On 2/28/06, Alex Zbyslaw <xfb52@dial.pipex.com> wrote:
>> Kurt Buff wrote:
>> >sshd: fatal: timeout before authentication from 192.168.11.63
>> >
>> Can you ssh from one of your other FreeBSD boxes to this box?  If not
>> then try "ssh -v -v -v" which may point you in the right direction.
>
>Well, today it's working, but it's veeeeeerrrrrrrryyyyyyy slow to log
>into, from the Windows boxes. From the FreeBSD boxes it's just a bit
>slow to log in.
>
>> If it's just Windows which can't login, then try running sshd in debug
>> mode and see if that tells you anything.  from man sshd
>>
>>      -d      Debug mode.  The server sends verbose debug output to the
>> system
>>              log, and does not put itself in the background.
>The server
>> also
>>              will not fork and will only process one connection.  This
>> option
>>              is only intended for debugging for the server.
>Multiple -d
>>              options increase the debugging level.  Maximum is 3.
>>
>> If none of that shows anything useful, then maybe you have
>some network
>> level problem.  Does any kind of connection from Windows work?  E.g.
>> Samba shared drive?  Ftp?  Or even (for testing only) telnet, since
>> putty does that too?
>
>Don't have telnet or ftp running, but I'm able to browse the samba
>shares just fine.
>
>> If it's a network level problem, then some more info about
>your topology
>> might be helpful.  E.g. are all these machines on the same LAN segment
>> connected to the same switch?
>
>One Windows box is on a different subnet but the same (layer3) switch,
>one is on a different switch but same subnet, and the FreeBSD boxes (3
>of them) are on the same switch and subnet.
>
>> PS I assume you've tried your error message through google?
>
>Yup - lots of hits, but not much meat.
>
>Kurt
>_______________________________________________
>freebsd-questions@freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>To unsubscribe, send any mail to
>"freebsd-questions-unsubscribe@freebsd.org"
>
>--
>No virus found in this incoming message.
>Checked by AVG Free Edition.
>Version: 7.1.375 / Virus Database: 268.1.1/273 - Release Date: 3/2/2006
>




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?LOBBIFDAGNMAMLGJJCKNIEHLFDAA.tedm>