| David Wang [Msft] 2004-10-29, 2:48 am |
| The article mentions that CrashOnAuditFail gets set to 2 only if the
Security log is full AND it was originally set to 1 AND a system reboot had
taken place after it was set to 1. It also mentions that the default value
is 0.
The KB article also mentions that setting Event Log to "overwrite as needed"
as well as setting CrashOnAuditFail to non-zero are essentially
self-defeating.
The only problem I see here is if:
1. CrashOnAuditFail is zero and you observe the "unable to authenticate"
situation
2. CrashOnAuditFail is non-zero and you've set Event Log to "overwrite as
needed" and you observe the "unable to authenticate" situation
Did you observe either of the two scenarios? If so, then feel free to file
a bug.
--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"pbirkle" <pbirkle@discussions.microsoft.com> wrote in message
news:B88D7415-BEF1-4C22-AECF-A3A90FB53174@microsoft.com...
No-one answered my post.
I know I resolved it myself but I would like some feeback
-----------------------------------------------------------
The security log was full. See http://support.microsoft.com/?id=832981 (This
prevent any users being Authenticated via AD Domain using Basic
Authentication. CrashOnAuditFail Registry Key gets set to 2 if Security log
is full based on the above KB article. Well my security log was full but it
was set to overwrite Events as needed not after X days or Manual.
But the weird thing is I had the Security Event log to Overwrite events as
needed not after x days or manual.
Does this been this is a Bug in Windows 2003
========================================
=====
Its has never happened in Windows 2000 Server running IIS 5.0
Should I log a bug with Microsoft about this
Peter Birkle
|