Versions: 6.7.x, 6.8.x, 2003.x

The following technical tip should be used with caution. If you misuse the Registry Editor (Regedit.exe), you may cause very serious problems that may require you to completely reinstall your Windows operating system. Use the Registry Editor at your own risk.

As you may already know, 4D, 4D Client or 4D Server use the TCP/IP protocol to communicate over the network. When 4D sends a TCP packet over the network, it asks the TCP driver to send the packet. The driver calls other low-level commands and sends the packet over the network. The destination driver receives the request and forwards the packet to the destination application. If 4D asks to send a TCP packet and the driver returns an error, 4D will try again for a few times and if they fail, it will report an error. This behavior also applies to the TCP/IP driver. When the driver encounters a problem when sending a packet, it will try again for a few times. If it still cannot send the packet, it reports the result to the application requesting the transfer.


The following URL is an article that Microsoft published showing how to configure TCP/IP under Windows XP.
http://support.microsoft.com/default.aspx?scid=kb;en-us;314053

This article can be useful to resolve disconnection problems between 4D Client and 4D Server on overloaded networks. The parameters that can be useful are KeepAliveInterval and TcpMaxDataRetransmissions.
TcpMaxDataRetransmissions is the maximum number of attempts the driver will make. However, all of these attempts must be performed in less than the interval defined by KeepAliveInterval (in milliseconds).