Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Discuss] 'nother question



rich pieri writes:
> On Tue, 7 Aug 2012 19:10:44 -0400
> dan moylan <jdm at moylan.us> wrote:
>>   debug1: connect to address 192.168.0.103 port 22: Connection refused
>>   ssh: connect to host 192.168.0.103 port 22: Connection refused
>>   lost connection

> "Connection refused" typically means one of three things:

> 1. No daemon listening on that port.  Solution: confirm that sshd is
> actually running on the remote host.  Also check sshd_config to ensure
> that it is listening on port 22.

> 2. TCP wrappers rejecting connections on that port.  Solution: check
> hosts.deny on the remote host.  If you are running denyhosts then you
> may need to add an exception in hosts.allow to permit local traffic.

> 3. A firewall rule blocking connections on that port.  Solution: fix
> your iptables configuration file.

sigh ... nr 1. it was; thanks, i knew that.

ole dan

j. daniel moylan
84 harvard ave
brookline, ma 02446-6202
617-232-2360 (tel)
jdm at moylan.us
www.moylan.us
[death to html bloat!]



BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org