Sign In with your
Trend Micro Account
Need Help?
Need More Help?

Create a technical support case if you need further support.

Fine tuning the TCP/IP settings on Windows machines

    • Updated:
    • 9 Dec 2020
    • Product/Version:
    • Control Manager 7.0
    • InterScan Messaging Security Suite 7.1 Windows
    • InterScan Messaging Security Suite 7.5 Windows
    • InterScan VirusWall 7.0
    • ScanMail for Lotus Domino 5.0 Windows
    • ServerProtect for Microsoft Windows/Novell Netware 5.7
    • ServerProtect for Microsoft Windows/Novell Netware 5.8
    • Worry-Free Business Security Standard/Advanced 7.0
    • Worry-Free Business Security Standard/Advanced 8.0
    • Worry-Free Business Security Standard/Advanced 9.0
    • Platform:
    • N/A

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:

  1. Open the Registry Editor.
    Always back up the whole registry before making any modifications. Incorrect changes to the registry can cause serious system problems.
  2. Go to the HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters hive.
  3. 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

  4. Set the value to "65530" (decimal).
    By default, the value is 5000, but you can set it from 5000 to 65530.
  5. 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)

  6. Set the value to "60" (decimal). ​​
    These two keys ("MaxUserPort" and " TcpTimedWaitDelay") do not exist.
  7. Close the Registry Editor.
  8. Reboot the system for the changes to take effect.
Solution Id:
Did this article help you?

Thank you for your feedback!

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.