Quote:
Originally Posted by Rathji
Why don't you use the arp table to find out the IP address associated with the MAC address?
At command line, in windows arp -a and I think Linux/Mac would be a simple arp with no arguments passed. Ran on on CLI on the machine that is locking them out (although other machines may work).
|
This is a good suggestion, assuming though that you are on the same subnet as the devices, and also assuming you've pinged the broadcast address for the subnet first.
Since he's talking about accounts getting locked out, and possibly Apple mobile devices, I'm guessing we're dealing with Exchange here, in which case he could also check the IIS logs on the Exchange box to find the IP's of the machines making bad requests that are denied due to authentication (a 403, I guess?). iPhones and iPads would be talking to the Activesync virtual directory, and Outlook 2011 clients and/or the Mac Mail/Calendar/iCal clients would be accessing the EWS virtual directory. Outlook 2008 and lower clients on Mac access Exchange via the OWA virtual directory, since they are essentially emulating OWA access on behalf of the user.
You could also look in your DHCP reservation tables to find the DHCP lease that the Apple device has - this will definitely contain the IP to MAC association, and running something like "netsh -c dhcp server scope xxx.xxx.xxx.xxx show clients" on your DHCP server should do the trick I think.
It would not surprise me at all that you will discover it's iPhones and/or iPad's that are causing the lockouts - it seems to me that the devices will make multiple attempts with an incorrect password before informing the user that the password is wrong. It's also tricky from an end-user perspective since the devices will continue to function for some time after a password change, at least for the duration of the Activesync HTTP keepalive (20 minutes, I believe, by default), or however long the Information Store on Exchange keeps cached credential info (which is also 20 minutes by default I think), so users often forget to update their devices after a password change, since they are still working for some time afterwards.