From owner-freebsd-questions@FreeBSD.ORG Tue Jun 21 07:55:34 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4C77C16A41C for ; Tue, 21 Jun 2005 07:55:34 +0000 (GMT) (envelope-from philip@xms.co.za) Received: from mail.int.xm.co.za (email.xm.co.za [196.23.175.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id 75E1043D48 for ; Tue, 21 Jun 2005 07:55:33 +0000 (GMT) (envelope-from philip@xms.co.za) Received: from mailnull by mail.int.xm.co.za with virus-scanned (Exim 4.42 (FreeBSD)) id 1Dkdjr-0003uz-EV for freebsd-questions@freebsd.org; Tue, 21 Jun 2005 10:04:07 +0200 Received: from [192.168.1.227] (helo=linux.int.xm.co.za) by mail.int.xm.co.za with esmtp (Exim 4.42 (FreeBSD)) id 1Dkdjr-0003up-8L; Tue, 21 Jun 2005 10:04:07 +0200 From: Philip Wege To: Olivier Nicole In-Reply-To: <200506210712.j5L7CwED078727@banyan.cs.ait.ac.th> References: <1119369916.4660.14.camel@linux.site> <200506210712.j5L7CwED078727@banyan.cs.ait.ac.th> Content-Type: text/plain Organization: XM Solutions Date: Tue, 21 Jun 2005 09:52:48 -0700 Message-Id: <1119372768.4660.18.camel@linux.site> Mime-Version: 1.0 X-Mailer: Evolution 2.0.1 Content-Transfer-Encoding: 7bit Cc: Freebsd-questions@freebsd.org Subject: Re: Sshd problem X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: philip@xms.co.za List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jun 2005 07:55:34 -0000 You cant even ssh onto the server from itself , it still times out. On Tue, 2005-06-21 at 14:12 +0700, Olivier Nicole wrote: > > Changed ip address to public address and made the box live so to speak. > > Ever since the ip was changed i am unable to ssh into the box , logs > > show error : Fatal timeout before authentication could occur. > > Did you, by any chance, used the IP from a previous box that was > already configured with SSH server? > > In that case your ssh client would have the public key for the old > server in it's table of known hosts, and would find a missmatch with > the public key of the new server. > > Olivier >