This article outlines information relating to the network used in a Dalet project (ports used, communication between servers, etc)
Site Network Requirements for Dalet Solutions
Please read the in-depth, dedicated article Network Hardware Requirements on the hardware and configurational aspects.
Dalet Flex
The load balancers must expose the following ports:
- TCP/80 (HTTP)
- TCP/443 (HTTPS)
- more network related info can be found in Dalet Flex Operational Requirements for Customer-Hosted Deployments
Dalet Pyramid
The load balancers only expose the following ports:
- TCP/80 (HTTP)
- TCP/443 (HTTPS)
- more network related info can be found in Dalet Pyramid - Operational Requirements for Customer's Dedicated Deployment
Dalet Galaxy and Legacy DaletPus
Since Dalet Galaxy 4.0.302,DCl has been retired in favor of GRPC https://grpc.io/. gRPC static range: 8400-8499. gRPC dynamic range:8 500-8999. Detailed information on gRPC and Dalet Galaxy can be found in gRPC Secure Communication in Dalet Galaxy five.
Port specification for Dalet applications are listed in the tables below.
DIS and DIS 2 rquire the Internet Control Message Protocol (ICMP) to be enabled.
Unless started differently, all communication below is based on the TCP Unicast protocol . As the vast majority of sites implement a stateful firewall, there is no need to configure bidrectional rules.
You can use powershell commands to open the firewall. Here are some examples:
1. netsh advfirewall firewall add rule name="SQL Port" dir=in action=allow protocol=tcp localport=1433
2. netsh advfirewall firewall add rule name="NameServiceServer" dir=in action=allow protocol=tcp localport=7874
3. for /L %i in (7900,1,9000) do netsh advfirewall firewall add rule name="DaletPlus Port" dir=in action=allow protocol=tcp localport=%i
For Dalet Galaxy Dalet Galaxy older than Dalet Galaxy 4.0.302: Dalet original applications (DaletPlus, Galaxy) communicate over the Dalet Communication Layer (DCL), following these specifications:
- Dynamically allocated ports for DCL communication, between these port ranges: 7900-9000 (used for all Dalet communications, server & client)
- Some specific applications subscribe to the NameServer with fixed HTTP endpoints (hard-coded or configurable)
- Specifically for the 4.0.302 branch (S2 2018), these port ranges are required as well: 50050-51150 (this can be changed to the default 7900-9000 using a flag)
Dalet Galaxy Ports Flow
Note: Dalet applications use Windows' standard dynamic port range (also known as "ephemeral port range") as source ports for Dalet traffic.
This port range can be configured in Windows using standard configuration methods.
More information : https://support.microsoft.com/en-us/help/929851/the-default-dynamic-port-range-for-tcp-ip-has-changed-in-windows-vista
|
Application/Service |
Source | Destination | Ports | Configuration | Comments |
|
General |
|||||
| Dalet Communication Layer (legacy) |
Any Dalet client |
Any Dalet client Any Dalet server |
7900-8399 | N/A | |
|
Dalet Communication Layer (gRPC static range) |
Any Dalet client Any Dalet server |
Any Dalet client Any Dalet server |
8400-8499 | N/A | This is the broad Static range; more specific rules are listed below |
| Dalet Communication Layer (gRPC dynamic range) |
Any Dalet client |
Any Dalet client |
8500-8999 | N/A |
Version 4.0.302: also 50050-51150 |
|
SQL |
|||||
| JDBC SQL |
Any Dalet server |
SQL Server | 1433 | SQL Server Management | |
|
MSSQL Browser (optional) |
MSSQL Browser | SQL Server | 1434 | SQL Server Management | Optional |
|
Core |
|||||
|
Dalet Name Server |
Any Dalet client |
NameServer hosts | 8500 | DtkFlag | (before 4.0.302: 7874) |
|
Dalet Service |
Any host running DaletServiceAdmin or Remote Admin | Any host running Dalet agents | 8484 | DtkFlag | (before 4.0.302: 7869) |
| DaletPlus Server | Any Dalet client |
Dalet Plus Server |
7900 and up | One port per DaletPlusServer per host, starting from 7900 | |
| DaletPlus Dispatch |
Any Dalet client |
Dalet database cluster hosts, Dalet clustered Dispatch virtual host | 5080 | ||
| Notifier / NATS Server | Any Dalet client Any Dalet Server |
Any host running Notifier Server or NatsServer |
NATS 8480 Notifier 8480-8483 |
N/A |
As of version 4.0.352 SP1, NATS replaces the Notifier Server. Previous ports (before 4.0.352): 7859, 7868 NOTE: NATS port 8480 is the default port for the SOLR server (depending on the Dalet Galalxy version.. On connection problems, change the port of the SOLR server or move a server to a different host. NOTE: Dalet Galaxy five 4.0 (4.0.336) SP6 is the only version which requires both Notifier and NATS |
|
Chat |
|||||
| Dalet Chat Server |
Any Dalet client |
Any host running DaletChatServer | 8400, 8401 | Remote Admin > Agent Properties |
Before version 4.0.352: 7442, 7443. Note: XtendToPremiereServer uses the same default port. You can change the Chat Server port in: C:\ProgramData\Dalet\Data\openfire.MAMDEMO-DaletChatServer_1@DEMO-MAM\conf\hazelcast.xml |
| Dalet Chat Server Administrator Console |
Administration console host |
Dalet Chat Server | 9093 | Remote Admin > Agent Properties | |
| Dalet Chat Server HTTP Client Port (also Webspace) |
Any Dalet client |
Any Dalet client Any WebSpace client |
5222 | Remote Admin > Agent Properties | |
| DaletChatServer HTTPS Client Port (also Webspace) | Any Dalet client Any WebSpace client |
Any Dalet client |
5223 | Remote Admin > Agent Properties | |
|
SolR (Search) |
|||||
| Dalet Search Server (SolR 4.6) |
Any Dalet client |
Dalet Solr Server | 8485-8489 | SolR deployment/assignment config |
Before 4.0.352: 9707 and up (one per agent running on the host).
|
| Dalet Search Server (SolR 7.5) | Any Dalet client Any Dalet server |
Dalet Solr Server |
8485-8489 |
SolR deployment/assignment config | |
|
API |
|||||
|
Dalet SOAP WebService (API1) |
Any Dalet Core Server Any 3rd party system integrating with Dalet API |
Dalet WebService Server | 8440 | Remote Admin > Agent Properties | Before 4.0.352: 8080 |
|
Dalet WebService (API2) |
Any Dalet Core Server Any 3rd party system integrating with Dalet API |
Dalet WebService Server | 8431, 8432 | Remote Admin > Agent Properties |
2 ports needed: WebService (API Endpoint) and iPython (useful for development, but not needed for production. Can be disabled) Before 4.0.352: 8080 (endpoint) and 8088 (iPython) |
|
Dalet WebService3 (API3) |
Any Dalet Core Server Any 3rd party system integrating with Dalet API |
Dalet WebService Server | 8410 | Remote Admin > Agent Properties | |
|
BPM |
|||||
|
Workflow Server |
Any client |
Workflow Server | 8420 | Remote Admin > Agent Properties | Galaxy and Web clients |
|
Dalet Message Queue |
Any Dalet Server | Message Queue Server | 8450 | A new port is needed when a new DaletMessageQueue is added on a host | |
|
Notifier JMS |
Any Dalet Server | Notifier JMS Server | 8003-8103 | Remote Admin > JMS Cluster | One range of 100 ports per NotifierJMS agent. By default, only one is needed for BPM/WorkflowServer. |
|
WebSpace |
|||||
| WebSpace Server HTTP | Any WebSpace client | Any WebSpace Server |
9090 |
Agent command line |
Add "-port XXXX" to end of the agent command line. |
|
WebSpace Server HTTPS |
Any WebSpace client | Any WebSpace Server | 443 | Agent command line | |
| WebSpace Upload Agent | Any WebSpace client | Any WebSpace Server | 0 (random) |
Remote Admin > Agent Properties |
The value "0" is for dynamic allocation. It is recommended to change this port. |
| Ingest Data Server |
Any WebSpace client |
Any WebSpace Server | 8408 | Remote Admin > Agent Properties | |
| Video / Audio Streaming |
Any WebSpace client |
Any Wowza Server | 1935 | Wowza configuration | |
| Secure Video / audio streaming |
Any WebSpace client |
Any Wowza Server |
1936 | Wowza configuration | |
| Workflow Server (BPM) |
Any WebSpace client |
Workflow Server | 8420 | Remote Admin > Agent Properties | |
| Frame Accurate Streaming Server |
Any WebSpace Server |
Frame Accurate Streaming Server Any WebSpace Server |
5711 | Remote Admin > Agent Properties | Both WebSpace and Thumbnail Servers communicate with FASS via the configured port. |
| Dalet Streaming Server | Dalet Streaming Server |
Any WebSpace Server |
0 (random) | Remote Admin > Agent Properties |
Webspace media preview for TrackStack. |
|
Dashboard |
|||||
|
IcingaAgent |
Icinga Server | Any monitored machine | 10101 | Remote Admin > Dashboard | Configuration server |
| IcingaAgent | Any monitored machine | Icinga Server | 10102 | ||
|
Icingaweb Dashboard |
Any Dashboard client | Icinga Server | 80, 443 | Docker port mapping | HTTP / HTTPS access to the server should be allowed from any host a user can connect from |
|
Grafana |
Any dashboard client | Icinga Server | 3000 | N/A | |
| Graphite | Any dashboard client | Icinga Server |
9093 |
N/A | For administration purposes |
|
NSClient monitoring agent |
Icinga Server | Any monitored machine | 5666 | N/A | |
|
Additional Application Servers |
|||||
| Dalet Xtend | NLE client with Xtend plugin | Dalet Xtend server |
Win: 8400 |
Remote Admin > Agent Properties |
Win/Mac is given as an indication; ports can be changed |
| Social Media Server | Any Dalet client |
Social Media Server |
8461 | Remote Admin > Agent Properties | |
|
OnePlay Server |
Any Dalet Server | Dalet OnePlay Server | 8531 | Remote Admin > Agent Properties | |
|
Remote Editing Server |
OneCutSA Remote Editing client | Remote Editing Server | 8456 | Remote Admin > Agent Properties | |
| On The Go | Mobile client (smartphone, tablet) | MobileApplicationServer | 8080 | Remote Admin > Agent Properties |
Hardcoded configuration port: 8081. To stream via Wowza, make sure the streaming ports are open. |
| Audit Trail | Any Dalet Server | SQL Server hosting Audit Trail | 1433 |
SQL Server configuration |
|
|
MOS Server |
Dalet MOS Gateway (server) | 3rd Party Mos Device |
MOM 10540 |
Remote Admin > Agent Properties / MOS Device | |
|
DIS - Dalet Installer |
|||||
| DIS 2.0 Administration | Web Interface client | DIS Server |
9095, 9098 [ICMP protocol has to be enabled, used in some java api for host status detection] |
DIS setup wizard |
|
| DIS 2.0 Deployment | DIS Server |
All Galaxy clients |
8406 [ICMP protocol has to be enabled, used in some java api for host status detection] |
N/A |
ActiveMQ Agent |
| DIS Server | All Galaxy clients All Galaxy Servers |
135, 49152-65535 [ICMP protocol has to be enabled, used in some java api for host status detection] |
Windows specific | WMI - used to install DaletInstallerService remotely on hosts | |
|
All Galaxy clients |
DIS Server |
8405, 9096 [ICMP protocol has to be enabled, used in some java api for host status detection] |
N/A |
8405: ActiveMQ Server 9096: Download of DIS agent |
|
| DIS 1.5 | Deployment Machine | All Galaxy clients All Galaxy Servers |
9999 [ICMP protocol has to be enabled, used in some java api for host status detection] |
N/A |
|
|
3rd Party Systems |
|||||
| Amazon S3 | Dalet Servers | AWS S3 regional endpoint | 80, 443 | N/A |
Interface to S3/Glacier |
|
Amberfin Transcoder service |
Dalet Servers | Amberfin Servers | 21012 | N/A |
Interface for Dalet to control Amberfin transcoder |
| Amberfin Workflow engine | Dalet Servers | Amberfin Servers | 31013 | N/A |
Interface for Dalet to control Amberfin Workflow engine |
|
FTP |
Any host connecting to FTP | Any Dalet Client Any Dalet server |
20, 21 | Vendor-specific | Ports given as an indication; customer might choose others |
| Rhozet | Rhozet | Any Dalet Client Any Dalet server |
TCP: 1120 |
N/A |
|
| SMB/CIFS |
Dalet Servers Dalet clients |
Storage, Domain controllers |
139, 445 | N/A | File Access to NAS storage |
|
SMTP |
Dalet Servers | SMTP Server(s) | 25 | N/A |
Emails TODO: update once we can use SMTP over TLS |
|
Time Sync |
Any Dalet Client |
TimeSync server |
TCP: 37 |
N/A | Time synchronization SNTP = UDP; Unitime = TCP |
|
Tableau |
Any Dalet server | 27000-27009 | N/A | TODO: looks wrong. to recheck | |
| YouTube | Dalet Migration Servers |
YouTube and associated services (e.g. auth) |
80, 443 | N/A | Full list of target hosts to be determined at implementation time |
Dalet Amberfin
|
Service/Function |
Port |
Description |
Comments |
|
Asteroid Device.exe |
50822 |
CORBA port for engine that performs File analysis, playback and ingest functions. Accessed by the Amberfin GUI |
|
|
Metashare.exe |
59577 |
CORBA port Amberfin library clip library manager. Accessed by Amberfin GUI. |
|
|
Safenet Network License Communications (Legacy) |
5093 (UDP) |
Safenet Network License Service. Communication between Local License Manager and Sentinel Service. |
Legacy - up to v11.8.10 |
|
Safenet License Communication (Legacy) |
14139 |
Local License Manager. Used for communication between components (Ingest, Asteroid) and Local License Manager |
Legacy - up to v11.8.10 |
|
LimeLM License Communication |
55053 |
License System Comms - gRPC |
From v11.9 onwards |
|
LimeLM License Communication |
55054 |
License System Comms - gRPC |
From v11.9 onwards |
|
Webservices legacy API |
8080 |
Amberfin Legacy Web Services port for Job Management. Accessed by external systems SOAP calls, but should use gateway |
Legacy SOAP APIs are also available via the gateway on 21012. |
|
Amberfin UQC Communications |
8081 |
HTTP port for QC job management. Accessed by the Controller. |
|
|
AmberFin Dark Services |
21021 |
Controller, Framework Manager, Profile Service, Gateway, Service APIs' |
|
|
AmberFin Workflow Services |
31013 |
Workflow Engine Service, Workflow Manager, Workflow REST API, Kiosk UI (Central), User Tasks |
|
|
Amberfin Management Service |
11091 |
Component Manager, Log Collection, Analytics |
|
|
Transcoder Ports |
22022…+1010 |
Range starting from 22022, 23032, 24042 etc…. |
|
|
Kiosk |
3002 |
|
|
|
AmberFin Controller Datastore (H2) |
9092 |
Default port for H2 database |
H2 Only |
|
AmberFin Workflow Datastore (H2) |
9093 |
Default port for H2 database |
H2 Only |
|
SQL Server default TCP Port |
1433 |
Default port for installations using SQL Server database instead of H2 (Controller and Workflow) |
SQL Server |
Dalet Radio Suite HD and older
*All TCP ports have to be open
*Dalet dynamically assigns ports all over the available port-range
Dalet Brio
|
Brio service
|
Remote
|
REST
|
TCP
|
gRPC
|
Thrift
|
|
Dalet Brio Amazon S3 copier
|
|
|
9081
|
|
|
|
Dalet Brio Anywhere Copier
|
|
|
9082
|
|
|
|
Dalet Brio Avid copier
|
|
|
9083
|
|
|
|
Dalet Brio BVW Player A
|
|
|
|
||
|
Dalet Brio BVW Player B
|
|
|
|
||
|
Dalet Brio BVW Player C
|
|
|
|
||
|
Dalet Brio BVW Player D
|
|
|
|
||
|
Dalet Brio BVW Recorder A
|
|
|
|
||
|
Dalet Brio BVW Recorder B
|
|
|
|
||
|
Dalet Brio BVW Recorder C
|
|
|
|
||
|
Dalet Brio BVW Recorder D
|
|
|
|
||
|
Dalet Brio Database Server
|
9120
|
9120
|
|
|
|
|
Dalet Brio FTP copier
|
|
|
9084
|
|
|
|
Dalet Brio Router Controller
|
9111
|
9111
|
|
|
|
|
Dalet Brio VTR Controller
|
9170
|
9170
|
|
|
|
|
Dalet Brio Backup Copier
|
DCOM
|
|
|
9080
|
|
|
Dalet Brio NMOS
|
9300
|
9300
|
|
|
|
|
Dalet Brio NMOS Connection management
|
9302
|
9302
|
|
|
|
|
Dalet Brio NMOS Registration
|
9301
|
9301
|
|
|
|
|
Dalet Brio Aspect Ratio Changer
|
8080
|
8080
|
|
|
|
|
Dalet Brio Extractor A
|
DCOM
|
|
|
9031
|
|
|
Dalet Brio Extractor B
|
DCOM
|
|
|
9032
|
|
|
Dalet Brio Extractor C
|
DCOM
|
|
|
9033
|
|
|
Dalet Brio Extractor D
|
DCOM
|
|
|
9034
|
|
|
Dalet Brio Extractor E
|
DCOM
|
|
|
9035
|
|
|
Dalet Brio Extractor F
|
DCOM
|
|
|
9036
|
|
|
Dalet Brio Extractor G
|
DCOM
|
|
|
9037
|
|
|
Dalet Brio Extractor H
|
DCOM
|
|
|
9038
|
|
|
Dalet Brio Mover A
|
DCOM
|
|
|
9041
|
|
|
Dalet Brio Mover B
|
DCOM
|
|
|
9042
|
|
|
Dalet Brio Mover C
|
DCOM
|
|
|
9043
|
|
|
Dalet Brio Mover D
|
DCOM
|
|
|
9044
|
|
|
Dalet Brio Mover E
|
DCOM
|
|
|
9045
|
|
|
Dalet Brio Mover F
|
DCOM
|
|
|
9046
|
|
|
Dalet Brio Mover G
|
DCOM
|
|
|
9047
|
|
|
Dalet Brio Mover H
|
DCOM
|
|
|
9048
|
|
|
Dalet Brio RTP Mosaic Server
|
9101
|
|
|
9101
|
|
|
Dalet Brio RTP Gateway
|
9102
|
|
|
9102
|
|
|
Dalet Brio Streaming Server Player A
|
8080
|
8080
|
|
|
|
|
Dalet Brio Streaming Server Player B
|
8081
|
8081
|
|
|
|
|
Dalet Brio Streaming Server Player C
|
8082
|
8082
|
|
|
|
|
Dalet Brio Streaming Server Player D
|
8083
|
8083
|
|
|
|
|
Dalet Brio Streaming Server Player E
|
8084
|
8084
|
|
|
|
|
Dalet Brio Streaming Server Player F
|
8085
|
8085
|
|
|
|
|
Dalet Brio Streaming Server Player G
|
8086
|
8086
|
|
|
|
|
Dalet Brio Streaming Server Player H
|
8087
|
8087
|
|
|
|
|
Dalet Brio Streaming Server Recorder A
|
8090
|
8090
|
|
|
|
|
Dalet Brio Streaming Server Recorder B
|
8091
|
8091
|
|
|
|
|
Dalet Brio Streaming Server Recorder C
|
8092
|
8092
|
|
|
|
|
Dalet Brio Streaming Server Recorder D
|
8093
|
8093
|
|
|
|
|
Dalet Brio Streaming Server Recorder E
|
8094
|
8094
|
|
|
|
|
Dalet Brio Streaming Server Recorder F
|
8095
|
8095
|
|
|
|
|
Dalet Brio Streaming Server Recorder G
|
8096
|
8096
|
|
|
|
|
Dalet Brio Streaming Server Recorder H
|
8097
|
8097
|
|
|
|
|
Dalet Brio VDCP A
|
10521
|
|
10521
|
|
|
|
Dalet Brio VDCP B
|
10522
|
|
10522
|
|
|
|
Dalet Brio VDCP C
|
10523
|
|
10523
|
|
|
|
Dalet Brio VDCP D
|
10524
|
|
10524
|
|
|
|
Dalet Brio VDCP E
|
10525
|
|
10525
|
|
|
|
Dalet Brio VDCP F
|
10526
|
|
10526
|
|
|
|
Dalet Brio VDCP G
|
10527
|
|
10527
|
|
|
|
Dalet Brio VDCP H
|
10528
|
|
10528
|
|
|
|
Dalet Brio VDCP Gateway
|
10500
|
|
10500
|
|
|
|
Dalet Brio VDCP File system
|
|
|
|
||
|
Dalet Brio FTP Server
|
21
|
|
21
|
|
|
|
Dalet Brio Portal
|
9200
|
9200
|
|
|
|
|
Dalet Brio Player API
|
9160
|
9160
|
|
|
|
|
Dalet Brio File System API
|
9150
|
9150
|
|
|
|
|
Dalet Brio Logs Collector
|
9180
|
9180
|
|
9009
|
|
|
Dalet Brio Socket logging server
|
|
|
11111-11127 11130-11147 11150-11153 11170,11180 |
|
|
|
Dalet Brio Sentinel Service
|
DCOM
|
|
|
9010
|
|
|
Dalet Brio Board Control Service
|
|
|
|
||
|
Dalet Brio Manager
|
9100
|
9100
|
|
|
|
|
Dalet Brio Player A
|
DCOM
|
|
|
9011
|
|
|
Dalet Brio Player B
|
DCOM
|
|
|
9012
|
|
|
Dalet Brio Player C
|
DCOM
|
|
|
9013
|
|
|
Dalet Brio Player D
|
DCOM
|
|
|
9014
|
|
|
Dalet Brio Player E
|
DCOM
|
|
|
9015
|
|
|
Dalet Brio Player F
|
DCOM
|
|
|
9016
|
|
|
Dalet Brio Player G
|
DCOM
|
|
|
9017
|
|
|
Dalet Brio Player H
|
DCOM
|
|
|
9018
|
|
|
Dalet Brio Recorder A
|
DCOM
|
|
|
9021
|
|
|
Dalet Brio Recorder B
|
DCOM
|
|
|
9022
|
|
|
Dalet Brio Recorder C
|
DCOM
|
|
|
9023
|
|
|
Dalet Brio Recorder D
|
DCOM
|
|
|
9024
|
|
|
Dalet Brio Recorder E
|
DCOM
|
|
|
9025
|
|
|
Dalet Brio Recorder F
|
DCOM
|
|
|
9026
|
|
|
Dalet Brio Recorder G
|
DCOM
|
|
|
9027
|
|
|
Dalet Brio Recorder H
|
DCOM
|
|
|
9028
|
|
|
Dalet Brio FIMS Capture Service
|
9000
|
9000
|
|
|
|
|
Dalet Brio FIMS Transfer Service
|
9001
|
9001
|
|
|
|
|
Dalet Brio PTP Server
|
|
|
|
||
|
Dalet Brio Ingest Scheduler
|
9140
|
9140
|
|
|
|
| Dalet Brio Streaming Monitor | 8433 |
Comments
4 comments
Broken link: gRPC Secure Communication in Dalet Galaxy five
What ports exactly are required for Galaxy's DaletAdmin and DaletServiceAdmin to communicate correctly?
Hi Fabien, the link has been fixed.
8484
Please sign in to leave a comment.