Windows IT Pro is the leading independent community for IT professionals deploying Microsoft Windows server and client applications and technologies.
  
  
  Advanced Search 


Return to article

Tracking Kerberos Authentication Events to Workstations
 

I'm trying to track down security violations that are originating within our network. I can tell that someone is using compromised accounts, but I can't connect those accounts to particular workstations or users. I've read that when a Windows 2000 domain controller (DC) logs authentication events, the DC can't record the workstation name if the Kerberos authentication protocol was used. All our computers are Win2K or later, so all our authentication takes place through Kerberos. How can I determine the name of the workstation being used to violate security?

When you enable the Audit account logon events audit category on Win2K DCs, Kerberos events don't include the workstation name. However, they do include the client IP address, as Figure 1 shows. You need to track down the IP address in your DHCP server logs to find the MAC address, then use it to find the computer. For details on how to use DHCP server logs, see Ask the Experts, "Differentiating Event ID 530 Logon Failures," September 2003, InstantDoc ID 39773.







Reader Comments

n/a

theDeuce -August 06, 2004
Windows IT Pro Home Register FAQ for Windows WinInfo News
Europe Edition About Us Contact Us/Customer Service Media Kit Affiliates / Licensing  
SQL Server Magazine Office & SharePoint Pro DevProConnections IT Job Hound
Left-Brain.com Technology Resource Directory asp.netPRO ITTV Windows SuperSite 
 
 Windows IT Pro is a Division of Penton Media Inc.
 © 2009 Penton Media, Inc. Terms of Use | Privacy Statement