Reference of common ports, protocols and troubleshooting context; a known port never means it should be exposed to the Internet.
Core infrastructure
Monitoring & directory
Prefer SNMPv3 where possible.
Active Directory also requires RPC/Kerberos/DNS.
LDAP over TLS; check certificate and trust chain.
Used by Active Directory global catalog.
Web & administration
Often redirected to HTTPS but may still be required for some services.
Major application port; inspect TLS/SNI/Host beyond TCP.
Remote PowerShell management on Windows.
WinRM over TLS; requires correct certificate/configuration.
Server-to-server mail transport.
Depending on provider/service.
Common authenticated client/application submission port.
Mailbox access, separate from SMTP sending.
Windows & Active Directory
AD authentication; also depends strongly on DNS and NTP.
RPC then uses dynamic ports depending on OS/configuration.
Highly sensitive to Internet exposure.
Modern default dynamic RPC range, configurable.
Databases
Default classic SQL Server port; named instances may differ.
Do not expose publicly without strong justification and controls.
Filter DB access by source and authentication.
Unprotected exposure is especially risky.
VPN, VoIP & virtualization
IKE negotiation.
Used when NAT is detected.
Does not cover RTP media, whose range depends on the platform.
Exact requirements depend on components and flow direction.
Test without unnecessary exposure
Test-NetConnection serveur -Port 443Tests TCP from the client point of view.
nc -vz serveur 443Tests TCP if netcat is installed.
Get-NetTCPConnection -State ListenConfirms a local service is listening.
ss -lntupMaps ports and processes when permissions allow.
Key points
- A standard port does not prove which service is actually behind it.
- Do not globally disable firewalls to test a port; use targeted temporary tests.
- For Active Directory, think in required flow sets rather than only 389/636.
- For SIP/RTP, VPN and vendor products, use the port matrix for the deployed version.