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 computer

Article translations Article translations
Article ID: 942228 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

When 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
Note 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.

CAUSE

This 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.

RESOLUTION

Hotfix information

A 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:
http://support.microsoft.com/contactus/?ws=support
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.

Prerequisites

You must have the .NET Framework 1.1 Service Pack 1 installed to apply this hotfix.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This 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 nameFile versionFile sizeDateTimePlatformSP requirementService branch
Aspnet_isapi.dll1.1.4322.2425258,04805-Oct-200708:58x86SP2SP2QFE
Aspnet_wp.exe1.1.4322.242532,76805-Oct-200708:58x86SP2SP2QFE
Corperfmonext.dll1.1.4322.242581,92005-Oct-200708:59x86SP2SP2QFE
Mscoree.dll2.0.50727.253271,36005-Oct-200708:59x86SP2SP2QFE
Mscorees.dll2.0.50727.2536,14418-Jan-200713:40x86SP2SP2QFE
Mscorie.dll1.1.4322.242586,01605-Oct-200708:59x86SP2SP2QFE
Mscorjit.dll1.1.4322.2425315,39205-Oct-200708:59x86SP2SP2QFE
Mscorld.dll1.1.4322.2425102,40005-Oct-200708:59x86SP2SP2QFE
Mscorlib.dll1.1.4322.24252,142,20805-Oct-200704:44x86SP2SP2QFE
Mscorlib.ldoNot applicable10,95205-Oct-200715:22Not applicableSP2SP2QFE
Mscorsn.dll1.1.4322.242577,82405-Oct-200709:00x86SP2SP2QFE
Mscorsvr.dll1.1.4322.24252,523,13605-Oct-200709:00x86SP2SP2QFE
Mscorwks.dll1.1.4322.24252,514,94405-Oct-200709:00x86SP2SP2QFE
Netfxupdate.exe1.0.3705.373,72820-Aug-200711:06x86SP2SP2QFE
Setregni.exe1.1.4322.2034106,49620-Aug-200711:06x86SP2SP2QFE
Sy52106.dll1.1.4322.24251,232,89618-Sep-200704:52x86SP2SP2QFE
System.ldoNot applicable11,54005-Oct-200715:22Not applicableSP2SP2QFE
System.web.dll1.1.4322.24251,265,66405-Oct-200704:46x86SP2SP2QFE
Togac.exe1.1.4322.573118,78420-Aug-200711:07x86SP2SP2QFE

WORKAROUND

To 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:
    • Negotiate
    • NTLM
    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 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.

STATUS

Microsoft 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 Description of the standard terminology that is used to describe Microsoft software updates

Properties

Article ID: 942228 - Last Review: October 8, 2011 - Revision: 2.0
APPLIES TO
  • Microsoft .NET Framework 1.1
Keywords: 
kbfix kbqfe kbexpertiseadvanced KB942228

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com