The IP addresses are not being mapped to the AD users and groups
When integrating the AD client with the Exinda appliance, the IPInternet protocol addresses are not being mapped to the users and groups on the Exinda appliance.
Logon auditing must be enabled for IP address to be mapped to the users.
You can investigate by verifying whether the domain controller is logging particular event IDs. If these events are absent then you will need to enable logon auditing.
In the Domain Controller, go to Event Viewer > Windows Logs > Security Logs.
- For Windows Server 2008, 2008 R2, 2012, and 2012 R2, you should see Event ID #4624
- For Windows Server 2003, 2003 R2, you should see Event ID #528 and 540.
If the Domain Controller is not logging these events, then you need to enable logon auditing on the domain controller and renumerate the AD client on the Exinda appliance.
- In the Domain Controller, go to Start menu > Administrative Tools > Group Policy Management Snap-in.
- In the Group Policy Management tree, go to your domain, expand the Group Policy Objects node, and select Default Domain Controllers Policy.
- Right click on Default Domain Controllers Policy and select Edit from the context menu.
- In the Group Policy Management Editor dialog box, expand the tree and select Computer Configuration > Policies > Windows Settings > Security Settings > Local Policies > Audit Policy.
- In the policy list on the right, click on Audit logon events and ensure that Success is checked.
- On the Exinda appliance, go to Configuration > System > Network > Active Directory.
- Click the Renumerate button.
- Apply the changes by executing the following command using a CMD console in the Domain Controller: gpupdate /force