From owner-freebsd-questions Tue Sep 10 22:20:09 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA11750 for questions-outgoing; Tue, 10 Sep 1996 22:20:09 -0700 (PDT) Received: from diablo.ppp.de (diablo.ppp.de [193.141.101.34]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id WAA11745 for ; Tue, 10 Sep 1996 22:20:06 -0700 (PDT) Received: from allegro.lemis.de by diablo.ppp.de with smtp (Smail3.1.28.1 #1) id m0v0hiK-000QiyC; Wed, 11 Sep 96 07:19 MET DST From: grog@lemis.de (Greg Lehey) Organisation: LEMIS, Schellnhausen 2, 36325 Feldatal, Germany Phone: +49-6637-919123 Fax: +49-6637-919122 Received: (grog@localhost) by allegro.lemis.de (8.6.9/8.6.9) id HAA23800; Wed, 11 Sep 1996 07:02:53 +0200 Message-Id: <199609110502.HAA23800@allegro.lemis.de> Subject: Re: Telnet delays out of 2.1.5 To: nc@ai.net (Network Coordinator) Date: Wed, 11 Sep 1996 07:02:53 +0200 (MET DST) Cc: questions@FreeBSD.org (FreeBSD Questions) In-Reply-To: from "Network Coordinator" at Sep 10, 96 08:03:02 pm X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-questions@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Network Coordinator writes: > > > We have installed 2.1.5 on two internal machines. One is a Pentium 150 > and one is a PentiumPro 200mhz. The first has 128MB of RAM and the other > 512MB. Telneting into each box provides excellent performance, but > whenever an FTP or telnet connection is attempted from either box, a long > delay ensues. > > Trying 1.1.1.1 > Connected > Hit ^] etc.. > > At this point it waits approximately 20-2minutes seconds. > > Then everything works fine. The receiving systems are not loaded at all, > so connections, etc should be fine. This happens between all other > machines including other 2.1.5 machines. None of our other BSD boxes are > doing this, and the receiving machines that are local are not even doing > reverse DNS lookups on these incoming requests. > > Any ideas or something I have overlooked? This is almost certainly a DNS problem. Try running tcpdump while somebody establishes a connection, and see what it's looking for. Greg