From owner-freebsd-questions@FreeBSD.ORG Thu May 6 17:32:24 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E618F106564A for ; Thu, 6 May 2010 17:32:24 +0000 (UTC) (envelope-from tundra@tundraware.com) Received: from ozzie.tundraware.com (ozzie.tundraware.com [75.145.138.73]) by mx1.freebsd.org (Postfix) with ESMTP id A5CCB8FC1C for ; Thu, 6 May 2010 17:32:24 +0000 (UTC) Received: from [192.168.0.2] (viper.tundraware.com [192.168.0.2]) (authenticated bits=0) by ozzie.tundraware.com (8.14.4/8.14.4) with ESMTP id o46HWGfZ060470 (version=TLSv1/SSLv3 cipher=DHE-DSS-CAMELLIA256-SHA bits=256 verify=NO) for ; Thu, 6 May 2010 12:32:16 -0500 (CDT) (envelope-from tundra@tundraware.com) Message-ID: <4BE2FD22.3060302@tundraware.com> Date: Thu, 06 May 2010 12:32:18 -0500 From: Tim Daneliuk User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4 MIME-Version: 1.0 To: FreeBSD Mailing List References: <20100506172149.GA42430@thought.org> In-Reply-To: <20100506172149.GA42430@thought.org> X-Enigmail-Version: 1.0.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.5 (ozzie.tundraware.com [75.145.138.73]); Thu, 06 May 2010 12:32:16 -0500 (CDT) X-TundraWare-MailScanner-Information: Please contact the ISP for more information X-TundraWare-MailScanner-ID: o46HWGfZ060470 X-TundraWare-MailScanner: Found to be clean X-TundraWare-MailScanner-From: tundra@tundraware.com X-Spam-Status: No Subject: Re: ssh: port 22: connection refuused X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 May 2010 17:32:25 -0000 On 5/6/2010 12:21 PM, Gary Kline wrote: > > can anybody help me with ne of my last problems: getting ssh Into > my new comuter? i am able to ssh outside. need to scp my config > files over. > > sshd is running on "zen" > > This generally involves two or three steps: 1) Make sure /etc/rc.conf has this in it: sshd_enable="YES" 2) Make sure /etc/hosts.allow permits access to your machine via ssh. Something like this: sshd: 192.168. a_host-name.com an.ip.add.ress :ALLOW Some people do this: sshd: ALL :ALLOW That's fine if the machine sits on a trusted LAN, but I don't much like this for machines that are internet-facing ... it just provides another vector for attack. So, for such machines, I explicitly name the address and names that are permitted ssh access. 3) If you're running a firewall, make sure that the sshd ports (22/tcp and 22/udp) are open for those machines/addresses you want to connect into your FreeBSD box. If you are still having trouble, go to the client machine and invoke your session like this: ssh -vvvvv your_freebsd_machine It will barf out a bunch of interesting information about why the connection isn't working that may help you figure out what's going on. Happy Trails, ---------------------------------------------------------------------------- Tim Daneliuk tundra@tundraware.com PGP Key: http://www.tundraware.com/PGP/