Appreciate the feedback, seriously…but yeah, I’ve already gone over all of that kind of stuff. Here’s the basic scenario again (lifted from my Experts-Exchange post…no one there can figure this out either):
Background:
I’m conducting object access auditing on several shared folders on one of our file servers. The file server is a Windows Server 2000 box with Service Pack 4.
I configured the local machine policy to audit “Success, Failure” for the Audit Object Access policy. I then configured auditing at the folder level for three shared folders. These folders are member folders in our DFS. At the folder level, I configured auditing for the “Domain Users” group, and specified “List Folder/Read Data” to be audited for Failed access attempts only. (I know that the best practice is to audit the “Everyone” group, but this was causing false hits due to System access failures due to to indexing, persistent connections, ect- we only need to audit the domain users group for our purposes anyway).
The problem:
At random intervals, a failed object access attempt will spawn a totally random number of events written to the security log, instead of one. I tested this extensively with a test domain user account without permissions to the folders- while attempting to access the SAME folder in the SAME manner, sometimes the failed access attempt would write one entry to the security log, sometimes it would write a random number. One failed attempt created 107 entries in the security log. Several times 50+ events were written (all for one failed object access attempt). All events are the correct Event ID 560.
I cannot find any logic to this. I have a case opened with Microsoft, but haven’t gotten any results from them.
i would try to narrow down the users to OS levels and AD OU’s… to try to see if anything similar is being effected… if some dude is sitting on an old box he might be using ipc$ to connect or something dumb in the backround that is causing more events than the others? (example of a random situation)
A perfectly logical answer…but not the case here. My test user accounts, from my workstation, from other workstations, and from a test server, all behave the same way- sometimes they generate one Event 560 (as they should), other times they generate 40, 50, or more.
i dunno… just a thought… you can use VB to cut through the BS events to narrow down on the ones you are intersted in… are you using MOM for reporting, it does the same but has a decent gui?
We’re using Open View for reporting and alerts.
Thanks again. I’ll update this post whenever MS gives me a solution. At this point they still haven’t come up with anything.