Communication ports and URLs used by Active Roles
This section and its subsections list the communication ports used by Active Roles and its various components. To ensure that Active Roles works properly, open these ports in your organization firewall.
NOTE: For the list of ports used by Active Roles and Capture Agent, see Communication ports used by in the Active Roles Administration Guide.
If the environment managed by Active Roles is located behind a firewall, open the following ports between the Active Roles Administration Service instance and your managed environment.
For more information on opening ports, see the instructions of the Windows Defender Firewall with Advanced Security console of your operating system, or the documentation of your network device.
Port to access DNS
Open the following port on the machine running Active Roles Administration Service:
Ports to access domain controllers (DCs)
Open the following outbound ports on the machine running Active Roles Administration Service:
-
Port 88 (Kerberos) TCP/UDP.
-
Port 135 (RPC endpoint mapper) TCP.
-
Port 139 (SMB/CIFS) TCP.
-
Port 389 (LDAP) TCP.
-
Port 445 (SMB/CIFS) TCP.
-
Port 636 (LDAP SSL) TCP.
-
Port 3268 (Global Catalog LDAP) TCP.
If Active Roles must access the domain via SSL, open the following ports on the machine running Active Roles Administration Service:
-
Port 3269 (Global Catalog LDAP SSL) TCP, Outbound.
-
The TCP port allocated by RPC endpoint mapper for communication with the DC.
URLs required to access Microsoft Azure and Microsoft 365
To ensure that Active Roles can access the various cloud Microsoft services (for example, Microsoft 365 and Azure AD), make sure that the machine hosting Active Roles Administration Service can resolve and access the following URLs:
Ports required by the Starling Connect Notifications Pane
To make sure that the Starling Connect Notifications Pane of the Active Roles Web Interface can display Starling notifications, open the following inbound ports from the client browser inbound to the machine running Active Roles Administration Service:
-
Port 7465 (HTTP) TCP.
-
Port 7466 (HTTPS) TCP.
NOTE: Starling notifications will work only if the machine running Active Roles Web Interface can resolve the Service machine name.
Ports to access Exchange servers
To communicate with your on-premises Exchange Server instance, open the following ports on the machine running Active Roles Administration Service:
-
Port 135 (RPC endpoint mapper) TCP, Outbound.
-
The TCP port allocated by RPC endpoint mapper for communication with Exchange Server.
TIP: You can configure Exchange Servers to use specific ports for RPC communication. For more information, contact Microsoft Support.
To ensure that Exchange Server operations related to the WinRM service can work, also open the following inbound and outbound ports:
-
Port 5985 (HTTP) TCP.
-
Port 5986 (HTTPS) TCP.
-
Port 80 TCP.
Ports to access SQL Server
To communicate with your SQL Server instance, open the following outbound ports on the machine hosting the Active Roles Administration Service:
-
Port 1433 (default SQL instance), TCP.
-
Port 1434 (SQL Server Browser instance), UDP.
Ports required to restart computers remotely with Active Roles
To restart computers remotely in your organization with Active Roles, open the following outbound ports on the machine hosting the Active Roles Administration Service:
Ports required by Computer resource management and Home folder provisioning/deprovisioning policies
To ensure that the Computer resource management and Home folder provisioning/deprovisioning policies work correctly in your organization, open the following outbound ports on the machine hosting the Active Roles Administration Service:
Ports to access SMTP servers for email integration
Open the following outbound port on the machine hosting the Active Roles Administration Service:
Port to access AD LDS instances
Open the following port on the machine hosting the Active Roles Administration Service:
If you set up a firewall between the various Active Roles client components (for example, the Active Roles Console, Web Interface, ADSI Provider, or Management Shell) and the Active Roles Administration Service, then to access the Active Roles Administration Service, open the following ports on the machines running the Active Roles client components.
For more information on opening ports, see the instructions of the Windows Defender Firewall with Advanced Security console of your operating system, or the documentation of your network device.
To access the Active Roles Web Interface through a firewall, open the following inbound ports on the machine running the Web Interface instance:
For more information on opening ports, see the instructions of the Windows Defender Firewall with Advanced Security console of your operating system, or the documentation of your network device.
NOTE: By default, SSL encryption is disabled for the Web Interface. To enable it:
-
Set up SSL in the machine running the Active Roles Web Interface as described in the following resources:
-
Configure SSL redirection in the Active Roles Configuration Center as described in Configure Web Interface for secure communication in the Active Roles Administration Guide.
After SSL is enabled, Active Roles Web Interface also runs over ports 80 and 443 by default.