FlashFXP Forums - View Single Post - Possible solution to dropped connections after transfer

bigstar · 09-21-2003, 04:41 PM

I found the following information which may resolve dropped connections which occur after a transfer has completed.

** On Windows NT:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\TcpIp\Parameters\

KeepAliveTime
Key: Tcpip\Parameters
Value Type: REG_DWORD - Time in milliseconds
Valid Range: 1 - 0xFFFFFFFF
Default: 7,200,000 (two hours)
Description: The parameter controls how often TCP attempts to verify that an idle connection is still intact by sending a keep alive packet. If theremote system is still reachable and functioning, it will acknowledge the keep alive transmission. Keep alive packets are not sent by default. This feature may be enabled on a connection by an application.

KeepAliveInterval
Key: Tcpip\Parameters
Value Type: REG_DWORD - Time in milliseconds
Valid Range: 1 - 0xFFFFFFFF
Default: 1000 (one second)
Description: This parameter determines the interval separating keep alive retransmissions until a response is received. Once a response is receive, the delay until the next keep alive transmission is again controlled by the value of KeepAliveTime. The connection will be aborted after the number of
retransmissions specified by TcpMaxDataRetransmissions have gone unanswered.

** On Win 9x, these parameters are to be created under

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\VxD\MSTCP

The KeepAliveTime determines how often a keep alive packet is sent to a TCP/IP socks. The default is two hours, which is too long. It is recommended that this value be set between 60000
and 300000 (1 to 5 minutes). Make sure that the "decimal" radio button is selected prior to typing this number into the Data field in the Registry Editor.

You will need to reboot windows for this new setting to take effect.

Please let us know if this solves your problem.

09-21-2003, 04:41 PM
bigstar FlashFXP Developer Join Date: Oct 2001 Posts: 8,012	Possible solution to dropped connections after transfer I found the following information which may resolve dropped connections which occur after a transfer has completed. On Windows NT: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\TcpIp\Parameters\ KeepAliveTime Key: Tcpip\Parameters Value Type: REG_DWORD - Time in milliseconds Valid Range: 1 - 0xFFFFFFFF Default: 7,200,000 (two hours) Description: The parameter controls how often TCP attempts to verify that an idle connection is still intact by sending a keep alive packet. If theremote system is still reachable and functioning, it will acknowledge the keep alive transmission. Keep alive packets are not sent by default. This feature may be enabled on a connection by an application. KeepAliveInterval Key: Tcpip\Parameters Value Type: REG_DWORD - Time in milliseconds Valid Range: 1 - 0xFFFFFFFF Default: 1000 (one second) Description: This parameter determines the interval separating keep alive retransmissions until a response is received. Once a response is receive, the delay until the next keep alive transmission is again controlled by the value of KeepAliveTime. The connection will be aborted after the number of retransmissions specified by TcpMaxDataRetransmissions have gone unanswered. On Win 9x, these parameters are to be created under HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\VxD\MSTCP The KeepAliveTime determines how often a keep alive packet is sent to a TCP/IP socks. The default is two hours, which is too long. It is recommended that this value be set between 60000 and 300000 (1 to 5 minutes). Make sure that the "decimal" radio button is selected prior to typing this number into the Data field in the Registry Editor. You will need to reboot windows for this new setting to take effect. Please let us know if this solves your problem.