https://bugs.winehq.org/show_bug.cgi?id=50545
--- Comment #22 from Damjan Jovanovic damjan.jov@gmail.com --- I discovered some LDAP bugs on my side, which may or may not relate to this.
The 1st problem, bug 50572, is that ldap_bind_sW() supplies the authorization name instead of the authentication name. This will break 100% of all WLDAP32_LDAP_AUTH_NEGOTIATE logins, as my examples there show. A patch, linked there, was just submitted.
The 2nd problem for me is that the username format is "domain\username", which always fails - my AD server wants "username" by itself. I am not yet sure where that's coming from but it should be an easy fix; when hacked by hardcoding the username in the above patch, it gets further.
The 3rd problem is that ldapns_QueryInterface() then fails for a number of interfaces, but it's COM- and .NET- internal interfaces like IMarshal, so this may not be a problem?
The 4th problem is that adsldp's search_SetSearchPreference() has missing options which probably break my application, as it doesn't get any further.