Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Cannot log on to OWA through Netscape Communicator


View products that this article applies to.

Symptoms

When you try to log on to Outlook Web Access (OWA) through Netscape Communicator, you may receive the following error message:
Authorization Failed.

↑ Back to the top


Cause

This problem occurs because the Integrated Windows Authentication check box is selected for the Exchange virtual directory.

↑ Back to the top


Resolution

Netscape does not support the Integrated Windows Authentication logon method. To work around this problem in Microsoft Exchange Server 5.5, enable Basic Authentication on the Exchange virtual directory:
  1. Open Internet Service Manager.
  2. Right-click the Exchange virtual directory under the default Web site.
  3. On the Directory Security tab, click Edit under Anonymous access and authentication control.
  4. Click to select the Basic Authentication check box.
  5. Click OK to close all the dialog boxes, and then restart the Default Web site.
Note This procedure is not effective if you are running Microsoft Exchange Server 5.5 on Microsoft Windows NT Server 4.0.

To work around this problem in Microsoft Exchange 2000 Server, use Exchange System Manager to manage the authentication method. To do this, follow these steps:
  1. Open Exchange System Manager.
  2. Expand Servers, expand ServerName, expand Protocols, expand HTTP, and then expand Exchange Virtual Server.
  3. Right-click the Exchange virtual directory, and then click Properties.
  4. Click the Access tab, and then click Authentication.
  5. Click to select the Basic Authentication check box.
  6. Click OK to close all the dialog boxes.
  7. Wait for the authentication setting to replicate to the Exchange virtual directory in Internet Services Manager. Alternatively, restart the Microsoft Exchange System Attendant to force replication.

↑ Back to the top


Status

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

↑ Back to the top


Keywords: KB300512, kbnofix, kberrmsg, kbbug

↑ Back to the top

Article Info
Article ID : 300512
Revision : 5
Created on : 10/27/2006
Published on : 10/27/2006
Exists online : False
Views : 270