Article ID: 237960 - View products that this article applies to.
This article was previously published under Q237960
This article has been archived. It is offered "as is" and will no longer be updated.
After you upgrade from the FrontPage 98 Server Extensions to the FrontPage 2000 Server Extensions, you can no longer open FrontPage Webs that reside on an Internet Information Server (IIS) computer when connecting through a Raptor firewall.
The FrontPage 2000 client returns the following error messages:
The folder 'http://servername' isn't accessible. The folder may be located on an unavailable volume or protected with a password. For details see C;\TEMP\wecerr.txt.
The FrontPage 98 client returns the following error message:
The server sent a response which FrontPage could not parse.
If you click Details, usually no additional information is provided and the Details dialog box is blank.
The server could not complete your request. Contact your Internet service provider or web server administrator to make sure that the web server has the FrontPage Server Extensions installed. For more specific information, click Details.
When you attempt to open a FrontPage 2000 Extended Web that can be browsed anonymously, FrontPage makes a post to the Author.dll file. This causes an HTTP 401 error message to be returned to the FrontPage client for authentication. The HTTP 401 error message never makes it through the firewall or proxy server, and the FrontPage client times out.
To resolve this problem, obtain Microsoft Office 2000 Service Release 1/1a (SR-1/SR-1a).
To obtain SR-1/SR-1a, click the article number below to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/245025/EN-US/ )OFF2000: How to Obtain and Install Microsoft Office 2000 Service Release 1/1a (SR-1/SR-1a)
Method 1To work around this problem, you must cause a complete HTTP 401 error to be generated. To do this, you will need to restrict anonymous access to the _vti_aut and _vti_adm virtual directories for each Web. When you open a FrontPage Web, FrontPage accesses these virtual directories anonymously. By restricting anonymous access to this file, a complete HTTP error is returned earlier in the Open Web Sequence, and this error is correctly passed through the firewall. To do this, perform the following steps:
If you later uninstall and reinstall the Server Extensions to the Web site, you will need to configure _vti_aut and _vti_adm without Anonymous Access again using the steps above.
Method 2If you have many virtual servers, the following workaround may be easier to use:
Microsoft has confirmed that this is a problem in FrontPage 2000 Server Extensions. This problem was corrected in Microsoft Office 2000 SR-1/SR-1a.
This problem occurs when you use the FrontPage 2000 Server Extensions with the Raptor firewall, Gauntlet Internet firewall, and the WinProxy proxy server.
The third-party products that are discussed in this article are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.