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

Create a technical support case if you need further support.

Communication ports in Control Manager (TMCM)

    • Updated:
    • 20 Oct 2015
    • Product/Version:
    • Control Manager 6.0
    • Platform:
    • Windows 2003 Enterprise Server
    • Windows 2003 Standard Server Edition
    • Windows 2008 Enterprise
    • Windows 2008 Standard
Summary

This article contains the list of the communication ports in TMCM.

Details
Public

Here is a list of communication ports that TMCM uses:

HTTP console port of TMCM

  • Source: Trend Micro products and administrators who will connect to the web browser
  • Destination: TMCM
  • Destination Port: TCP port 80 by default. This can vary, depending on the IIS settings of each customer.
  • Details: HTTP port of website where TMCM is configured. TMCM is placed in the default website. MCP agents use this port to connect to the TMCM server, and vice versa if the low security option is selected, or when the medium option is selected and HTTPS is unavailable. Products also connect to the HTTP port to download updates.

HTTPS console port of TMCM

  • Source: Trend Micro products and administrators who will connect to the web browser
  • Destination: TMCM
  • Destination Port: TCP port 443 by default. This may vary depending on the IIS settings of each customer.
  • Details: HTTPS port of website where TMCM is configured. TMCM is placed in the default website. MCP agents use this port to connect to the TMCM server, and vice versa if the low security option is selected, or when the medium option is selected and HTTPS is unavailable. Some products also connect to the HTTPS port to download updates.

TMI proprietary port (From TMCM to TMI Agent)

  • Source: Trend Micro products that use TMI Agent
  • Destination: TMCM
  • Destination Port: TCP port 10319
  • Details: TMI-based agents use this port to connect to the server and vice versa. Examples are Trend Micro ServerProtect and ScanMail for Domino for AS400.

MI proprietary port (From TMI Agent to TMCM)

  • Source: TMCM
  • Destination: Trend Micro products that use TMI Agent
  • Destination Port: TCP port 10319
  • Details: TMI-based agents use this port to connect to the server and vice versa. Examples are Trend Micro ServerProtect and ScanMail for Domino for AS400.

TMI Interprocess port

  • Source: Control Manager server
  • Destination: TMCM server
  • Destination Port: TCP port 10198
  • Details: In case that customers enable server firewall, please make sure to port this internal communication port.

Heartbeat processes of TMCM agents

  • Source: Trend Micro products
  • Destination: TMCM server
  • Destination Ports:

    UDP 10319 – Heartbeat port for TMI-based agents
    UDP 10323 – Heartbeat port for MCP-based agents

  • Details: This port is used by the Control Manager server to listen if the products are still alive.

Web service-based agents

  • Description: For Web Service-based agents, the TMCM server must be able to connect to the console of the product.
  • Source: TMCM server
  • Destination: Trend Micro products

    TCP port 4119 – Deep Security port, Vulnerability Protection
    TCP port 4343 – Officescan console port, Trend Micro Security for Macintosh port
    TCP port 8080 – Endpoint Encryption port

Cloud-based products

  • Source: TMCM server
  • Destination: sco-nabu.trendmicro.com
  • Destination ports: TCP ports 80 and 443
  • Details: The TMCM server connects to the this website to get information about cloud-based products (Hosted Email Security, Interscan Web Security as a Service, Worry-free Business Security Services).

SMTP port for notifications (Optional)

  • Source: TMCM server
  • Destination: SMTP Service
  • Destination Port: TCP 25 by default. This can vary depending on the SMTP service used by customers.
  • Details: TMCM may send notifications by SMTP service

Syslog port for notifications (Optional)

  • Source: TMCM server
  • Destination: Syslog server used by customers
  • Destination Port: UDP 514. This can vary depending on the Syslog servers used by customers.
  • This is the default destination port for sending TMCM data to a named syslog server.

MSN Instant Messaging Protocol for notifications (Optional)

  • Source: TMCM server
  • Destination: MSN online services. http://*.messenger.msn.com.
  • Destination Port: TCP 1863
  • Details: Msn ports for notifications.

Trend Micro Network Time protocol (in case service is started; Optional)

  • Source: Trend Micro products
  • Destination: TMCM
  • Destination Port: UDP 123
  • Details: It is possible to use TMCM as a Network Time Server. This is done by enabling the Trend Micro Network Time Service and disabling the Windows time service on the local machine. This is mostly for appliance-based products, to allow TMCM and appliance to have the same time. This is not recommended to be used anymore.
Premium
Internal
Rating:
Category:
Configure
Solution Id:
1038211
Feedback
Did this article help you?

Thank you for your feedback!

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.

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.


Need More Help?

Create a technical support case if you need further support.