[e2e] Is this a bug with Windows TCP Stack ?

[sanjay kaniyar]

Winsock API has subtle semantics, I am not totally sure but something like
this could result in the observed trace:

- IIS does send
- does Shutdown(SD_SEND) -> data and FIN go out.
- setsockopt(Linger = OFF)
- closesocket		-> RST goes out.

But I don't want to spread speculation - I got someone here at Microsoft to
run a test which does the following with IIS 6.0:

- client establishes a connection, sends a get request
- server sends a response and closes the connection -> Data and FIN go out
- FIN gets acked.
 <no RST is seen>

So, I would think there is something specific to the setup. If Goutham can
send the details (and the test application if possible), we can take a
closer look.

Thanks,
Sanjay



-----Original Message-----
From: Ted Faber [mailto:faber at ISI.EDU] 
Sent: Monday, December 06, 2004 8:30 AM
To: sanjay kaniyar
Cc: end2end-interest at postel.org
Subject: Re: [e2e] Is this a bug with Windows TCP Stack ?

On Sun, Dec 05, 2004 at 11:59:45AM -0800, sanjay kaniyar wrote:
> In this case, Windows TCP is not sending the RST on its own from
FIN_WAIT_2 
> - IIS must have closed the connection.

The close is what put the connection into FIN_WAIT_1, and getting an ACK
after close put it into FIN_WAIT_2.  IIS can't close it again.  I hope.

-- 
Ted Faber
http://www.isi.edu/~faber           PGP:
http://www.isi.edu/~faber/pubkeys.asc
Unexpected attachment on this mail? See
http://www.isi.edu/~faber/FAQ.html#SIG