It may or may not be coincidence that shortly after updating to 10.8 I started getting DDS error messages.
We are using an LDAP connection to windows 2012 R2 AD domain controller (and I have already rolled back windows updates just prior to the errors starting) which has been working reliably for the previous 18 months or so. Obviously I always get one such message when the DC is rebooting after a windows update but I know that is simply because the directory was briefly offline.
The audit logs are showing that lookups sometimes timeout connecting to the directory.
Every time I have manually tested the connection from the control centre, for all types of lookups, I get a result back right away and cannot replicate the timeout.
We currently have 3 users active (including myself) and about 6 aliases so we shouldn't be taxing the connection too much, although I am seeing evidence in the logs of more brute force attempts than I get messages for (presumably clever enough to spread usernames accross enough IP addresses to avoid being flagged for repeats within 15 minutes), so it may just be excessive lookups?
I had a feeling that the timeouts were occurring more on outgoing mail than incoming, but in retrospect thats probably because I only see when outbound messages are delayed as a result.
Is anyone else having a similar problem since upgrading to 10.8 or is that just coincidence?
Do I just need to tune how the DC handles LDAP requests? I am aware that 2012 R2 is nearly EEOL but getting the boss to do anything about it in advance is like banging my head against a wall.
(Not a pro, just the guy in a small business who also does the IT)