FlashFXP Forums - View Single Post

Lunatik · 04-05-2005, 06:51 PM

I discovered that with Win 2003 SP1 for some reason the FTP Socket is getting stuck in a TIME_WAIT state.

Because of the new design microsoft did with the tcp/ip stack with sp1, if the state does not go to ESTABLISHED then windows will kick out the connection after 60 seconds.

As a temporary messure to get around the issue sending a NOOP command every so often will keep the connection up as it uses a new client port number, however it causes a problem with users not wanting to allow the noop command because of idling.

04-05-2005, 06:51 PM
Lunatik Member Join Date: Nov 2002 Posts: 40	Win 2003 SP1 & TCP_WAIT issue I discovered that with Win 2003 SP1 for some reason the FTP Socket is getting stuck in a TIME_WAIT state. Because of the new design microsoft did with the tcp/ip stack with sp1, if the state does not go to ESTABLISHED then windows will kick out the connection after 60 seconds. As a temporary messure to get around the issue sending a NOOP command every so often will keep the connection up as it uses a new client port number, however it causes a problem with users not wanting to allow the noop command because of idling.