Error message when you try to access Web sites through a downstream server after you enable hotfix 927265 on an upstream server that is running ISA Server 2004 or ISA Server 2006: "502 Proxy Error"

Consider the following scenario:

• A downstream server is chained to an upstream server that is running Microsoft Internet Security and Acceleration (ISA) Server 2004 or Microsoft Internet Security and Acceleration (ISA) Server 2006.
• A client computer is configured to use the downstream server as the proxy server.
• On the upstream server, you have enabled the hotfix that is described in the following Microsoft Knowledge Base article:
  927265  (http://support.microsoft.com/kb/927265/ ) Authentication fails when client computers use Internet Explorer 7 to authenticate with an upstream ISA Server computer through a downstream ISA Server computer that does not require authentication

However, when a user on the client computer tries to access Web sites through the downstream server, the user receives the following error message:

This problem occurs because proxy-to-proxy authentication fails. The downstream server expects the upstream server to return "Negotiate" as a supported authentication scheme for Windows Integrated authentication. However, after you enable hotfix 927265, the upstream server is configured to return only "NTLM" as an authentication scheme for Windows Integrated authentication. Therefore, the downstream server and the upstream server cannot authenticate one another.

A hotfix package is available to resolve this problem. For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

The authentication process between the downstream server and the upstream server uses a special URL request. After you apply hotfix 938466, the upstream ISA Server computer will return "Kerberos" and "Negotiate" as supported authentication schemes if there is a special ISA-to-ISA authentication URL request.