You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Ports used by Indeed CM server

DNS

  • 53 (TCP/UDP), outgoing connections

Web applications, HTTP, HTTPS

  • 80 (TCP), incoming and outgoing connections
  • 443 (TCP), incoming and outgoing connections
  • 3003 (TCP), incoming and outgoing connections for Indeed CM Agent

Mail notifications, SMTP server

  • 25 (TCP), outgoing connections
  • 465 (TCP), outgoing connections
  • 587 (TCP), outgoing connections

Active Directory, incoming and outgoing connections

  • 135 (TCP) – NetBIOS
  • 389 (TCP/UDP) – LDAP
  • 636 (TCP) – LDAPS
  • 3268 (TCP/UDP) – Microsoft Global Catalog 
  • 88 (TCP/UDP) – Kerberos
  • 464 (TCP/UDP) – Kerberos

SQL Server, incoming and outgoing connections

  • 135 (TCP) – Transact-SQL debugger
  • 1433 (TCP) – SQL Server default instance
  • 1434 (UDP) – SQL Server Browser service
  • 4022 (TCP) – Service Broker 

Microsoft CA, incoming and outgoing connections

  • 135 (TCP) – NetBIOS
  • 389 (TCP) – LDAP 
  • 636 (TCP) – LDAPS
  • The port used for certificate requesting is DCOM/RPC7

Microsoft CA is implemented using DCOM technology. The DCOM applications use random TCP port numbers from upper range by default. It is also possible to set the CA to use an explicitly defined TCP port.

Ports used by Indeed CM operator and user workstations

DNS

  • 53 (TCP/UDP), outgoing connections

Web applications, HTTP, HTTPS

  • 80 (TCP), incoming and outgoing connections 
  • 443 (TCP), incoming and outgoing connections
  • 3003 (TCP), incoming and outgoing connections for Indeed CM Agent


  • No labels