What port numbers do routers have to have open in order to run a Continuum system.
- Continuum BACnet / Infinet Controllers
There have been many questions on which network ports the Continuum system uses for communication. Below is a listing of the network ports along with what the port is being used for.
The destination UDP port from the controller will always be one of the below port numbers. The source UDP port that the controller uses is completely arbitrary and will be anywhere from 32768 to 65534. (0x8000 to 0xFFFE)
Controller/Cyberstation Application Packet type Decimal port number Hex Port numbers
Controller Error Log Tool - UDP 33487 0x82CF
BACNet B4 controller Point Configuration UDP 33487 0x82CF
BACNet B4 controller Alarm Configuration, Alarms, and COV UDP 47808 0xBAC0
BACNet B4 controller Controller flash TCP 33456 0x82B0
BACNet B4 controller Web Server TCP 80
NetController Point Configuration, Alarms, and Events UDP 33487 0x82CF
Netcontroller Save from Controller TCP 33440 0x82A0
NetController Controller flash TCP 33456 0x82B0
Sending Email TCP 25
NetController WebServer TCP 80 (but configurable)
CX9702 ** Point Configuration, Alarms, and Events See Note 33487 0x82CF
CX9702 ** Save from Controller See Note 33440 0x82A0
CX9702 ** Controller flash See Note 33456 0x82B0
CX9702 ** WebServer See Note 80 (but configurable)
** Note: UDP or TCP port (user configurable via the TransportType attribute)
Remote View Remote view Video TCP 18772 0x4954
CyberStation Controller Alarms and Events UDP 33487 0x82CF
CyberStation Peer Cyberstation communication UDP 44224 (1.4x and 1.5x), 47808 (all other revisions)
0xACC0 (1.4x and 1.5x), 0xBAC0 (all other revisions)
CyberStation Workstation to SQL database TCP Determined by Microsoft, 1433 by default
CyberStation BACNet communication UDP 47808 0xBAC0
CyberStation MSMQ TCP 1801 0x0709
CyberStation MSMQ UDP 3527 0x0DC7
CyberStation MSMQ UDP 1801 0x0709
CyberStation MSMQ RPC 135 0x0087
CyberStation MSMQ RPC 2101*,2103*, 2105* 0x0835, 0x0837, 0x0839
*Message Queuing message traffic and internal session management traffic between Queue Managers is delivered over Winsock through reserved TCP port 1801.
The Message Queuing Independent Client multicasts a server discovery broadcast over reserved UDP port 1801.
Message Queuing Servers listen on TCP port 2101* for RPC-based MQIS and Active Directory lookups. Message Queuing 3.0 independent clients and Message Queuing servers make MQIS requests directly to Active Directory by using LDAP on TCP port 389.
Message Queuing Independent Clients and Servers listen on fixed TCP port 2103* and 2105* for RPC-based remote reads of their public queues and private queues. Also, the Dependent Client uses these two ports to communicate with its server for send and for receive.
There is a dynamic RPC port that is assigned by the RPC layer for handshaking with an Independent Client or with an RPC server for the Message Queuing Server to determine the fixed ports. This is typically port 135.
The internal "ping" mechanism for Message Queuing operates over reserved UDP port 3527.
When you use HTTP messaging in Message Queuing 3.0, Message Queuing message traffic and internal session management traffic between Queue Managers is delivered over Winsock through reserved TCP port 1801.
* These port numbers may be incremented by 11 if the initial choice of RPC port is being used when Message Queuing initializes. A connecting QM queries port 135 to discover the 2xxx ports.
For more information on MSMQ ports check with Microsoft, http://support.microsoft.com/kb/178517
A .PDF document containing this Network Port information can be downloaded Here.