If the domain is not reachable, the auth debug log should have more information about why (assuming you are logging management events), if it doesn't that makes me sad. The auth debug log should say when it connects or disconnects from a domain controller, as well as a domain as a whole.
I posted about the failure IDs in this thread (why didnt you find it?! ---jk): Re: Web Hybrid Lists
Each failure ID has a failure reason string (human readable), the property is Authentication.FailureReason.Message.
0 No Failure - Authentication was fine
1 Unexpected Credentials - Authentication was out of expected order (applies to NTLM)
2 Unknown User - User doesnt exist in directory.
3 Wrong Password - Bad password (can apply in other situations, see https://community.mcafee.com/message/268185#268185)
4 No Credentials - No credentials were sent (ignore if authentication hasnt failed -- NTLM)
5 No Server Available - Directory server MWG attempted to contact was not reachable.
6 Proxy Timeout - MWG was communicating with a resource and it took too long to get an answer.
7 Server Timeout - ?
8 Communication Error - Server that MWG was communicating with shut down the connection.
10000 Internal Error -catch all
Using the failureIDs is not without their pitfalls though:
Do you have a use case for the failure IDs? Most of the time the you should only look at the failure ID if authentication actually failed (Authentication.Failed equals true).
thanks for the reply. No, there is no Domain Controller information in the Auth Debug LOG. At the moment we do not know what causes the entry in the dashboard.
We opened a service request and submitted a feedback file. Let´s see if we get additional information from that. :-)