Troubleshooting Outlook Web Access Publishing
This document describes a strategy for troubleshooting common issues that occur when publishing Microsoft® Exchange servers using Microsoft Outlook® Web Access. Typical symptoms of problems in this scenario include the following:
- Users do not have access to Outlook Web Access following installation or upgrade.
- All users (or some users) cannot access Exchange using Outlook Web Access.
- Issues occur when publishing Outlook Web Access through a Microsoft Internet Security and Acceleration (ISA) Server computer configured with a single network adapter.
- There are specific connection, logon, or authentication issues.
Run the ISA Server Best Practices Analyzer
For initial troubleshooting, run the Microsoft ISA Server Best Practices Analyzer Tool. This tool scans configuration settings of the local ISA Server computer, and reports issues that do not conform to best practices. The ISA Server Best Practices Analyzer can run on ISA Server 2006 or ISA Server 2004. In Enterprise Edition, run the ISA Server Best Practices Analyzer on each array member. Microsoft .NET Framework 1.1 must be installed on the computer.
Install and run the ISA Server Best Practices Analyzer as follows:
- Download from the Microsoft Download Center. Installation files are copied to the %SystemDrive%\Program Files\IsaBPA folder.
- Run the tool. To do this, click Start, point to All Programs, point to Microsoft ISA Server, point to ISA Tools, and then click ISA Server Best Practices Analyzer. Then click Start a scan.
Each ISA Server Best Practices Analyzer error or warning message has an associated Help topic, with instructions about how to fix the issue.
Installation and upgrade issues
For issues following installation or upgrade, check the following:
- Ensure you have a publishing rule to allow external clients to access the Outlook Web Access site. Rules are created using the New Publishing Rule Wizard. For more information, see the following documents at Microsoft TechNet:
- Check rule ordering. If there is a deny rule blocking access to the site, and this rule is ordered before the allow rule, the deny rule will be processed first. Rules should follow this order from the top of the rule list:
- Global deny rules. Rules that deny access to all users.
- Global allow rules. Rules that allow specific access to all users.
- Rules for specific computers.
- Rules for specific users, URLs, and MIME types.
- Other allow rules.
- Default deny rule, which is at the bottom of the list. Requests not matched by any other rule in the list are blocked by this default rule.
- When you upgrade from ISA Server 2004 Standard Edition to ISA Server 2004 Enterprise Edition, and then to ISA Server 2006 Enterprise Edition, upgraded Exchange publishing rules do not have credential delegation enabled by default. Users allowed access with these rules will be prompted twice for credentials. Check delegation settings on these upgraded rules. For more information, see Microsoft article 935767.
If some or all users cannot connect to the Outlook Web Access site, check the following:
- Syntax issues:
- Ensure that the user is typing the correct URL.
- Check that the user is specifying credentials with the syntax \.
- Check that a user is typing a correct password, and that the CAPS LOCK feature is not turned on.
- Ask the user to access another Web page to check that the browser is not the issue.
- Log on to the mailbox from another non-administrator account to check that it is available. If the new account is working, compare the Active Directory® directory service configuration for that account with the user account that is not working.
- Name resolution issues:
- Internal clients on the same network as the Exchange server should not loop through the ISA Server external interface to access the published server. Instead, these clients should access the published server directly, and they must be able to internally resolve the fully qualified domain name (FQDN) of the published server. They may use an internal Domain Name System (DNS) server with a resource record for name resolution, or through means of a Hosts file on the client. Note the following:
- SecureNAT clients (with a default gateway pointing to ISA Server) handle their own name resolution, and the internal DNS server that they use must resolve the site name.
- For Firewall clients, specify the FQDN for direct access. For more information, see the section "Firewall Client Local Addresses" in "Internal Client Concepts in ISA Server 2006" at Microsoft TechNet.
- Client computers making requests as Web proxy clients should be configured for direct access. For more information, see the section "Web Proxy Clients" in "Internal Client Concepts in ISA Server 2006" at Microsoft TechNet.
- Rule configuration:
- Check the properties of the Outlook Web Access publishing rule.
- Check that the user is not being denied access by some other rule that is ordered higher in the rule list.
Single network adapter issues
ISA Server provides support for publishing Outlook Web Access with a single network adapter. In this configuration, check the following:
- Ensure that ISA Server is configured with the Single Network Adapter network template.
- When you install ISA Server on a computer with a single network adapter, ISA Server is only aware of two networks: the Local Host network that represents the ISA Server computer itself, and the Internal network, which includes all unicast IP addresses that are not part of the Local Host network. Ensure that the Web listener you select in the Outlook Web Access publishing rule is configured to listen on the Internal network.
For connection issues, check the following:
- To check whether the connection issue is associated with a specific client computer, try to connect to the Outlook Web Access site from an alternative computer.
- If no computers can access the Outlook Web Access site, check that the site is available and running.
- Check the following DNS and name issues:
- External Internet clients require a valid public DNS entry to resolve requests. The domain name can be registered with a public DNS server to resolve the name to the appropriate IP address of the ISA Server computer (usually the IP address of the external adapter).
- The name specified in external client requests for the Outlook Web Access site must match the FQDN specified in the Common Name field of the server certificate used by ISA Server to authenticate to the client.
- Checks to verify name resolution include the following:
- To test the deployment, you can specify the name resolution information in the Hosts file. When you connect to the Outlook Web Access site (for example https://mail.fabrikam.com/exchange), a logon page should appear, allowing you to input credentials.
- Use the Nslookup.exe command-line tool to check that the external Web site name is resolved as expected. For more information, see "Nslookup" at Microsoft TechNet.
Authentication and logon issues
For logon issues or authentication problems, check the following:
- Use the full URL when connecting with Outlook Web Access, for example, https://servername/exchange/username. With Outlook Web Access, users do not need to know the full URL to their mailbox to log on. They type https://servername/exchange and when prompted by the browser, enter their user name and password. Exchange then uses the user name and password information to look up the full URL path to the user's mailbox in Active Directory, and then routes the user to the correct mailbox. When you connect using the full URL, Exchange does not perform the Active Directory lookup. If you can access the mailbox using the full URL, but cannot access the mailbox by logging on with the shorter URL, the access problem may be related to authentication.
- Set the authentication method to Basic. This is particularly useful for access problems due to improperly configured permissions. For security reasons, never select Basic authentication as your only authentication method unless you also use Secure Sockets Layer (SSL) encryption. If using Basic authentication with no other authentication method allows you to access the mailbox, the access problem may be caused by Integrated Windows authentication or Anonymous access. Integrated Windows Authentication refers to authentication mechanisms registered on the Exchange server, such as NTLM and Kerberos.
- Check HTTP errors. Users may receive a number of common HTTP errors when accessing an Outlook Web Access site, including the following:
- 401 Access Denied and 401 Logon Failed. Indicates that the user name or password is incorrect. Verify that the password has been specified correctly, and that the CAP LOCKS feature is not turned on. Ensure that the name is specified with the syntax "\". If the user account was recently created, it may take a few minutes for it to be properly initialized.
- 403 Access Denied. Indicates that the user authenticated successfully, but cannot access a resource. For example, the user attempted to access the server with https://, when https:// is required. Ensure that the Exchange virtual directory that the user is trying to access is available.
- 404 Not Found. Indicates that an item requested does not exist in a specified location. This can happen if an item has been denied. In addition, ensure that users are typing a correct URL to access a resource.
- 405 Method Not Allowed. May indicate that the running of scripts or executable files is not allowed, and you attempted to run an .asp page or access a .dll file.
- 500 Internal Server Error. May indicate that the Exchange server is unable to contact Active Directory. It may also indicate general Internet Information Services (IIS) authentication issues. It can also occur when the user browser supports Kerberos authentication, and the difference in clock settings between the client computer and the Exchange server is greater than five minutes. Try synchronizing the time.
- Check whether forms-based authentication is enabled on both the ISA Server computer and the Exchange computer. It should be configured only on one of them.
- Check that users can authenticate in accordance with the authentication settings specified in the publishing rule. For example, if a rule has a condition allowing access only to a specific group account, ensure that users that require access belong to the group.
- Check the bridging configuration of the rule. For example, if bridging is configured to redirect HTTPS requests over HTTPS to the published server, ensure that the Web listener used by the rule is listening for HTTPS requests.
- If there is an issue for users who type https://www.address.com instead of https://www.address.com, ensure that redirection settings are configured as required. In ISA Server 2004, you can create a Web page that provides a link that users can click to take them to the https site. In ISA Server 2006, you can enable HTTP to HTTPS redirection in ISA Server Management, as shown in the following procedure.
To enable HTTP to HTTPS redirection
In ISA Server Management, click the Firewall Policy node.
On the Toolbox tab, right-click the Web listener used by the rule that allows users access, and then click Properties.
On the Connections tab, ensure that Enable HTTP connections on port and Enable SSL (HTTPS) connections on port are selected.
Select one of the following options:
- To redirect all traffic handled by this listener, select Redirect all traffic from HTTP to HTTPS.
- To redirect only requests from authenticated users, select Redirect authentication traffic from HTTP to HTTPS. This option is useful when you are publishing a secure Outlook Web Access site requiring authentication and a non-secure site with anonymous access using the same Web listener.
If a problem arises when requesting a certificate, do the following:
- Ensure that you are requesting a certificate correctly:
- Use the Certificates Microsoft Management Console (MMC) snap-in to request a certificate from an enterprise certification authority (CA) when ISA Server is a member of an enterprise CA domain. Otherwise, use the Web enrollment site to request a certificate. The CA root certificate of the enterprise CA is automatically entered into the Trusted Root Certification Authorities store for all computers in the same domain as the CA. If the ISA Server computer is not a domain member, manually place the CA certificate into the Trusted Root Certification Authorities store on the ISA Server computer.
- If you receive a message that the CA is not started or there is a permissions problem, this may indicate an issue with DCOM that is required to acquire a certificate. As a workaround, do the following:
- Disable the RPC setting as follows:
If ISA Server is requesting the certificate, edit the system policy rule.
If an internal host is requesting the certificate from another network through ISA Server, edit the access rule allowing DCOM traffic between the different networks.
- Whether it is ISA Server requesting a certificate or an internal host requesting a certificate from another network, after clearing the Enforce strict RPC compliance setting, you need to create a rule to allow all traffic or a rule for a custom protocol.
To edit the RPC setting in the system policy rule
In ISA Server Management, click the Firewall Policy node.
On the Tasks tab, click Edit System Policy.
In the Configuration Groups list, select the Active Directory group.
On the General tab, clear the Enforce strict RPC compliance check box. To edit the RPC setting in the access rule
In ISA Server Management, click the Firewall Policy node, and then select the required rule.
On the Tasks tab, click Edit Selected Rule.
On the Protocols tab, click Filtering, and then click Configure RPC Protocol.
Clear the Enforce strict RPC compliance check box.
On the Configuration node of ISA Server Management, click Add-Ins.
Right-click RPC Filter in the details pane, and then click Disable.
Repeat this procedure for any other access rules that are configured between the networks. Ensure that you enable all settings again after requesting the certificate.
- Disable the RPC setting as follows:
Certificate error messages
If you receive the error message: "500 Internal Server Error – The target principal name is incorrect", check the following:
- The name of the server certificate used by ISA Server to authenticate to the external client must match the name that the external client types in the browser to reach the ISA Server computer.
- If you are using HTTPS to HTTPS bridging (where the client authenticates to ISA Server over HTTPS and ISA Server forwards the request to the published Web server over HTTPS), the name of the server certificate that the published server uses to authenticate to the ISA Server computer must match the internal server name specified on the To tab of the publishing rule properties.
- If you use the same server certificate to authenticate the ISA Server computer to the client and the published Web server to the ISA Server computer, the URL typed by the client and the internal name of the Web server must be the same as the common name of the certificate. To resolve the issue, either obtain a new certificate that matches the required name, or modify the internal name and external name to match the common name on the certificate. Ensure that ISA Server can resolve the internal name of the published Web site. If you modify the name on the To tab, one way to ensure that the name can be resolved is to add a Hosts file entry on the ISA Server computer (WINNT\system32\drivers\etc\hosts) to map the name and IP address of the published site.
- If you are using a wildcard certificate on the ISA Server computer, note the following:
- When using HTTPS to HTTP bridging in ISA Server 2004, you cannot use a wildcard certificate to authenticate to the back-end Web server. Instead, on the internal Web server, create a new certificate that matches the name of the internal Web server, as specified on the To tab in the Web publishing rule.
- Use of wildcard certificates on the back-end server is supported in ISA Server 2006.
If you receive the error message: "500 Internal Server Error - The certificate chain was issued by an authority that is not trusted", do the following:
- Check that ISA Server trusts the CA that issued the certificate used to authenticate the published Web server, as described in the following procedure.
To check certificate trust
In Internal Explorer, click the Tools menu, and then click Internet Options.
On the Content tab, click Certificates.
On the Trusted Root Certification Authorities tab, check that a certificate for the CA appears.
- Ensure that there is a trust relationship defined between the installed certificate and the issuing CA. To do this, on the Certification Path of the certificate properties, you should see a hierarchical relationship, and a note that states: This certificate is OK.
If you receive a message that the certificate cannot be found, this indicates that the certificate was not imported to the correct certificate store, or that you did not choose to export the private key during the export certificate process. Do the following:
- Check that the certificate was imported under the Local Computer account and stored in the Personal certificates store.
- Ensure that the certificate has a corresponding private key on the Details tab of the certificate properties. If it does not, you will not be able to bind it to a Web listener when you create the Web publishing rule. If it is the certificate you imported to ISA Server from the Web server, export it again from the Web server, and repeat the import to the ISA Server computer.
If you receive a message that it is the wrong type of certificate, check that the relevant usage of the certificate is correctly configured. To do this, in the MMC Certificates snap-in, right-click the certificate, and then click Properties. Select Enable only the following purposes, and make sure that Server Authentication is selected.
If you receive a message about the validity of the certificate, check the validity information on the General tab of the certificate properties.
E-mail message issues
To troubleshoot issues with e-mail through Outlook Web Access, do the following:
- If you are authenticating using SecurID credentials and you receive an invalid SecurID passcode message when you try to access a file or application for download by clicking the Information bar in Internet Explorer, add the URL of the file or application to the trusted sites list in Internet Explorer. For more information, see "You are repeatedly prompted for credentials when you use SecurID authentication to access a document or program that is published by ISA Server 2006" at Microsoft Help and Support.
- If you cannot download attachments and you receive an attachment blocked message, ensure that the setting to block attachments is not enabled, as described in the following procedure.
To verify block attachments settings
In ISA Server Management, click the Firewall Policy node.
On the Toolbox tab, click Network Objects.
On the toolbar beneath Network Objects, click Edit.
On the Preferences tab, click Authentication.
Verify that the forms-based authentication method is selected, and then click Configure:
- If Outlook Web Access clients are not allowed to receive attachments on public computers, select Clients on public machines.
- If Outlook Web Access clients are not allowed to receive attachments on private computers, select Clients on private machines.
This section summarizes common issues that you may encounter.
Identical certificate on each array server
Issue: When I try to configure a listener for an Outlook Web Access rule, I receive the following message: To select a certificate, you must install at least one identical certificate on each member server.
Solution: In an array with multiple servers, you must install the exact same certificate on each array member.
Modifying the forms-based authentication page
Issue: Is modification of the Outlook Web Access forms-based authentication page a supported scenario?
Solution: It is supported for ISA Server 2006. It is not supported for ISA Server 2004. For more information, see Customizing HTML Forms in ISA Server 2006, at Microsoft Technet.
Common Name field of certificate
Issue: When I generate a Certificate Signing Request, what do I put in the Common Name field?
Solution: The Common Name field contains the domain or server name. Do not include https:// before the name or any subfolders indicated by the / after the domain name. Do not add the port number. Valid examples are: www.contoso.com, contoso.com, and secure.contoso.com.
500 Internal Server Error – The target principal name is incorrect
Issue: I receive the following error message: 500 Internal Server Error – The target principal name is incorrect.
Solution: This error message occurs when the name in the SSL client request from ISA Server does not match the common name on the Web site certificate. For the certificate on the ISA Server computer, the name must match the name that the external clients specify to reach the site. For the certificate on the published Web server, the name must match the name that appears on the To tab of the rule. To troubleshoot, either obtain a new certificate that matches the required name, or modify the required name to match the certificate’s common name. In addition, make sure that ISA Server can resolve the name to the IP address of the published Web site. If you modify the name on the To tab, one way to ensure that the name can be resolved is to add a Hosts file entry on the ISA Server computer (WINNT\system32\drivers\etc\hosts) to map the name and IP address of the published site.
Issue: I am publishing remote procedure call (RPC) over HTTP, and even though the name in the client request matches the name of the certificate on the ISA Server computer, the following error message appears: 500 Internal Server Error – The target principal name is incorrect.
Solution: When you create a new Outlook profile, on the Connection tab of Exchange Server Settings, you click Exchange Proxy Settings to specify RPC over HTTP settings. In Use this URL to connect to my proxy server for Exchange, ensure that you have typed the same name that appears on the certificate. Select Mutually authenticate the session when connecting with SSL, and then in Principal name for proxy server, again type the name that appears on the common name of the certificate. For example, if the common name is the FQDN used by clients to reach the site, you will type it in the form msstd:common name.
Publishing multiple SSL sites using the same IP address and port
Issue: How can I publish multiple SSL sites using the same IP address and port, with different certificates?
Solution: You can only use one SSL certificate per listener. If all sites are published using the same domain name, you can use a wildcard certificate, and then use a single IP address and a single listener to publish multiple sites. For example, if you are trying to publish the following sites: OWA, WebSite1, and WebSite2 at domain.com, you can acquire a wildcard certificate for the ISA Server computer for *.domain.com. Note that a wildcard certificate can only be used if sites are in the same domain.
500 Internal Server Error – The certificate chain was issued by an authority that is not trusted
Issue: I receive an error message: "500 Internal Server Error – The certificate chain was issued by an authority that is not trusted".
Solution: ISA Server must trust the certificate from the published Web server. Ensure that the CA certificate is in the ISA Server Trusted Root Certification Authorities certificate store.
No certificates configured on this server
Issue: When I try to create a Web listener with a certificate, the following message appears: "There are no certificates configured on this server". I have a certificate, so why can I not add it?
Solution: This message may also be accompanied by an event in Event Viewer indicating that the certificate private key could not be accessed. This error message may occur in the following circumstances:
- The SSL certificate and its corresponding private key were not imported to the correct certificate store on the ISA Server computer. The SSL certificate has been moved from one certificate store to another, causing the SSL certificate to separate from its corresponding private key.
- When you exported the certificate from the Web server, you did not indicate that the private key should be exported.
- Check that the private key was exported, and that the certificate was imported under the Local Computer account into the Personal store.
Multiple common names on certificate
Issue: I want to use a certificate with multiple common names in it, for example, to reference https://server_name and https://www.server_name.com. Can ISA Server handle these multiple common names?
- Solution: No, ISA Server only references the first common name in the certificate, and does not support multiple names.