Server to server communication

At points throughout this document inter server communication validations has been highlighted, this section provides a useful guide to the ports and direction required at each server within the solution. The latest traffic requirements and network environment preparation documentation is always available online and should be reviewed along with this guide.

All servers should be reachable (ping, telnet) using both their short names and FQDNs.

Port	2-way?	Origin	IP / FQDN	Destination	IP / FQDN	Change?	Description
22	Y	REPORTING or administrator's desktop		DNCA		N	Remote Secure Shell.
25	Y	REPORTING		SMTP		N	Sends mail via SMTP from components of Discover to the mail server.
80 / 443	Y	Portal thin client (Browser)		REPORTING		N	Thin Client Note: To enable effective replay, the Replay Server might require access to static content stored on the origin server. Typically, this access occurs over ports 80 or 443.
54054	Y	REPORTING		Remote SQL Server		Y	Needed only if Reporting DB is MSSQL and Report Server is on a platform other than MSSQL server.
1966	Y	DNCA		PROCESSING		Y	Captured data stream.
5597	Y	REPORTING		PROCESSING		Y	Communications between Portal and ctree session database on Canister.
8080 or 8443	Y		REPORTING or administrator's desktop		DNCA	Y	DNCA Status and configuration program.
19000	Y		PROCESSING		REPORTING	N	Searches and retrieves sessions via TCP/IP.
20000	Y		REPORTING + PROCESSING		REPORTING + PROCESSING	N	Communication for retrieving and sending configurations of Discover servers, components, and databases.
23000	Y		REPORTING		Discover database	N	Discover Data Service.
38000							Advanced replay configuration.

Tip

Note down instance IPs / Fully Qualified Domain Names (FQDN) against instances for your security team and organisation's records.