You are prompted repeatedly for password when publishing or saving to IIS 5.0 server

When you use the FrontPage 2000 client, you are prompted repeatedly for your user name and password when you attempt to publish a Web or save Web pages to a Web server that is running Microsoft Internet Information Services (IIS) version 5.0.

The default text for an HTTP 401.1 error message is contained in an HTML file that is included with Internet Information Services (IIS) version 5.0. This default text is too large for the FrontPage client to parse correctly when using NTLM authentication.

A fix is available from Microsoft in versions of the Fp4awec.dll file with a revision number of 4.0.2.3702 or later. The following table lists release versions for the Fp4awec.dll file that incorporate this fix. To download the latest version of the server extensions, browse to the following Microsoft Web site:

To work around this problem, use one of the following methods.

Method 1

Set the 401.1 error message to default, rather than the HTML file that is included with IIS 5.0. To do this, follow these steps:

1. Open the Internet Service Manager on the Web server.
2. Right-click your Web site.
3. Click Properties.
4. Click the Custom Errors tab.
5. Click to select the 401.1 error message.
6. Click Edit Properties.
7. In the message type list, select Default, rather than File.
8. Click OK twice.

Method 2

Configure the Web site to use Basic authentication.

Note Basic authentication sends user names and passwords over the network in clear text. This presents a significant security risk. Basic authentication should be used only together with SSL because SSL can encrypt the information that is being sent over the network.

To configure the Web site to use Basic authentication, follow these steps:

1. Open the Internet Service Manager on the Web server.
2. Right-click your Web site.
3. Click Properties.
4. Click the Directory Security tab.
5. Click the Edit button for Anonymous access and authentication control.
6. Select the Basic authentication check box.
7. Click Yes.
8. Click OK twice.

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