When you encounter socket errors, it means that the system you are trying to connect to might have used up all its available sockets. This is common on machines with intensive network activities, such as databases, proxies, gateways, or other servers.
Here are some examples of WSA socket errors:
- Error Number: 10054
Connection reset by peer.
An existing connection was forcibly closed by the remote host. This normally results if the peer application on the remote host is suddenly stopped, the host is rebooted, or the remote host used a "hard close". - Error Number: 10061
Connection refused.
No connection could be made because the target machine actively refused it. This usually results from trying to connect to a service that is inactive on the foreign host - i.e. one with no server application running.
Trend Micro products function within the TCP/IP boundaries of the underlying operating system. To fine tune the TCP/IP settings of the machine, do the following TCP tweaks:
- Open the Registry Editor. Always back up the whole registry before making any modifications. Incorrect changes to the registry can cause serious system problems.
- Go to the HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters hive.
- For the products other than InterScan Messaging Security Suite (IMSS), add the following registry key with the following details: This step may cause failure for IMSS to listen on 10024 (or 10025 and 10026).
registry name: MaxUserPort
Data type: REG_DWORD
Range: 5,000-65,534 (port number) Default value: 5000 - Set the value to "65530" (decimal).
- On the same hive, add the following registry key and details:
registry name: TcpTimedWaitDelay
Data type: REG_DWORD
Range: 0x0 0x12C (0-300 seconds)
Default value: 0x78 (120 seconds = 2 min) - Set the value to "60" (decimal). These two keys ("MaxUserPort" and " TcpTimedWaitDelay") do not exist.
- Close the Registry Editor.
- Reboot the system for the changes to take effect.
