Question
Are there any suggested TCP parameters that should be changed on a Windows server running webNetwork.
Windows Server OS out of the box should function properly with webNetwork. However, some customers have had to follow this information from Microsoft due to their specific environment.
Solution
Increase the upper range of ephemeral ports that are dynamically allocated to client TCP/IP socket connections.
Start Registry Editor.
Browse to, and then click the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
On the Edit menu, click New, DWORD Value, and then add the following registry value to increase the number of ephemeral ports that can by dynamically allocated to clients:
MaxUserPort=65534 (Decimal)
Close Registry Editor
Reduce the client TCP/IP socket connection timeout value from the default value of 240 seconds.
Start Registry Editor.
Browse to, and then click the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
On the Edit menu, click New, DWORD Value, and then add the following registry value to reduce the length of time that a connection stays in the TIME_WAIT state when the connection is being closed. While a connection is in the TIME_WAIT state, the socket pair cannot be reused:
TcpTimedWaitDelay = 30 (Decimal)
Close Registry Editor
Restart the Server OS to activate these registry changes.
These changes helped some customers with server resources not being released in a timely manner on a high usage webNetwork server.
Info from the following msdn URL:
See the following Technet Blog post for more information on close_wait and time_wait: