Date: Thu, 06 May 2010 12:32:18 -0500 From: Tim Daneliuk <tundra@tundraware.com> To: FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: ssh: port 22: connection refuused Message-ID: <4BE2FD22.3060302@tundraware.com> In-Reply-To: <20100506172149.GA42430@thought.org> References: <20100506172149.GA42430@thought.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4BE2FD22.3060302>