Welcome to HostingForumz.com!
FAQFAQ   SearchSearch      ProfileProfile    Private MessagesPrivate Messages   Log in/Register/PasswordLog in/Register/Password

401.1 Unable to Authenticate Users in IIS in IIS 6 under 2..

  
   Web Hosting Problem Solving Community! (Home) -> IIS RSS
Next:  IIS: Windows 2000 server: clients limited to 30 Kb/s per thread  
Author Message
pbirkle

External


Since: Oct 27, 2004
Posts: 6



(Msg. 1) Posted: Thu Oct 28, 2004 10:41 pm
Post subject: 401.1 Unable to Authenticate Users in IIS in IIS 6 under 2003 Serv
Archived from groups: microsoft>public>inetserver>iis (more info?)
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

 >> Stay informed about: 401.1 Unable to Authenticate Users in IIS in IIS 6 under 2.. 
Back to top
Login to vote
someone9

External


Since: Aug 25, 2003
Posts: 2419



(Msg. 2) Posted: Fri Oct 29, 2004 2:37 am
Post subject: Re: 401.1 Unable to Authenticate Users in IIS in IIS 6 under 2003 Serv [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
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.TakeThisOut@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

 >> Stay informed about: 401.1 Unable to Authenticate Users in IIS in IIS 6 under 2.. 
Back to top
Login to vote
pbirkle

External


Since: Oct 27, 2004
Posts: 6



(Msg. 3) Posted: Mon Nov 01, 2004 12:07 am
Post subject: Re: 401.1 Unable to Authenticate Users in IIS in IIS 6 under 2003 [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
I have observed you point 2.

2. CrashOnAuditFail is non-zero and you've set Event Log to "overwrite as
 > needed" and you observe the "unable to authenticate" situation

Yes !!!

How do I file a bug report with Microsoft??

Peter Birkle


"David Wang [Msft]" wrote:

 > 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.TakeThisOut@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 <a style='text-decoration: underline;' href="http://support.microsoft.com/?id=832981" target="_blank">http://support.microsoft.com/?id=832981</a> (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
 >
 >
 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: 401.1 Unable to Authenticate Users in IIS in IIS 6 under 2.. 
Back to top
Login to vote
someone9

External


Since: Aug 25, 2003
Posts: 2419



(Msg. 4) Posted: Mon Nov 01, 2004 1:07 pm
Post subject: Re: 401.1 Unable to Authenticate Users in IIS in IIS 6 under 2003 [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
Hmm... that's not what you described earlier. Can you confirm that you did
set CrashOnAuditFail to be non-zero and Event Log to "overwrite", rebooted,
and when the security log got full, observed the situation.

You haven't said that you ever changed CrashOnAuditFail.

--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"pbirkle" <pbirkle.RemoveThis@discussions.microsoft.com> wrote in message
news:5B0D7464-EE4F-4BFA-A608-05CDA463B737@microsoft.com...
I have observed you point 2.

2. CrashOnAuditFail is non-zero and you've set Event Log to "overwrite as
 > needed" and you observe the "unable to authenticate" situation

Yes !!!

How do I file a bug report with Microsoft??

Peter Birkle


"David Wang [Msft]" wrote:

 > 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.RemoveThis@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
 >
 > -----------------------------------------------------------
<font color=purple> > The security log was full. See <a style='text-decoration: underline;' href="http://support.microsoft.com/?id=832981</font" target="_blank">http://support.microsoft.com/?id=832981</font</a>>
(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
 >
 >
 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: 401.1 Unable to Authenticate Users in IIS in IIS 6 under 2.. 
Back to top
Login to vote
pbirkle

External


Since: Oct 27, 2004
Posts: 6



(Msg. 5) Posted: Thu Nov 04, 2004 7:12 pm
Post subject: Re: 401.1 Unable to Authenticate Users in IIS in IIS 6 under 2003 [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
Never touched the CrashOnAudit Fail Registry Settings.
It would have been at the default

Peter Birkle

"David Wang [Msft]" wrote:

 > Hmm... that's not what you described earlier. Can you confirm that you did
 > set CrashOnAuditFail to be non-zero and Event Log to "overwrite", rebooted,
 > and when the security log got full, observed the situation.
 >
 > You haven't said that you ever changed CrashOnAuditFail.
 >
 > --
 > //David
 > IIS
 > This posting is provided "AS IS" with no warranties, and confers no rights.
 > //
 > "pbirkle" <pbirkle DeleteThis @discussions.microsoft.com> wrote in message
 > news:5B0D7464-EE4F-4BFA-A608-05CDA463B737@microsoft.com...
 > I have observed you point 2.
 >
 > 2. CrashOnAuditFail is non-zero and you've set Event Log to "overwrite as
  > > needed" and you observe the "unable to authenticate" situation
 >
 > Yes !!!
 >
 > How do I file a bug report with Microsoft??
 >
 > Peter Birkle
 >
 >
 > "David Wang [Msft]" wrote:
 >
  > > 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 DeleteThis @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
  > >
  > > -----------------------------------------------------------
<font color=green>  > > The security log was full. See <a style='text-decoration: underline;' href="http://support.microsoft.com/?id=832981</font" target="_blank">http://support.microsoft.com/?id=832981</font</a>>
 > (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
  > >
  > >
  > >
 >
 >
 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: 401.1 Unable to Authenticate Users in IIS in IIS 6 under 2.. 
Back to top
Login to vote
pbirkle

External


Since: Oct 27, 2004
Posts: 6



(Msg. 6) Posted: Thu Nov 04, 2004 7:23 pm
Post subject: Re: 401.1 Unable to Authenticate Users in IIS in IIS 6 under 2003 [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
OKay.

First thing that I noticed was that users were not being Authenticated to
the IIS 6.0 box using Basic Authentication in IIS 6.0

We thought that IIS 6.0 had some issue.

After read through the KB Article 832981 I discovered that if the Security
Log gets FULL on IIS 5 or 6 then the Crash On Audit Flag gets set to 2

Looking at the
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\CrashOnAuditFail
for the first time it was set to a value of 2 (So only Administrators could
logon)

So I don't know if the original value was 0 or not it must have been 1

As indicated in the KB article. Values of

• 0 - Anyone may log on. This is the default value.
• 1 - Anyone may log on if the system can audit the events and write the
events to the security event log. If the security event log is full, the
value for the CrashOnAuditFail key is changed to 2, and the server crashes.
• 2 - Only administrators may log on.

I did a default install of another IIS 6.0 system and the default for the
CrahOnAuditFail was infact set 0.

Peter Birkle

"David Wang [Msft]" wrote:

 > Hmm... that's not what you described earlier. Can you confirm that you did
 > set CrashOnAuditFail to be non-zero and Event Log to "overwrite", rebooted,
 > and when the security log got full, observed the situation.
 >
 > You haven't said that you ever changed CrashOnAuditFail.
 >
 > --
 > //David
 > IIS
 > This posting is provided "AS IS" with no warranties, and confers no rights.
 > //
 > "pbirkle" <pbirkle.DeleteThis@discussions.microsoft.com> wrote in message
 > news:5B0D7464-EE4F-4BFA-A608-05CDA463B737@microsoft.com...
 > I have observed you point 2.
 >
 > 2. CrashOnAuditFail is non-zero and you've set Event Log to "overwrite as
  > > needed" and you observe the "unable to authenticate" situation
 >
 > Yes !!!
 >
 > How do I file a bug report with Microsoft??
 >
 > Peter Birkle
 >
 >
 > "David Wang [Msft]" wrote:
 >
  > > 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.DeleteThis@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
  > >
  > > -----------------------------------------------------------
<font color=green>  > > The security log was full. See <a style='text-decoration: underline;' href="http://support.microsoft.com/?id=832981</font" target="_blank">http://support.microsoft.com/?id=832981</font</a>>
 > (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
  > >
  > >
  > >
 >
 >
 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: 401.1 Unable to Authenticate Users in IIS in IIS 6 under 2.. 
Back to top
Login to vote
Display posts from previous:   
   Web Hosting Problem Solving Community! (Home) -> IIS All times are: Pacific Time (US & Canada) (change)
Page 1 of 1

 
 You can post new topics in this forum
You can reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum



[ Contact us | Terms of Service/Privacy Policy ]