From owner-freebsd-questions@FreeBSD.ORG Thu Oct 7 13:14:30 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 9489716A4CE for ; Thu, 7 Oct 2004 13:14:30 +0000 (GMT) Received: from dsl-mail.kamp.net (mail.kamp-dsl.de [195.62.99.42]) by mx1.FreeBSD.org (Postfix) with SMTP id D7A8143D1F for ; Thu, 7 Oct 2004 13:14:29 +0000 (GMT) (envelope-from root@pukruppa.de) Received: (qmail 11925 invoked by uid 513); 7 Oct 2004 13:23:07 -0000 Received: from root@pukruppa.de by dsl-mail by uid 89 with qmail-scanner-1.21 Clear:RC:1(213.146.114.24):SA:0(-4.9/5.0):. Processed in 0.711004 secs); 07 Oct 2004 13:23:07 -0000 X-Spam-Status: No, hits=-4.9 required=5.0 Received: from unknown (HELO reverse-213-146-114-24.dialin.kamp-dsl.de) (213.146.114.24) by dsl-mail.kamp.net with SMTP; 7 Oct 2004 13:23:06 -0000 Date: Thu, 7 Oct 2004 15:17:52 +0200 (CEST) From: Peter Ulrich Kruppa X-X-Sender: root@pukruppa.net To: Bill Moran In-Reply-To: <20041007085825.2cc8c722.wmoran@potentialtech.com> Message-ID: <20041007150647.F1089@pukruppa.net> References: <20041007142750.O1089@pukruppa.net> <20041007085825.2cc8c722.wmoran@potentialtech.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed 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 13:14:30 -0000 On Thu, 7 Oct 2004, Bill Moran wrote: > 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. Nothing. > > Unfortunately, there is almost no information in your email that can > actually be used to diagnose the problem. Sorry, I don't know what I might have to look for. I tried # man ssh but couldn't find anything about log files or so. > Have you ensured that it doesn't work from other locations? Yes, I tried three machines on our lan and the server itself. > 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. I can't use this via internet, since our server has no public IP. Uli.