Tips for finding Knowledge Articles

  • - Enter just a few key words related to your question or problem
  • - Add Key words to refine your search as necessary
  • - Do not use punctuation
  • - Search is not case sensitive
  • - Avoid non-descriptive filler words like "how", "the", "what", etc.
  • - If you do not find what you are looking for the first time,reduce the number of key words you enter and try searching again.
  • - Minimum supported Internet Explorer version is IE9
Home  >
article

KB-4933: Logs do not show source machine for locked accounts

Centrify Identity Service, Mac Edition ,  

5 May,15 at 06:17 PM

Applies to: Centrify DirectControl for Mac.

Question: 

A user account has been locked from too many failed login attempts from a Mac.  When checking the logs in the Event Viewer on the domain controller, the "Caller Computer Name" field is blank. 

Why doesn't this show the source machine the failed logins originated from?


Answer: 

This function is not supported by Microsoft.  As a result, source machines are not shown in the AD event logs for Mac, Linux and Unix systems that are joined to the domain.

This is a Microsoft limitation and is not exclusively encountered with Centrify - it is also the case for Mac systems joined to the domain with the native AD plugin from Apple.

The image below shows event 4740 for a user account that has been locked on a Windows 2008 Server; the "Caller Computer Name" is empty. This is expected behavior.

Event 4740 showing locked account with no Caller Computer Name.

Still have questions? Click here to log a technical support case, or collaborate with your peers in Centrify's Online Community.