Is port 389 on AD in anyway used or required when a new client queries . . . When NLA starts to detect the network location, the machine will contact a domain controller via port 389 If this detection is successful, it will get the domain firewall profile (allowing for correct ports) and we cannot change the network location profile
What is Port 389? - CBT Nuggets Port 389 is for making LDAP connections so users can access protected network resources These connections grant LDAP clients the ability to make use of directory services on LDAP servers Unlike when using LDAP over port 636, connections made over port 389 are unencrypted
What is Port 389 LDAP: A Complete Guide for Beginners Port 389 is designated as the standard port for the Lightweight Directory Access Protocol (LDAP) and is one of the most commonly used ports in corporate networks and on the Internet
LDAP Ports: 389, 636, and Everything In Between - ManageEngine There are two main LDAP port numbers in use: port 389 and port 636 Port 389 is the default LDAP port The traffic on port 389 is unencrypted by default, though you can upgrade it to an encrypted one with STARTTLS Port 636, on the other hand, is for LDAPS, which is LDAP over SSL
List of TCP and UDP port numbers - Wikipedia 2Well-known ports 3Registered ports 4Dynamic, private or ephemeral ports 5Note 6See also 7References and notes 8Further reading 9External links Toggle the table of contents
389 Directory Server - Wikipedia The 389 Directory Server (previously Fedora Directory Server) is a Lightweight Directory Access Protocol (LDAP) server developed by Red Hat as part of the community-supported Fedora Project The name "389" derives from the port number used by LDAP