From owner-freebsd-questions@FreeBSD.ORG Thu Oct 7 12:58:27 2004 Return-Path: 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 7FA3B16A4CE for ; Thu, 7 Oct 2004 12:58:27 +0000 (GMT) Received: from internet.potentialtech.com (h-66-167-251-6.phlapafg.covad.net [66.167.251.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5679343D1D for ; Thu, 7 Oct 2004 12:58:27 +0000 (GMT) (envelope-from wmoran@potentialtech.com) Received: from working.potentialtech.com (pa-plum-cmts1e-68-68-113-64.pittpa.adelphia.net [68.68.113.64]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by internet.potentialtech.com (Postfix) with ESMTP id 87B9369A40; Thu, 7 Oct 2004 08:58:26 -0400 (EDT) Date: Thu, 7 Oct 2004 08:58:25 -0400 From: Bill Moran To: Peter Ulrich Kruppa Message-Id: <20041007085825.2cc8c722.wmoran@potentialtech.com> In-Reply-To: <20041007142750.O1089@pukruppa.net> References: <20041007142750.O1089@pukruppa.net> Organization: Potential Technologies X-Mailer: Sylpheed version 0.9.12 (GTK+ 1.2.10; i386-portbld-freebsd4.9) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-questions@freebsd.org Subject: Re: Cannot log into 4.10 machine via ssh X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Oct 2004 12:58:27 -0000 Peter Ulrich Kruppa wrote: > Hi! > > We are using Putty to log into our FreeBSD 4.10 Samba Server for > administration. > > Recently this doesn't work any more: > We can type in our login names, but there won't be any password > prompt. > Even locally from the server's terminal itself nothing happens. > > Everything else (pinging the machine, Samba service) works fine. > > What can be done? Look at what changed between the time it worked and when it stopped working and change that back. Unfortunately, there is almost no information in your email that can actually be used to diagnose the problem. Have you ensured that it doesn't work from other locations? Perhaps you putty installation got corrupted, or maybe an intervening ISP suddenly decided to block ssh. Do an nmap scan to see if ssh is being filtered. Try logging in from a closer server to see if the sshd on the server is still working. At least narrow it down to whether putty, the sshd, or the network is the problem. Ethereal would be a good tool as well. HTH -- Bill Moran Potential Technologies http://www.potentialtech.com