Quantcast
Channel: StudioSysAdmins Message Board
Viewing all articles
Browse latest Browse all 3749

Weird Windows TCP behavior

$
0
0
Weird Windows TCP behavior
posted by Jean-Francois Panisset on Nov. 17, 2015, 12:20 a.m.
I've got two identical machines running Windows 8.1 Pro, same Windows updates, connected to ports on the same switch. One has no problems talking to HTTP servers, the other one does.

On the one that works fine, I see the expected behavior of a graceful TCP connection shutdown initiated by the http server:

HTTP Server -> FIN, ACK
Good Client -> ACK
Good Client -> FIN, ACK
HTTP Server -> ACK
Good Client -> [SYN]
and so on. But on the "bad" client:

HTTP Server -> FIN, ACK
Bad Client -> ACK
Bad Client -> [SYN]

so it acknowledges the connection shutdown from the server, but never sends its own, and things then start falling apart.

I'm quite baffled, and getting close to just nuking the machine and reinstalling Windows, but that seems like a morally bankrupt way of dealing with the problem?

No attempted has been made to tweak TCP Delayed Ack on either machine.

I know this is a long shot, but just in case someone's seen this before and can say "oh yes, HKLM/THE_STUPID_PARAMETER_THAT_HAS_NO_REASON_TO_BE_DIFFERENT"


JF


Thread Tags:
  discuss-at-studiosysadmins 

0 Responses   0 Plus One's   0 Comments  
 
I've got two identical machines running Windows 8.1 Pro, same Windows updates, connected to ports on the same switch. One has no problems talking to HTTP servers, the other one does.

On the one that works fine, I see the expected behavior of a graceful TCP connection shutdown initiated by the http server:

HTTP Server -> FIN, ACK
Good Client -> ACK
Good Client -> FIN, ACK
HTTP Server -> ACK
Good Client -> [SYN]
and so on. But on the "bad" client:

HTTP Server -> FIN, ACK
Bad Client -> ACK
Bad Client -> [SYN]

so it acknowledges the connection shutdown from the server, but never sends its own, and things then start falling apart.

I'm quite baffled, and getting close to just nuking the machine and reinstalling Windows, but that seems like a morally bankrupt way of dealing with the problem?

No attempted has been made to tweak TCP Delayed Ack on either machine.

I know this is a long shot, but just in case someone's seen this before and can say "oh yes, HKLM/THE_STUPID_PARAMETER_THAT_HAS_NO_REASON_TO_BE_DIFFERENT"


JF



Viewing all articles
Browse latest Browse all 3749

Trending Articles