On Wed, Apr 2, 2008 at 1:57 PM, Haines Brown <[EMAIL PROTECTED]> wrote: > Eduardo M KALINOWSKI <[EMAIL PROTECTED]> writes: > > > > Haines Brown wrote: > >> debug1: Server will not fork when running in debugging mode. > >> debug1: rexec start in 4 out 4 newsock 4 pipe -1 sock 7 > >> debug1: inetd sockets after dupping: 3, 3 > >> debug1: Connection refused by tcp wrappe > > > > The last line is the key. While I cannot say for certain the cause, I'd > > check the /etc/hosts_allow and /etc/hosts_deny files to see if they are > > allowing ssh access. > > Yes, if I got those files wrong, I'd be in serious trouble. In > hosts.deny I have simply: > > ALL: ALL > > which I understand denies all hosts access except those mentioned in > hosts.allow. In hosts.allow I have: > > ALL:LOCAL > sshd: 192.168.0.3 > > My /etc/hosts: > > 127.0.0.1 localhost.localdomain localhost > 192.168.1.1 router.hartford-hwp.com router > 192.168.1.4 teufel.hartford-hwp.com teufel > 192.168.1.3 langhans.hartford-hwp.com langhans > > In the hosts.allow, I list simply the laptop that I would like to use as > a SSH client, not the shared rounter, as you will note. Should I have > listed the router instead of langhans (the laptop)?
No, the router only passes packages along, in the same sub-net it is only acting as a hub (actually, like a switch.) However, I see 192.168.0.3 (zero) in /etc/hosts_allow, and 169.168.1.3 (one) in the hosts file. If this is not a typo, could as well be the cause. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
