From owner-freebsd-sparc64@FreeBSD.ORG Sun Sep 5 17:16:39 2004 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3461116A4CE for ; Sun, 5 Sep 2004 17:16:39 +0000 (GMT) Received: from mta13.adelphia.net (mta13.mail.adelphia.net [68.168.78.44]) by mx1.FreeBSD.org (Postfix) with ESMTP id AD82643D3F for ; Sun, 5 Sep 2004 17:16:38 +0000 (GMT) (envelope-from ababurko@adelphia.net) Received: from ample.adelphia.net ([24.52.224.96]) by mta13.adelphia.net (InterMail vM.6.01.03.02 201-2131-111-104-20040324) with ESMTP id <20040905171638.GNFX24693.mta13.adelphia.net@ample.adelphia.net> for ; Sun, 5 Sep 2004 13:16:38 -0400 Message-Id: <5.2.1.1.0.20040905131400.01b63898@mail.dc2.adelphia.net> X-Sender: ababurko@mail.dc2.adelphia.net X-Mailer: QUALCOMM Windows Eudora Version 5.2.1 Date: Sun, 05 Sep 2004 13:16:37 -0400 To: sparc64@FreeBSD.org From: Bob Ababurko Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: RE: 5.3beta2 X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Sep 2004 17:16:39 -0000 I should probably not that I can log in via ssh if I am on a console. My console is just a pc,running hyperterm. But get the error from a remote session attempt which is actually on the same network. -bob >hello- > > I am not sure if this is fit for this list but we'll soon find > out...... I just installed 5.3 beta2 on my Ultra2 and I am not able to > log into the box remotely via ssh. I am trying to log in with a user > that I created, eg. not root. What I get is: > >"unable to authenticate using any of the configured authentication methods" > > The reason that I post this hdere is because before the system comes > up, there was a screen asking for random characters to be typed in. This > is where the prob;em may be as I left the console before that happened > and that event timed out. This is the only thing that I can think of. I > have checked the config of sshd and it looks the same as the rest of my others. > Maybe this has happened to someone else out there....i hope! ANy help > will be much appreciated. > >/bob