Microsoft KB Archive/317627

= XWEB: Troubleshooting HTTP 401.x Errors in Outlook Web Access 5.5 =

Article ID: 317627

Article Last Modified on 10/28/2006

-

APPLIES TO


 * Microsoft Exchange Server 5.5 Service Pack 3
 * Microsoft Outlook Web Access 5.5
 * Microsoft Exchange Server 5.5 Service Pack 1
 * Microsoft Exchange Server 5.5 Service Pack 2

-



This article was previously published under Q317627



SUMMARY
This article describes some of the various reasons that you may receive a &quot;401 Unauthorized&quot; error message when you are using Microsoft Outlook Web Access (OWA). This article also provides some common methods that you can use to try to resolve such an error.



401.1 - Unauthorized: Logon Failed
This error may occur for the following reasons:  Local security policies. Every OWA user requires access to two local security policies:  The first local security policy is &quot;Log On Locally.&quot; To make sure that your users have this setting enabled:  Start User Manager for Domains. On the Policies menu, click User Rights. In the User Rights dialog box, click Log on Locally. In the Grant To box, add a domain group that your users belong to. Typically, this group is the Domain Users group. Adding such a domain group ensures that your users have access to log on locally.

NOTE: If Exchange is running on a member server, the change must be made to the local security policy for that server. To bring up the server's local security policy, click Start, click Run, and then type usrmgr .</ol> </li> The second local security policy is &quot;Access This Computer From the Network.&quot; To make sure that your users have this setting enabled: <ol> Start User Manager for Domains.</li> On the Policies menu, click User Rights.</li> In the User Rights dialog box, click Access This Computer From the Network.</li> In the Grant To box, add a domain group that your users belong to. Typically, this group is the Domain Users group. Adding such a domain group allows your OWA users access through this policy.</li></ol> </li></ul> </li> Basic authentication and the Windows NT domain name. OWA supports two authentication methods. Those methods are &quot;Basic&quot; and &quot;Windows NT Challenge Response (NTLM)&quot;. If you use the Basic authentication method in OWA and you do not supply a default domain name, you may receive this error message because the domain is omitted in the credentials dialog box.

To determine whether or not you are experiencing this issue, after you type your mailbox name in OWA, look at the credentials dialog box. If two boxes are displayed (User name and Password), you are probably using Basic authentication. If three boxes are displayed (User name, Password, and Domain), you are probably using NTLM authentication.

The exception to this rule is Microsoft Internet Explorer 6. If you use Internet Explorer 6, only the User name and Password boxes are displayed in the credentials dialog box, even if you are using NTLM authentication.

After you determine that you are using Basic authentication, try using the following format for your logon information: <ul> User name:

\ (for example, microsoft\user1)

</li> Password:

</li></ul>

If you can use the preceding format to log on without receiving the 401.1 error message, to avoid this issue in the future, either:

<ul> Instruct your users to log on by using that format. -or-

</li> Add a default domain in the Basic authentication section of Internet Information Services (IIS) for OWA: <ol> On the OWA server, start Internet Services Manager.</li> Expand the Web site in which OWA is installed, right-click the Exchange virtual directory, and then click Properties.</li> Click the Directory Security tab, and then click Edit next to Anonymous access and Authentication Control.</li> Click Edit next to Basic authentication.</li> Use one of the following steps, as appropriate: <ul> If all of your user accounts exist in one Windows NT domain, type that domain name in the Default Domain box. -or-

</li> <li>If your user accounts are spread among multiple domains, it is easier to type \ in the Default Domain box. If you type \ in the Default Domain box, OWA searches all of the trusted domains for the user name.</li></ul> </li></ol>

After you add a default domain, the users can gain access to OWA by just supplying their user name and password, instead of typing \.

</li></ul> </li> <li>File-level antivirus scanning software. A file-level antivirus scanning utility that is actively scanning the Exchsrvr folder on the hard disk can also cause this error. This issue can also manifest itself as a blank screen in the Web browser, instead of as an error message.

At a minimum, exclude the Exchsrvr\Mdbdata, Exchsrvr\Webdata, and Exchsrvr\Webtemp folders from file-level antivirus scans. If you do not exclude these folders, issues may occur with both OWA and MAPI clients. Refer to your antivirus software's documentation for instructions about how to exclude files and folders.

If you are concerned about mail-related viruses in Microsoft Exchange Server, obtain antivirus software which is &quot;Exchange Server-aware&quot;. Exchange Server-aware antivirus software uses scanning methods for the Exchange Server store that are not damaging. Exchange Server-aware antivirus software uses the antivirus application programming interface (API) that is built into Exchange Server.</li></ul>

401.3 - Unauthorized Due to ACL on Resource
This error is usually the result of not having the required NTFS security permissions on a file or registry key. To determine if this error is the result of not having the required NTFS security permissions: <ol> <li>Confirm that the Everyone group has at least the minimum permissions that are required on the folders in the following table. To view the permissions on a folder, open the properties of the folder, and then click the Security tab. If the Security tab is missing, the folder resides on a file allocation table (FAT) partition. There are no specific file-level permissions on a FAT partition. If the folder is on a FAT partition, skip to step 2 (registry permissions).

</li> <li>Confirm that the Everyone group has at least the minimum permissions required on the registry keys in the following table. To view security settings on registry keys:

<ol> <li>Click Start, and then click Run.</li> <li>In the Run dialog box, type regedt32.exe .</li> <li>Click the registry key that you want to view the security settings for, and then click Permissions on the Security menu.</li></ol>

</li></ol>

401.1 - Unauthorized: Logon Failed
This error may occur for the following reasons: <ul> <li>Local security policies. Every OWA user requires access to two local security policies: <ul> <li>The first security policy is &quot;Log On Locally.&quot; To make sure that your users have this setting turned on: <ol> <li>Start the Local Security Policy snap-in.

NOTE: If OWA is installed on a Windows 2000-based computer that is a domain controller, start the Domain Controller Security Policy snap-in.</li> <li>Expand Local Policies, and then expand User Rights Assignment.</li> <li>In the right pane, click Log on Locally.</li> <li>In the Assign To box, add a domain group that your users belong to. Typically, this group is the Domain Users group. Adding such a domain group ensures that your users have access to log on locally.</li></ol> </li> <li>The second Local Security Policy is &quot;Access This Computer From the Network.&quot; To make sure that your users have this setting turned on: <ol> <li>Start the Local Security Policy snap-in.

NOTE: If OWA is installed on a Windows 2000-based computer that is a domain controller, start the Domain Controller Security Policy snap-in.</li> <li>Expand Local Policies, and then expand User Rights Assignment.</li> <li>In the right pane, click Access This Computer From the Network.</li> <li>In the Assign To box, add a domain group that your users belong to. Typically, this group is the Domain Users group. Adding such a domain group allows your OWA users access through this policy.</li></ol> </li></ul> </li> <li>Basic authentication and the Windows NT domain name. OWA supports two authentication methods. Those methods are &quot;Basic&quot; and &quot;Windows NT Challenge Response (NTLM).&quot; If you use the Basic authentication method in OWA and you do not supply a default domain name, you may receive this error message because the domain name is omitted in the credentials dialog box.

To determine whether or not you are experiencing this issue, after you type your mailbox name in OWA, view the credentials dialog box. If two boxes are displayed (User name and Password), you are probably using Basic authentication. If three boxes are displayed (User name, Password, and Domain), you are probably using NTLM authentication.

The exception to this rule is Internet Explorer 6. If you use Internet Explorer 6, only the User name and Password boxes are displayed in the credentials dialog box, even if you are using NTLM authentication.

After you determine that you are using Basic authentication, try using the following format for your logon information:

<ul> <li>User name:

\ (for example, microsoft\user1)

</li> <li>Password:

</li></ul>

If you can use the preceding format to log on without receiving the 401.1 error message, to avoid this issue in the future, either: <ul> <li>Instruct your users to log on by using that format. -or-

</li> <li>Add a default domain in the basic authentication section of IIS for OWA: <ol> <li>On the OWA server, start Internet Services Manager.</li> <li>Expand the Web site in which OWA is installed, right-click the Exchange virtual directory, and then click Properties.</li> <li>Click the Directory Security tab, and then click Edit next to Anonymous access and Authentication Control.</li> <li>Click Edit next to Basic authentication.</li> <li>Use one of the following steps, as appropriate: <ul> <li>If all your user accounts exist in one Windows NT domain, type that domain name in the Default Domain box. -or-

</li> <li>If your user accounts are spread among multiple domains, it is easier to type \ in the Default Domain box. If you type \, OWA searches all of the trusted domains for the user name.</li></ul> </li></ol>

After you add a default domain, the users can gain access to OWA by just supplying their user name and password, instead of typing \.

</li></ul> </li> <li>File-level antivirus scanning software. A file-level antivirus scanning utility that is actively scanning the Exchsrvr folder on the hard disk can also cause this error. This issue can also manifest itself as a blank screen in the Web browser, instead of as an error message.

At a minimum, exclude the Exchsrvr\Mdbdata, Exchsrvr\Webdata, and Exchsrvr\Webtemp folders from file-level antivirus scans. If you do not exclude these folders, issues may occur with both OWA and MAPI clients. Refer to your antivirus software's documentation for instructions about how to exclude files and folders.

If you are concerned about mail-related viruses in Exchange Server, obtain antivirus software that is &quot;Exchange Server-aware.&quot; Exchange Server-aware software uses scanning methods for the Exchange Server store that are not damaging. Exchange Server-aware antivirus software uses the antivirus application programming interface (API) that is built into Exchange Server.</li> <li>OWA is installed on Windows 2000. Users who log on to OWA from a computer that is running any Microsoft Windows operating system other than Windows 2000 can gain access to OWA, but users who log on to OWA from a computer that is running Windows 2000 may receive a 401.1 error message.

This issue can occur if OWA is installed on a computer that is running Windows 2000 Server with Integrated Windows Authentication turned on as one of the authentication methods on the Exchange Server virtual directory.

To resolve this issue, on the server that OWA is installed on, edit the Constant.inc file in the Exchsrvr\Webdata\Usa folder:

<ol> <li>Use Notepad to open the Constant.inc file.</li> <li>Under '--Other Strings--', locate the following line:

bstrAuthTypesAccepted = &quot;_BasicNTLMDPAMBS_BASIC&quot;

</li> <li>Change the line to read:

bstrAuthTypesAccepted = &quot;_BasicNTLMDPAMBS_BASICNegotiate&quot;

</li> <li>On the File menu, click Save.</li> <li>On the File menu, click Exit.</li></ol>

If you use a computer that is running either Microsoft Windows 2000 Server and Internet Explorer 5 or Microsoft Windows 2000 Professional and Internet Explorer 5 to try to log on to Internet Information Service (IIS) 5.0, and Integrated Windows Authentication is enabled, a negotiation is performed to determine if the Kerberos protocol or Windows NT Challenge/Response will be used for authentication.

If you use a computer that is running either Windows 2000 Server and Internet Explorer 5 or Windows 2000 Professional and Internet Explorer 5, the server variable AUTH_TYPE is set to Negotiate. When you use a computer that is running any other Windows operating system, the server variable is set to NTLM. OWA checks what this variable returns against the bstrAuthTypesAccepted value that is modified. This check ensures that the authentication type is acceptable before OWA allows a user to log on.</li></ul>

401.3 - Unauthorized Due to ACL on Resource
This error is usually the result of not having the required NTFS security permissions on a file or registry key. To determine if this error is the result of not having the required NTFS security permissions: <ol> <li>Confirm that the Everyone group has at least the minimum permissions that are required on the folders in the following table. To view the permissions on a folder, open the properties of the folder, and then click the Security tab. If the Security tab is missing, the folder resides on a FAT partition. There are no specific file-level permissions on a FAT partition. If the folder is on a FAT partition, skip to step 2 (registry permissions).

</li> <li>Confirm that the Everyone group has at least the minimum permissions that are required on the registry keys in the following table. To view security settings on registry keys:

<ol> <li>Click Start, and then click Run.</li> <li>In the Run dialog box, type regedt32.exe .</li> <li>Click the registry key that you want to view the permissions for, and then click Permissions on the Security menu.</li></ol>

</li></ol>

Keywords: kbhowto KB317627

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.