Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Notifications
Login / Register
Community
Community
Notifications
close
  • Forums
  • Knowledge Center
  • Events & Webinars
  • Ideas
  • Blogs
Help
Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Login / Register
Sustainability
Sustainability

Join our "Ask Me About" community webinar on May 20th at 9 AM CET and 5 PM CET to explore cybersecurity and monitoring for Data Center and edge IT. Learn about market trends, cutting-edge technologies, and best practices from industry experts.
Register and secure your Critical IT infrastructure

Router required open port numbers to run a Continuum system

Building Automation Knowledge Base

Schneider Electric Building Automation Knowledge Base is a self-service resource to answer all your questions about EcoStruxure Building suite, Andover Continuum, Satchwell, TAC…

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
  • Home
  • Schneider Electric Community
  • Knowledge Center
  • Building Automation Knowledge Base
  • Router required open port numbers to run a Continuum system
Options
  • Bookmark
  • Subscribe
  • Email to a Friend
  • Printer Friendly Page
  • Report Inappropriate Content
Invite a Co-worker
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send Invite Cancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Send New Invite Close

Related Forums

  • Intelligent Devices Forum

Previous Next
Contributors
  • DavidFisher
    DavidFisher
  • ScottLeedberg
    ScottLeedberg
  • PaulFr
    PaulFr
  • sesa119747
    sesa119747
  • AbeMeran
    AbeMeran
  • Product_Support
    Product_Support

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague Invite
Back to Building Automation Knowledge Base
Options
  • Bookmark
  • Subscribe
  • Email to a Friend
  • Printer Friendly Page
  • Report Inappropriate Content
0 Likes
5710 Views

Link copied. Please paste this link to share this article on your social media post.

Trying to translate this page to your language?
Select your language from the translate dropdown in the upper right. arrow
Translate to: English
  • (Français) French
  • (Deutsche) German
  • (Italiano) Italian
  • (Português) Portuguese
  • (Русский) Russian
  • (Español) Spanish

Router required open port numbers to run a Continuum system

Picard Product_Support
‎2018-09-07 12:37 AM

Issue

What port numbers do routers have to have open in order to run a Continuum system?

Product Line

Andover Continuum

Environment

  • Cyberstation
  • Continuum BACnet / Infinet Controllers
  • TCP/IP

Cause

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.

Resolution

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.

Labels (1)
Labels:
  • Andover Continuum
Tags (2)
  • Find more articles tagged with:
  • 2573
  • ethernet
Was this article helpful? Yes No
No ratings

Link copied. Please paste this link to share this article on your social media post.

To The Top!

Forums

  • APC UPS Data Center Backup Solutions
  • EcoStruxure IT
  • EcoStruxure Geo SCADA Expert
  • Metering & Power Quality
  • Schneider Electric Wiser

Knowledge Center

Events & webinars

Ideas

Blogs

Get Started

  • Ask the Community
  • Community Guidelines
  • Community User Guide
  • How-To & Best Practice
  • Experts Leaderboard
  • Contact Support
Brand-Logo
Subscribing is a smart move!
You can subscribe to this board after you log in or create your free account.
Forum-Icon

Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.

Register today for FREE

Register Now

Already have an account? Login

Terms & Conditions Privacy Notice Change your Cookie Settings © 2025 Schneider Electric

This is a heading

With achievable small steps, users progress and continually feel satisfaction in task accomplishment.

Usetiful Onboarding Checklist remembers the progress of every user, allowing them to take bite-sized journeys and continue where they left.

of