Microsoft KB Archive/317822

= FIX: Problems with Web Browser if ISA Server 2000 Is Chained to an Upstream Web Proxy Server =

Article ID: 317822

Article Last Modified on 6/14/2007

-

APPLIES TO


 * Microsoft Internet Security and Acceleration Server 2000 Standard Edition

-



This article was previously published under Q317822



IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry



SYMPTOMS
If Internet Security and Acceleration (ISA) Server 2000 is chained to an upstream Web proxy server, you may experience unexpected delays, incomplete pages, random authentication warning messages, and so forth, when you browse the Web.

This behavior does not occur if the upstream proxy server requires NTLM authentication and the routing rule on the downstream server is configured to provide Integrated Authentication credentials to the upstream Web proxy server.



CAUSE
This behavior can occur if all of the following conditions are true:
 * The downstream ISA Server computer is configured to require integrated authentication (NTLM).

-and-
 * The upstream Web proxy server is not configured to require authentication (anonymous).

-and-
 * You are using Internet Explorer as your client browser.

Under certain circumstances, Internet Explorer sends an extraneous NTLM authentication header on a connection that has already been authenticated with the downstream ISA Server computer by using integrated authentication. This may cause the downstream ISA Server computer to pass those credentials to the upstream Web proxy server. Because these credentials are for the downstream ISA Server computer, the upstream proxy server may return unexpected delays or responses because it is unable to process the NTLM credentials. The downstream ISA Server computer then passes this HTTP response back to the Web browser, resulting in unexpected delays, authentication warning messages, or other effects on the client computer (running Internet Explorer).



RESOLUTION
Note that you must have ISA Server 2000 Service Pack 1 (SP1) installed on your computer before you apply the following fix.

For additional information about how to obtain ISA Server 2000 SP1, click the article number below to view the article in the Microsoft Knowledge Base:

313139 How to obtain the Latest Internet Security and Acceleration Server 2000 Service Pack

A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

The English-language version of this fix should have the following file attributes or later:   Date        Time      Version       Size     File name 27-Feb-2002 14:10:00 3.0.1200.170  383,760  W3proxy.exe



STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.



MORE INFORMATION
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To implement the functionality in this fix and then enable it, follow these steps after you have installed the fix:  Stop the Web Proxy service. Start Registry Editor. Locate and select the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3Proxy\Parameters

 Create a new DWORD value named RemoveAllProxyAuthorization. Give this new value a data value of 1.</li> Restart the Web Proxy service.</li></ol>

To revert to the original configuration, either remove the RemoveAllProxyAuthorization registry value or change its data value to 0 (zero). After you make either change, restart the Web Proxy service.

<div class="references_section">