Mentioned
In
|
 |
 |
 |
|
Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms
of Use |
Trademarks
Article ID: 942228 - Last Review: November 9, 2007 - Revision: 1.1 FIX: An authentication failure occurs when a .NET Framework 1.1 client application tries to access some resources from IIS 7.0 on a Windows Vista-based computerOn This PageSYMPTOMSWhen a Microsoft .NET Framework 1.1 client application tries to access some resources from Internet Information Services (IIS) 7.0 on a Windows Vista-based computer, an authentication failure occurs. This problem occurs if one of the following conditions is true: - IIS is configured to have more than one authentication scheme for the client-requested resources. And, one of the authentication schemes is Integrated Windows authentication.
- IIS is configured for Integrated Windows authentication only. However, the value of the NTAuthenticationProviders metabase property for the client-requested resources is set to Negotiate,NTLM.
When the authentication failure occurs, you may receive an exception that resembles the following: The remote server returned an error: (401) Unauthorized.
at System.Net.HttpWebRequest.CheckFinalStatus()
at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
at System.Net.HttpWebRequest.GetResponse()
at simpleclient.Form1.Button2_Click(Object sender, EventArgs e) in E:\Attempts\simpleclient\Form1.vb:line 123
This problem does not occur if the .NET Framework 1.1 client application tries to access some resources from IIS on a Windows Server 2008-based computer. CAUSEThis problem occurs because of a problem in the .NET Framework. When a client application tries to access some resources from IIS, IIS sends back "WWW-Authenticate" headers to the client application. The headers indicate what authentication schemes are configured for the client-requested resources. When the client application selects Integrated Windows authentication as the authentication scheme, the application sends back a token. Then, IIS sends back a challenge to the token. If other authentication schemes are also defined for the client-requested resources, IIS may send other "WWW-Authenticate" headers together with the challenge in the response. In this case, the .NET Framework client application incorrectly parses the challenge, and the authentication failure occurs. Note Earlier versions of IIS do not send back other possible authentication schemes for the client application. Therefore, this problem does not occur. RESOLUTIONHotfix informationA supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next .NET Framework 1.1 service pack that contains this hotfix. To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site: Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question. PrerequisitesYou must have the .NET Framework 1.1 Service Pack 1 installed to apply this hotfix. Restart requirementYou do not have to restart the computer after you apply this hotfix. Hotfix replacement informationThis hotfix does not replace any other hotfixes. File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel. Collapse this tableExpand this table | File name | File version | File size | Date | Time | Platform | SP requirement | Service branch |
|---|
| Aspnet_isapi.dll | 1.1.4322.2425 | 258,048 | 05-Oct-2007 | 08:58 | x86 | SP2 | SP2QFE | | Aspnet_wp.exe | 1.1.4322.2425 | 32,768 | 05-Oct-2007 | 08:58 | x86 | SP2 | SP2QFE | | Corperfmonext.dll | 1.1.4322.2425 | 81,920 | 05-Oct-2007 | 08:59 | x86 | SP2 | SP2QFE | | Mscoree.dll | 2.0.50727.253 | 271,360 | 05-Oct-2007 | 08:59 | x86 | SP2 | SP2QFE | | Mscorees.dll | 2.0.50727.253 | 6,144 | 18-Jan-2007 | 13:40 | x86 | SP2 | SP2QFE | | Mscorie.dll | 1.1.4322.2425 | 86,016 | 05-Oct-2007 | 08:59 | x86 | SP2 | SP2QFE | | Mscorjit.dll | 1.1.4322.2425 | 315,392 | 05-Oct-2007 | 08:59 | x86 | SP2 | SP2QFE | | Mscorld.dll | 1.1.4322.2425 | 102,400 | 05-Oct-2007 | 08:59 | x86 | SP2 | SP2QFE | | Mscorlib.dll | 1.1.4322.2425 | 2,142,208 | 05-Oct-2007 | 04:44 | x86 | SP2 | SP2QFE | | Mscorlib.ldo | Not applicable | 10,952 | 05-Oct-2007 | 15:22 | Not applicable | SP2 | SP2QFE | | Mscorsn.dll | 1.1.4322.2425 | 77,824 | 05-Oct-2007 | 09:00 | x86 | SP2 | SP2QFE | | Mscorsvr.dll | 1.1.4322.2425 | 2,523,136 | 05-Oct-2007 | 09:00 | x86 | SP2 | SP2QFE | | Mscorwks.dll | 1.1.4322.2425 | 2,514,944 | 05-Oct-2007 | 09:00 | x86 | SP2 | SP2QFE | | Netfxupdate.exe | 1.0.3705.3 | 73,728 | 20-Aug-2007 | 11:06 | x86 | SP2 | SP2QFE | | Setregni.exe | 1.1.4322.2034 | 106,496 | 20-Aug-2007 | 11:06 | x86 | SP2 | SP2QFE | | Sy52106.dll | 1.1.4322.2425 | 1,232,896 | 18-Sep-2007 | 04:52 | x86 | SP2 | SP2QFE | | System.ldo | Not applicable | 11,540 | 05-Oct-2007 | 15:22 | Not applicable | SP2 | SP2QFE | | System.web.dll | 1.1.4322.2425 | 1,265,664 | 05-Oct-2007 | 04:46 | x86 | SP2 | SP2QFE | | Togac.exe | 1.1.4322.573 | 118,784 | 20-Aug-2007 | 11:07 | x86 | SP2 | SP2QFE |
WORKAROUNDTo work around this problem, use one of the following methods: - Do not use the Integrated Windows authentication scheme on IIS.
- If the Integrated Windows authentication scheme is used, set the NTAuthenticationProviders metabase property to one of the following values:Notes
- If you set the value of the NTAuthenticationProviders metabase property to Negotiate, the client application can select either NTLM authentication or Kerberos authentication.
For more information about how to configure IIS to support both the Kerberos protocol and the NTLM protocol for network authentication, click the following article number to view the article in the Microsoft Knowledge Base:
215383Â
(http://kbalertz.com/Feedback.aspx?kbNumber=215383/
)
How to configure IIS to support both the Kerberos protocol and the NTLM protocol for network authentication
- Even though you have made this change, if any additional authentication scheme is set for the client-requested resources, an authentication failure will occur.
- If the client application selects Integrated Windows authentication as the authentication scheme, suppress other "WWW-Authenticate" headers. To do this, create a server side plug-in, such as a native module or an ISAPI filter.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATION
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684Â
(http://kbalertz.com/Feedback.aspx?kbNumber=824684/
)
Description of the standard terminology that is used to describe Microsoft software updates
APPLIES TO- Microsoft .NET Framework 1.1
| kbfix kbpubtypekc kbqfe kbhotfixserver kbexpertiseadvanced KB942228 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate
Be the first to leave feedback, to help others about this knowledge base
article.
(Optional) Name
(Optional)
Public URL Or Email
Comments
No
HTML -- Text Only Please
|
|
 |
|
 |
|
|
|
| |