Full Disclosure mailing list archives
Re: Reverse engineering the Windows TCP stack
From: Thierry Zoller <Thierry () sniff-em com>
Date: Thu, 31 Mar 2005 21:52:33 +0200
Dear Pretty, <Afaik> That key does indeed control the number of times windows retries to connect, *but* its not supposed to take that number into account after it recieved an RST packet, it's supposed to act that way when no answer is received at all. </Afaik> pv> TcpMaxConnectRetransmissions pv> Key: Tcpip\Parameters pv> Value Type: REG_DWORD - Number pv> Valid Range: 0 - 0xFFFFFFFF pv> Default: 5 pv> Description: This parameter determines the number of times that TCP pv> retransmits a connect request (SYN) before aborting the attempt. The pv> retransmission timeout is doubled with each successive retransmission in a pv> particular connect attempt. The initial timeout value is three seconds. -- Thierry Zoller _______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.grok.org.uk/full-disclosure-charter.html Hosted and sponsored by Secunia - http://secunia.com/
Current thread:
- Re: Reverse engineering the Windows TCP stack, (continued)
- Re: Reverse engineering the Windows TCP stack Vladamir (Mar 25)
- Re: Reverse engineering the Windows TCP stack ADT (Mar 25)
- Re: Reverse engineering the Windows TCP stack Thierry Zoller (Mar 26)
- Re: Reverse engineering the Windows TCP stack Vladamir (Mar 26)
- Re: Reverse engineering the Windows TCP stack Georgi Guninski (Mar 28)
- Re: Reverse engineering the Windows TCP stack NSC (Mar 29)
- Re: Reverse engineering the Windows TCP stack Vladamir (Mar 24)
- Re: Reverse engineering the Windows TCP stack Thierry Zoller (Mar 31)