From owner-freebsd-current Sun Mar 2 23:29:11 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 125E637B401 for ; Sun, 2 Mar 2003 23:29:10 -0800 (PST) Received: from heron.mail.pas.earthlink.net (heron.mail.pas.earthlink.net [207.217.120.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0109943F85 for ; Sun, 2 Mar 2003 23:29:09 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0033.cvx22-bradley.dialup.earthlink.net ([209.179.198.33] helo=mindspring.com) by heron.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 18pkNl-00001P-00; Sun, 02 Mar 2003 23:29:06 -0800 Message-ID: <3E6303EE.9516823A@mindspring.com> Date: Sun, 02 Mar 2003 23:27:42 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Andre Guibert de Bruet Cc: Wayne Barnes , current@FreeBSD.ORG Subject: Re: can't sshd into box References: <20030303000955.A69139@klentaq.com> <20030303020915.B59207@alpha.siliconlandmark.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4484b23930f674c99a42b4adad8c73520350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Andre Guibert de Bruet wrote: > On Mon, 3 Mar 2003, Wayne Barnes wrote: > > Immediately after rebooting, I get this: > > > > root@etaq3:/home/wayne>telnetd -debug > > telnetd: bind: Address already in use > > > > This doesn't happen on my other (working) system. > > Could this be a clue to my problem? > > Telnetd is telling you that something else is listening on port 23. This > is most probably inetd. Do a 'killall inetd' then try that command. That's not only going to stop inetd from sitting on the port, it will probably also make telnet into the box start working, if it's related to the TCP wrappers (if he had modified his hosts.allow with the advice from a previous poster, he would not be having this problem, if that happens, so rather than posting his problem over and over again, maybe he should read the responses, and at least tell us if they worked?). Otherwise, another common culprit is ipfw; if he has the firewall enabled, the default is to block everything. Given that he got a connection, and that it was subsequently closed, though, rather than not getting a connection at all, it's a safe bet that it's the TCP wrappers, not the ipfw, that is causing the trouble. In which case, he should take the advice on the hosts.allow file contents that he was given earlier, and it will fix his problem... -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message