Newsgroup: it.comp.os.win.nt
Titolo: time wait su iis (netstat -a)

praticamente...mi succede quanto descritto nel KB (nt4sp6a iis4.0
patchato)..che però sembra un problema già risolto da tempo quando
invece non mi sembra proprio. Sarebbe un'idea forzare il server nel
registry (tcpip/parameters) in modo che possa "controllare" il keep
alive connectione come da altro kb?
scusate per il post kilometrico....
KeepAliveInterval
          Key: Tcpip\Parameters
          Value Type: REG_DWORD - Time in milliseconds
          Valid Range: 1 - 0xFFFFFFFF
          Default: 1000 (one second)
          Description: This parameter determines the interval separating
keep alive retransmissions until a response
          is received. Once a response is receive, the delay until the
next keep alive transmission is again controlled
          by the value of KeepAliveTime. The connection will be aborted
after the number of retransmissions
          specified by TcpMaxDataRetransmissions have gone unanswered.
   KeepAliveTime
          Key: Tcpip\Parameters
          Value Type: REG_DWORD - Time in milliseconds
          Valid Range: 1 - 0xFFFFFFFF
          Default: 7,200,000 (two hours)
          Description: The parameter controls how often TCP attempts to
verify that an idle connection is still
          intact by sending a keep alive packet. If the remote system is
still reachable and functioning, it will
          acknowledge the keep alive transmission. Keep alive packets
are not sent by default. This feature may be
          enabled on a connection by an application.
   The information in this article applies to:
          Microsoft Windows NT Server version 4.0
          Microsoft Windows NT Server Enterprise Edition version 4.0
          Microsoft Windows NT Server version 4.0, Terminal Server
Edition
   SYMPTOMS
   There is a small time window in Afd.sys (the Microsoft Winsock2
service provider for TDI transport) where it does not
   indicate data received immediately after a connection is accepted.
This window should affect only applications that use
   AcceptEx with buffer space for receiving data after a connection is
accepted.
   CAUSE
   In TCP/IP, timewait state queue management has a problem that causes
time wait states to exceed four minutes under
   stress.
   RESOLUTION
   To resolve this problem, obtain the latest service pack for Windows
NT 4.0 or Windows NT Server 4.0, Terminal Server
   Edition. For additional information, please see the following article
in the Microsoft Knowledge Base:
          Q152734 How to Obtain the Latest Windows NT 4.0 Service Pack
   For your convenience, the English version of this post-SP3 hotfix has
been posted to the following Internet location.
   However, Microsoft recommends that you install Windows NT 4.0 Service
Pack 4 to correct this problem.
ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/NT40/hotfixes-postSP3/iis4-fix/
   NOTE: The above link is one path; it has been wrapped for
readability.
   STATUS
   Microsoft has confirmed this to be a problem in Windows NT 4.0 and
Windows NT Server 4.0, Terminal Server Edition. This
   problem was first corrected in Windows NT 4.0 Service Pack 4.0 and
Windows NT Server 4.0, Terminal Server Edition
   Service Pack 4


KeepAliveInterval


   KeepAliveTime




   SYMPTOMS

   CAUSE

   RESOLUTION






ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/NT40/hotfixes-postSP3/iis4-fix/

   STATUS

--
Posted from [195.223.199.140] 
via Mailgate.ORG Server - 
http://www.Mailgate.ORG