Secure Network Ports

For a secure system we recommend that ClearSCADA is set up in a firewalled environment. This section describes the ports used so that firewalls can be set up appropriately.

ClearSCADA TCP Ports

ClearSCADA uses network ports for various forms of client / server and device communication. These are dependent on the protocols and ports configured in the ClearSCADA database. A guide is available here:

http://resourcecenter.controlmicrosystems.com/display/public/CS/Network+Ports+used+by+ClearSCADA

ClearSCADA DBServer uses a database server port for all native ClearSCADA communications. This is used to synchronize one server with another server, ViewX client access, and client API access (for example COM, ODBC, .Net). The default port is 5481. Generally there’s no reason this should be modified, but it can be changed through the Database Manager, the Server Configuration Tool, or (while the server is stopped) by altering the following registry key:

HKLM\SOFTWARE\Schneider Electric\ClearSCADA\DB\Port

If you use a non-default database instance, (for example if you are running multiple ClearSCADA instances on a node), the key becomes:

HKLM\SOFTWARE\Schneider Electric\ClearSCADA-<instance name>\DB\Port

The server port number needs to match the port number configured on clients in the Configure Connections utility, and needs to match the port numbers configured on other servers for database synchronization.

ViewX clients listen on a separate TCP port to allow the server to connect to the client and deliver real-time updates. This port must be open for the client to access the server, and appropriate measures should be taken to allow firewalls to pass this connection through. The default port range is 5000 – 5009 and can be modified using the ClearSCADA Client Applet.

The OPC client connections also require this port.


Disclaimer

ClearSCADA 2017 R2