Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 31 Jan 2005 09:00:52 +0100
From:      Fabian Anklam <greatnorthern@gmail.com>
To:        nigel@eyede.com, freebsd-questions@freebsd.org
Subject:   Re: sshd_config / failed authentication
Message-ID:  <467b1e7a050131000064c42dd5@mail.gmail.com>
In-Reply-To: <41F9B721.7090602@eyede.com>
References:  <467b1e7a050127172176b829f4@mail.gmail.com> <467b1e7a05012719057f9b7a30@mail.gmail.com> <41F9ADCE.4080705@eyede.com> <467b1e7a050127192736557aed@mail.gmail.com> <41F9B20C.5070304@eyede.com> <467b1e7a050127194414e626b6@mail.gmail.com> <41F9B721.7090602@eyede.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 28 Jan 2005 16:53:05 +1300, Nigel Wohlers <nigel@eyede.com> wrote:
> Sorry, that's all the info I have on the subject, I recall a similar
> issue I encountered a while ago and that seemed to be the cause.  Was
> just my initial postulation.
> 
> 
> Fabian Anklam wrote:
> > On Fri, 28 Jan 2005 16:31:24 +1300, Nigel Wohlers <nigel@eyede.com> wrote:
> >
> >>What is the value of "LoginGraceTime"?
> >>
> >>SSH will try to do a reverse lookup on the IP connecting to it and if
> >>that times out before "LoginGraceTime" then your client (putty) will get
> >>booted and SSH will report the failure to syslog.
> >>
> >>
> >>Fabian Anklam wrote:
> >>
> >>>>Reverse DNS lookup timeout?
> >>>>
> >>>>N
> >>>>
> >>>
> >>>
> >>>Authentication seems to be the problem, not connection, care to elaborate?
> >>>
> >>>Thanks,
> >>>
> >>>Fabian
> >>
> >
> > LoginGraceTime was left at default value (2 minutes iirc). Adding the
> > Windows box to /etc/hosts doesn't resolve the problem.
> >
> > sshd writes
> >
> > sshd[procid]: fatal: Timeout before authentication for windows.box.ip
> >
> > to /var/log/messages
> >
> > Fabian
> 

Hi Nigel, sorry for brushing your suggestion off so quickly. SSHD
trying a reverse DNS of the (private IP) ssh'ing machines name via my
ISP's DNS servers which were in resolv.conf thanks to the machine
being configured with DHCP once seemed to be the cause of the problem.

Again, thanks for your help!



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