From owner-freebsd-questions  Wed Aug  7 11:22:32 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id LAA26785
          for questions-outgoing; Wed, 7 Aug 1996 11:22:32 -0700 (PDT)
Received: from kitty.oester.com (kitty.oester.com [206.25.136.13])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA26780
          for <questions@freebsd.org>; Wed, 7 Aug 1996 11:22:30 -0700 (PDT)
Received: from fatcat.oester.com by kitty.oester.com (8.6.12/1.37)
	id LAA15835; Wed, 7 Aug 1996 11:22:19 -0700
Message-ID: <3208DD99.1C0B@oester.com>
Date: Wed, 07 Aug 1996 11:16:57 -0700
From: "G.R.Gircys" <rich@oester.com>
Reply-To: rich@oester.com
Organization: Oesterreich & Assc. Inc.
X-Mailer: Mozilla 3.0b4Gold (Win95; I)
MIME-Version: 1.0
To: Cliff Addy <fbsdlist@revelstone.jvm.com>
CC: questions@freebsd.org
Subject: Re: tcp/ip problem:  long pause
References: <Pine.BSF.3.91.960807091416.5109A-100000@revelstone.jvm.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Cliff Addy wrote:
> 
> 
> Help!  What do I even *look* at?
> 
Very possible that your domain's in-addr is not setup or does not include
the server's rev IP mapping.

If this is the case, many (not all) machines you connect to will connect
right away, but then the machine you connected to tries to do a reverse
lookup (so that the hostname can be logged instead of the IP) and the 
long delay you see is the DNS timeout period.

Another, but less likely cause, is problems with newer tcp compliance. See
the /etc/sysconfig file and disable (NO) to tcp_extenions.

have fun,

rich