search for: cc771022

...in a domain using LDAPS. It's also very likely that the issue is related to my Domain Controllers, I've only verified that they are accepting connections on port 636 using the LDP.exe tool. see https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/cc771022(v=ws.11) ~Cordell

> Samba 4.13 recently removed this support. > The issue is that while it was possible to use LDAPS in some situations, it was not possible to reliably determine the hostname to verify the TLS certificate, rendering the protection moot. > Furthermore, extensive work would have been required to fully implement the 'channel bindings' required to tie the Kerberos authentication Samba

So is that a bind type not mentioned in the chart he referenced for ldp.exe? <https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/cc771022(v=ws.11)#understanding-bind-options-for-ldap-authentication>Understanding bind options for LDAP authentication There are several authentication methods available in ldp that allow a client to bind to an LDAP server. The best method depends on several factors. Method Description Simple Clear...