Re: Windows 2003 Server - Remote Socket Restrictions
- From: "Arkady Frenkel" <arkadyf@xxxxxxxxxxxxxxxx>
- Date: Tue, 11 Oct 2005 09:13:19 +0200
Even more twice of that , because TcpTimedWaitDelay reg key by default is 4
min ( twice of MSL which is 2 min )
Arkady
"Alexander Nickolov" <agnickolov@xxxxxxxx> wrote in message
news:OajbHrbzFHA.1168@xxxxxxxxxxxxxxxxxxxxxxx
> After re-reading your question, it seems you are trying to go
> against the TCP protocol on purpose (maybe I misread
> something?). Perhaps you were exploiting a hole in Win2K
> that was plugged in Win2K3? The latter did tighten security...
>
> BTW, the TIME_WAIT timeout is 2 minutes, not 2 seconds.
>
> --
> =====================================
> Alexander Nickolov
> Microsoft ex-MVP [VC], MCSD
> email: agnickolov@xxxxxxxx
> MVP VC FAQ: http://www.mvps.org/vcfaq
> =====================================
>
> "Joe" <Joe@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:3A2CBD0E-2A7E-4E78-B2A9-E0DE9B9179DD@xxxxxxxxxxxxxxxx
>> Hello,
>>
>> We are porting our application from Windows 2000 Professional to Windows
>> 2003 Server. We are communicating with a remote device which makes a
>> client
>> connection to our server every second. Things work fine for weeks at a
>> time
>> on Windows 2000. On Windows 2003 Server, the remote device is no longer
>> able
>> to connect after a few minutes .
>>
>> Using Ethereal we have determined that the Windows 2003 Server system
>> does
>> not acknowledge connection attempts from the remote device when the
>> device
>> reuses a socket which is in the TIME WAIT state on the server.
>>
>> After reviewing the device's TCP/IP stack code we have found that it can
>> theoretically reuse the same client socket once the socket's TIME WAIT
>> period
>> of 2 seconds has expired.
>>
>> We are about to change the device's behaviour but we would still like to
>> confirm that this is the expected behaviour under Windows 2003 Server.
>>
>> So, our question is:
>> Has something changed in Windows 2003 server with regards to
>> acknowledging
>> connection attempt from client sockets which are currently in the time
>> wait
>> state on the server?
>>
>> Joe
>
>
.
- References:
- Re: Windows 2003 Server - Remote Socket Restrictions
- From: Alexander Nickolov
- Re: Windows 2003 Server - Remote Socket Restrictions
- Prev by Date: Re: WSAENOBUFS error on CAsyncSocket::Receive()
- Next by Date: Re: How to detect computer restart/reboot programmatically?
- Previous by thread: Re: Windows 2003 Server - Remote Socket Restrictions
- Next by thread: Re: Re:How to modify list of preferred wireless networks?
- Index(es):
Relevant Pages
|
