Network Ports used by ClearSCADA

[sbeadle1]

📖 Home  Back  
This article details ports used by ClearSCADA and should form the basis for configuration of system firewalls. For client-server connections, you need to create the firewall rules as described here.

The following table provides details about the protocols and ports used by the other ClearSCADA components, such as drivers. You may need to create firewall rules for those components and features (if any) that your system is using.



The table shows which ports are used by the various ClearSCADA components. The information is categorized under these headings:

• Protocol - Indicates the protocol used by the port (TCP or UDP)

• Port(s) - Shows the port or ports that are used by the server or clients. The table shows the numbers for the default ports (you can configure your system to use different ports)

• Incoming Connection - Indicates the component that receives the connection request

• Outgoing Connection - Indicates the component that attempts to open the connection

Protocol	Port(s)	Incoming Connection	Outgoing Connection	Description
TCP or UDP	-	Devices	Drivers	The protocol and ports used by TCP/IP channels for the connections between the devices and the drivers. You can configure the protocol and port by adjusting the Port and TCP/IP Type settings on the Connection tab of the Channel Form in ViewX.
TCP or UDP	-	Outstations	Drivers	The protocol and ports used by network outstations (outstations that have Ethernet ports that are connected to a network). You can configure the port by adjusting the Port setting(s) on the Network tab of the Outstation Form in ViewX. The protocol for the port(s) is defined by the outstation's network channel (see below).
TCP or UDP	-	Drivers	Outstations	The protocol and ports used by network channels (channels that are used to connect to network outstations - see above). You can configure the protocol and port by adjusting the Listen Port\Port and TCP/IP Type settings on the Connection tab of the Channel Form in ViewX.
TCP	502	Outstations	Modbus Driver	The port is used by Modbus TCP outstations. You can configure the port by adjusting the Port setting on the Primary Port and Secondary Port tabs of the Scanner Form in ViewX.
TCP	502	Modbus Slave Driver	Modbus TCP Masters	The port is used by Modbus TCP slave outstations. This port is fixed and cannot be re-configured.
ICMP		Any Network Device	ICMP Driver	Used to test the connection between the main server and any network device. A ping is used to test the connection. You can configure the device by adjusting the Device setting on the Digital Point tab of the Point Form in ViewX. The ICMP protocol does not have ports.
TCP	102	Siemens PLCs	Simatic S7 Driver	The port is used by Siemens Simatic S7 network scanners. You can configure the port by adjusting the Port settings on the Primary Connection and Secondary Connection tabs on the Scanner Form in ViewX.
TCP	-	OPC XML-DA Servers	OPC XML-DA Driver	The port is used by OPC XML-DA servers. You can configure the port by adjusting the OPC Server URL setting on the Server tab of the Server Form in ViewX. The URL includes the server and port of the OPC server, for example, http://opcsvr:8080/xmlda/ for  a ClearSCADA server called 'opcsvr' on port 8080.
UDP	123	NTP Servers	NTP Driver	The port is being used by the Network Time Protocol servers. You can configure the NTP server by adjusting the NTP Server setting on the Scanner tab of the Scanner Form in ViewX. The protocol and port are fixed and cannot be re-configured.
TCP	20876	Port Server	Drivers	The ports used for remote serial channels (dynamic ports). This is fixed and cannot be re-configured. Each serial port will use a different TCP/IP port number.
TCP	-	Port Server	Drivers and Third Party	The port for remote serial channels (static ports). You can configure the static ports by editing the HKEY_LOCAL_MACHINE\SOFTWARE\Serck Controls\SCX6\PortServer/Ports registry key. The name of each value in the key is a port number. For more information, see the Port Server documentation in the Server Administration Guide in ClearSCADA Help.
TCP	0	Server	Telnet Clients	The ports used by the Telnet server for server monitoring. Each Telnet server will use a different port. The port that is currently being used is shown in the General\Information\Telnet Server section of the Server Status Tool. You can configure the port by using the System Configuration\Logging\Server\Telnet Port setting on the Server Configuration Tool. For more information, see the Server Administration Guide in ClearSCADA Help.
TCP	0	Drivers	Telnet Clients	The ports used by the Telnet server for driver monitoring. Each Telnet server will use a different port. The port that is currently being used is shown in the Telnet Port column in the General/Modules section of the Server Status Tool. You can configure the port by right-clicking on the individual driver in the General/Modules section of the Server Status Tool and then choosing the Logging option. This displays the Logging Configuration window. On the Configuration tab, you can change the port that is used by the driver by entering the required port number in the Telnet Port field.
TCP	0	Drivers (Channels)	Telnet Clients	The port is used by the Telnet server for driver channel communications logging. The port that is currently being used in shown in the View window for the relevant channels. You can configure the port by using the Enable Telnet pick action and entering the required port at the prompt. You can also define the port as a parameter for the EnableTelnet method.
TCP	0	Port Server	Telnet Clients	The port is used by the Telnet server for port server logging. The port that is currently being used is shown in the header of log files. You can configure the port by editing the HKEY_LOCAL_MACHINE\SOFTWARE\Serck Controls\SCX6\PortServer\LogTelnetPort registry key. For more information, see the Port Server documentation in the Server Administration Guide in ClearSCADA Help.
TCP	0	License Server	Telnet Clients	The port is used by the Telnet server for license server logging. The port that is currently being used is logged in the header of log files. You can configure the port by editing the HKEY_LOCAL_MACHINE\SOFTWARE\Serck Controls\SCX6\LicenceServer\LogTelnetPort registry key.
TCP	0	Alarm and Event Printer	Telnet Clients	The port is used by the Telnet server for OPC alarm and event printer logging. The port that is currently being used is shown in the header of log files. You can configure the port by editing the HKEY_LOCAL_MACHINE\SOFTWARE\Serck Controls\SCX6\AEPrinter\LogTelnetPort registry key.

Notes

• In this article, the term 'Telnet client' refers to any computer that is running a Telnet client application to access ClearSCADA diagnostics.

• The term 'Drivers' refers to any driver that is installed on the ClearSCADA server except the internal drivers (Logic and QP - Query Processor).

• The term 'Devices' refers to any SCADA device or application that accepts telemetry protocol via a network connection, for example:

• Comtrol DeviceMaster

• Port Server (Static Port)

• The term 'Modbus TCP Master' refers to any master station (or similar) that has a Modbus TCP driver (including other ClearSCADA servers).

• Port 0 means that this will be a dynamically assigned port (assigned by the operating system by default). You will need to configure and assign a specific port and then create a firewall rule for the port.

• Where no port is specified, the port is configured in the database or registry by a user and there is no default setting.

• Firewalls that support per program exceptions can be configured to unblock those ClearSCADA programs that require network access.

Go: Home Back