KB34971: What TCP/IP ports are used by the MicroStrategy Product Suite?

The Strategy Product Suite uses the following TCP/IP ports:
Strategy Intelligence Server 
The Strategy Intelligence Server listens for client connections from all Strategy clients on TCP port 34952 by default. This port is configurable when setting up the Intelligence Server. Cluster synchronization traffic between Intelligence Server nodes uses this same client port.
Strategy Listener
The Strategy Listener service allows users to monitor and control Strategy services on remote machines. The Listener listens for connections on TCP and UDP port 30172.
Strategy Web/Web Services/Mobile
Clients connect to Strategy Web/Web Services/Mobile using the port configured on the web server hosting the Strategy web application.
Strategy Web/Web Services/Mobile connects to the Strategy Intelligence Server on the Intelligence Server configured client port, by default TCP 34952.
Strategy Narrowcast Server
Strategy Narrowcast Server uses several ports to communicate between the Narrowcast components:

• Distribution Manager
  
• Listens for incoming connections on TCP port 11343. This port is not configurable.
• DCOM is used to trigger Narrowcast Services in the Distribution Manager. Narrowcast uses TCP port 135 and UDP ports 1024-5000 for DCOM communication. Consult the Windows System Administrator if changing these ports is desired.
• Logging Client
  
• The Narrowcast components connect to the Logging Client to log messages recorded to the DELogs.
• Listens for incoming connections on TCP port 20009. This port is configurable in the Narrowcast Administration Console.
• Logging Server
  
• The Logging Server aggregates logging messages from the Logging Clients.
• Listens for incoming connections from Logging Clients on TCP port 20020 by default. This port is configurable in the Narrowcast Administration Console.
• Relays logging messages to the Logging Consumer on TCP port 20030 by default. This port is configurable in the Narrowcast Administration Console.
• Relays logging messages to interested clients on TCP port 20040 by default. This port is configurable in the Narrowcast Administration Console. The Narrowcast Administration Console System Message Viewer connects to the Logging Server on this port.
• Logging Consumer
  
• Listens for incoming connections from the Logging Server on TCP port 20030 by default. This port is configurable in the Narrowcast Administration Console.

Refer to the following Strategy Knowledge Base technical note for more information on how to change the ports used by the Strategy Narrowcast Logging Services:
KB34759 - How to modify the network ports used by the Strategy 9.x logging services
Strategy Narrowcast Server connects to the Strategy Intelligence Server on the Intelligence Server configured client port, by default TCP 34952.
Strategy Clients
All Strategy clients connect to the Strategy Intelligence Server on the Intelligence Server configured client port, by default TCP 34952. This list of clients includes:

• Strategy Developer
• Strategy Command Manager
• Strategy Object Manager
• Strategy Integrity Manager
• Strategy Enterprise Manager
• Strategy System Manager
• Strategy Tools (License Manager, Project Mover, Cube Advisor, ScanMD)
• custom Strategy clients built with the Strategy SDK

 
DataDirect SequeLink ODBC Socket Server
Strategy Narrowcast Server comes bundled with the DataDirect Sequelink ODBC Socket Server. This service allows the Narrowcast Subscription Portal to interact with the Narrowcast repositories. Refer to the following technical note for more information on SequeLink:
KB14843 - SequeLink Frequently Asked Questions in Strategy Narrowcast Server 9.x
By default, the SequeLink services listen for incomming connections from the Subscription Portal or Strategy Web on TCP ports 19995 and 19996.
 
Strategy Health Center
Strategy Health Center Master Health Agent listens for incoming connections from Health Agents and the Health Center Console on TCP port 44440 by default. This port is configurable when setting up the Master Health Agent. The Master Health Agent checks for updates from Strategy by connecting to TCP port 443, https.