From owner-freebsd-questions@FreeBSD.ORG Tue Nov 23 03:37:23 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 912DF16A4CE for ; Tue, 23 Nov 2004 03:37:23 +0000 (GMT) Received: from out006.verizon.net (out006pub.verizon.net [206.46.170.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id D62F743D39 for ; Tue, 23 Nov 2004 03:37:22 +0000 (GMT) (envelope-from georgiev@vt.edu) Received: from bburg.bg ([151.199.112.157]) by out006.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20041123033722.VIPW4719.out006.verizon.net@bburg.bg> for ; Mon, 22 Nov 2004 21:37:22 -0600 From: Ivan Georgiev To: freebsd-questions@freebsd.org Date: Mon, 22 Nov 2004 22:37:19 -0500 User-Agent: KMail/1.7.1 References: <200411201921.27880.georgiev@vt.edu> <200411220005.33354.georgiev@vt.edu> <20041122220140.1c87273d@localhost> In-Reply-To: <20041122220140.1c87273d@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200411222237.19660.georgiev@vt.edu> X-Authentication-Info: Submitted using SMTP AUTH at out006.verizon.net from [151.199.112.157] at Mon, 22 Nov 2004 21:37:22 -0600 Subject: Re: NEW: cannot ssh to my computer 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: Tue, 23 Nov 2004 03:37:23 -0000 > > Just another thing ... > > > > If I remove myself from the group wheel then I CAN ssh to my computer; > > if I put myself back to wheel - then CANNOT ssh to the computer. > > > > How can I ssh and be a member of the wheel group? > > hello ivan, > > it might be worth your while to check /etc/login.access to see if you > have refused remote logins by wheel. > > hth, > epi Thank you so very much Epi !!! I guess I have put this -:wheel:ALL EXCEPT LOCAL in /etc/login.access but had no recollection of doing it. After commenting it out the problem is gone. Many thanks to all that helped solving my "mysterious"/trivial problem ! Regards, Ivan