From owner-freebsd-stable@FreeBSD.ORG Mon Jun 6 21:41:49 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DC19116A41C for ; Mon, 6 Jun 2005 21:41:49 +0000 (GMT) (envelope-from ratman6@charter.net) Received: from mxsf25.cluster1.charter.net (mxsf25.cluster1.charter.net [209.225.28.225]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0E74043D5D for ; Mon, 6 Jun 2005 21:41:48 +0000 (GMT) (envelope-from ratman6@charter.net) Received: from mxip18a.cluster1.charter.net (mxip18a.cluster1.charter.net [209.225.28.148]) by mxsf25.cluster1.charter.net (8.12.11/8.12.11) with ESMTP id j56Lflfi019611 for ; Mon, 6 Jun 2005 17:41:47 -0400 Received: from pc-24-151-49-073.newt1.ct.charter.com (HELO bedroom) (24.151.49.73) by mxip18a.cluster1.charter.net with ESMTP; 06 Jun 2005 17:41:48 -0400 X-IronPort-AV: i="3.93,175,1115006400"; d="scan'208"; a="1154208676:sNHT18369328" From: "Matt Smith" To: Date: Mon, 6 Jun 2005 17:41:46 -0400 Message-ID: <000001c56ae0$8a20c870$0201a8c0@bedroom> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 In-Reply-To: <44ll5nuq1h.fsf@be-well.ilk.org> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Subject: RE: SSHD and FTPD, can't connect X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Jun 2005 21:41:50 -0000 Where is the sshd debugger? Matt -----Original Message----- From: lowell@be-well.ilk.org [mailto:lowell@be-well.ilk.org] On Behalf Of Lowell Gilbert Sent: Monday, June 06, 2005 5:36 PM To: Matt Smith; freebsd-stable@freebsd.org Subject: Re: SSHD and FTPD, can't connect "Matt Smith" writes: > Did that, to no avail. It was fine then it started doing this. Any > other suggestions? Plenty, but guessing is an inefficient way to solve this. Turn on debugging for both the sshd on that system and the slogin invocations on the other machines, and let the computers tell you what is wrong.