Why would LDAP traffic go to a different endpoint than Kerberos in AD?
retained text
Hi everyone,
I'm analyzing some Active Directory telemetry in CrowdStrike Identity Protection and I'm trying to understand something that initially looked unusual.
I'm seeing activity where a Windows workstation communicates with one endpoint using **Kerberos**, but then performs **LDAP searches against a different endpoint**.
For example, the pattern looks roughly like:
Workstation
│
├── Kerberos ──> Domain Controller A
│
└── LDAP ──────> Endpoint B
Endpoint B is **not a Domain Controller**.
My understanding is that Kerberos is used for authentication/tickets, while LDAP is used for directory queries, and Kerberos can potentially authenticate a client to an LDAP service running on another server.
However, I'm trying to understand how common/legitimate this scenario is in a Windows AD environment.
**Questions:**
1. Is it normal for the Kerberos KDC endpoint and LDAP endpoint to be different machines?
2. If the LDAP destination is not a DC, what are the common legitimate reasons for this?
3. Could this simply be an application/server running an LDAP service or LDAP proxy?
4. How would you determine which process/application on the client initiated the LDAP connection?
5. For those using CrowdStrike Identity Protection, how reliable have you found the LDAP endpoint attribution in these events?
I'm particularly interested in real-world examples of why a domain-joined Windows workstation would perform LDAP queries against a non-DC endpoint.
Thanks!document fetched 2026-09-15 00:38 · canonical https://reddit.com/r/sysadmin/comments/1wg1s55/why_would_ldap_traffic_go_to_a_different_endpoint