Ports used by Archive Shuttle

The following table shows the network communication ports used by Archive Shuttle. These ports are provided for reference for the situation where a firewall exists between the source and target environments in the archive migration.

SOURCE Destination Port(s) Description
Module Servers Archive Shuttle Server TCP 80 (HTTP)
TCP 443 (HTTPS)
HTTP/S Communication from Modules to Archive Shuttle Servers (*1)
Export / Import Module Servers Storage Servers (CIFS Shares) TCP 445 (CIFS) Access to CIFS Shares (*2)
Archive Shuttle Server SQL Server TCP 1433 (MSSQL) Access to Microsoft SQL Server hosting the Archive Shuttle databases
Archive Shuttle Server DNS Servers UDP 53 (DNS) Access to DNS for Windows
Archive Shuttle Server Domain Controllers TCP 88 (Kerberos)
TCP 445 (CIFS)
Access to Domain Controllers for Windows
Enterprise Vault Module Servers Enterprise Vault Servers Please see your Enterprise Vault documentation on what ports are needed for the Enterprise Vault API to talk to Enterprise Vault
Exchange Module Servers Exchange Servers Please see your Microsoft Exchange documentation on what ports are needed to talk to Microsoft Exchange (MAPI/EWS)
Office 365 Module Servers Office 365 TCP 443 (HTTPS) HTTPS communication from Archive Shuttle Office 365 Module to Office 365
SourceOne/EMX Module SQL Server TCP 1433 (MSSQL) Access to Microsoft SQL Server hosting the SourceOne/EMX databases
Zantas EAS Module SQL Server TCP 1433 (MSSQL) Access to the Microsoft SQL Server hosting the EAS database
Zantas EAS Module Zantas App Server TCP 443 (HTTPS)
TCP 80 (HTTP)
HTTP(S) communication with the Zantas EAS application server
Metalogix Archive Manager Module SQL Server TCP 1433 (MSSQL) Access to the Microsoft SQL Server hosting the Metalogix Archive Manager database
Metalogix Archive Manager Module Metalogix App Server TCP 443 (HTTPS)
TCP 80 (HTTP)
HTTP(S) communication with the Metalogix Archive Manager application server

(*1) If the Archive Shuttle core is configured to use HTTPS, then port 443 needs to be open on any firewalls. If the core is configured to use HTTP, then port 80 needs to be open on any firewalls.
(*2) Please note that this is also supported through SMB 2 and SMB 3.

Print Friendly, PDF & Email