Received: (from majordom@localhost)
	by hyperreal.org (8.8.5/8.8.5) id WAA05218;
	Thu, 4 Sep 1997 22:38:41 -0700 (PDT)
Received: from valis.worldgate.com (marcs@valis.worldgate.com [198.161.84.2])
	by hyperreal.org (8.8.5/8.8.5) with ESMTP id WAA05090
	for <new-httpd@apache.org>; Thu, 4 Sep 1997 22:37:48 -0700 (PDT)
Received: from localhost (marcs@localhost)
	by valis.worldgate.com (8.8.7/8.8.7) with SMTP id XAA20266
	for <new-httpd@apache.org>; Thu, 4 Sep 1997 23:37:38 -0600 (MDT)
Date: Thu, 4 Sep 1997 23:37:38 -0600 (MDT)
From: Marc Slemko <marcs@worldgate.com>
To: new-httpd@apache.org
Subject: Re: [BUG] 1.3 not closing socket on NT
In-Reply-To: <Pine.BSF.3.95q.970904230545.26119Y-100000@valis.worldgate.com>
Message-ID: <Pine.BSF.3.95q.970904232144.26119d-100000@valis.worldgate.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: new-httpd-owner@apache.org
Precedence: bulk
Reply-To: new-httpd@apache.org

See MS KB article Q170359 for how to tune the time it remains in
TIME_WAIT.  You should be able to drop it to 60 seconds without too much
hassle, but that doesn't really fix anything.  

Which of the traces you posted result in the server remaining in
TIME_WAIT?

There is something else going on here, but I think it is MS's problem.  I
don't have a NT box here right now to play with.

There are a few more things to be said about the length of the 2*MSL
timeout (it is not strictly based on the TTL) that are not quite fitting
together here, but more when I'm awake.