No Supported Authentication Methods Found in Response


Topic Last Modified: 2012-05-21

The Microsoft Exchange Remote Connectivity Analyzer sends an HTTP request to test the authentication methods of a specified service. If a 401 unauthorized response is received, the Analyzer expects certain WWW-Authenticate headers in the response. These headers indicate the supported authentication methods for the service. If no WWW-Authenticate headers are received, the Analyzer generates the following error:

"No supported Authentication Methods found in Response"

This issue will prevent users from being able to successfully connect to the specified service.

For More Information

To resolve this issue, do the following:

  1. Confirm that the proper authentication methods are selected for the virtual directories in IIS.

  2. If the entry point to your Exchange server is ISA Server 2006, check the publishing rule to determine whether the rule is configured to disallow all authentication. Go to the delegation tab and view the list beneath "Method used by ISA Server to authenticate to the published Web server." The "No delegation and Client may not authenticate directly" option disables any authentication on the rule. Because all Exchange Services require some type of authentication, select on the menu a different delegation method that suits your environment.

For more information about how to publish Exchange 2007 Services through Microsoft ISA Server 2006, see Publishing Exchange Server 2007 with ISA Server 2006.

The Exchange Remote Connectivity Analyzer is a new tool that has limited documentation at this time. In an effort to improve the documentation for each of the errors you might receive, we would like to solicit additional information from the community. Please use the Community Content section below to post additional reasons why you failed at this point. If you need technical assistance, please create a post in the appropriate Exchange TechNet forum or contact support.