active directory - Can not promote server to domain controller because required ports are already in use - Server Fault
Active Directory Ports Used Client to Server - Active Directory Pro
domain controller firewall ports – Dimitri's Wanderings
Terminalworks Blog | Restricting Active Directory communication ports
Firewall ports to join a domain (RPC)
Ports used for connections - Configuration Manager | Microsoft Learn
Configure firewalls for Managed Microsoft AD | Managed Microsoft AD Documentation | Google Cloud
Configuring Domain Trusts Across a Firewall | Alexander's Blog
Firewall Ports Required to Join AD Domain - AventisTech
Securely extend and access on-premises Active Directory domain controllers in AWS | AWS Security Blog
Active Directory Ports Used Client to Server - Active Directory Pro
Domain controllers required ports: Use PowerShell to check if they are listening
Deploying Mobility in a DMZ
Configure firewalls for Managed Microsoft AD | Managed Microsoft AD Documentation | Google Cloud
Domain Controller Ports – The World According to Mitch
Firewall Ports Required to Join AD Domain - AventisTech
Upcoming change - Microsoft to disable use of unsigned LDAP port 389 - msandbu.org
Terminalworks Blog | Restricting Active Directory communication ports
How to Troubleshoot Active Directory Across Firewalls – TCP Techs
Ports Used by GPA - Group Policy Administrator User Guide
Ports Used by Configuration Manager
The TCP ports required by Active Directory Domain Services are already in use on this computer.
