This article has been archived. It is offered "as is" and will no longer be updated.
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
When you Web publish a Web Distributed Authoring and Versioning (WebDAV) folder, external clients may not be able to gain access to the folder.
The hotfix that is described in this article corrects a problem with Web publishing WebDAV folders with Internet Security and Acceleration (ISA) Server by allowing ISA Server to respond correctly to the Web browser by sending the actual Options that are sent by the WebDAV server.
This is an example of a normal HTTP response by a WebDAV server:
Value Name: PassOPTIONSToPublishedServer Data Type : REG_DWORD Data : 1 Default : 0
Set this parameter to 1. The data can be any non-zero value.
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 resolve this problem, obtain latest service pack for ISA Server 2000. For additional information about the latest service pack, click the following article number to view the article in the Microsoft Knowledge Base:
313139 How to obtain the latest Internet Security and Acceleration Server 2000 Service Pack
The English version of this fix should have the following file attributes or later:
Date Time Version Size File name ----------------------------------------------------- 26-Aug-2001 17:34 3.0.1200.69 381,712 W3proxy.exe
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Microsoft Internet Security and Acceleration Server 2000 Service Pack 1.