Article ID: 822594 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
When you try to connect to Microsoft Exchange Server 2003 by using a remote procedure call (RPC) over HTTP connection, the connection may not succeed, or the connection may revert to a TCP (Transmission Control Protocol) connection.
This issue may occur if you try to connect to the Exchange server by using Microsoft Outlook with Secure Sockets Layer (SSL) enabled. This issue occurs if the server-based certificate is issued to a different server than the one that you are trying to connect to.
For example, if you have configured Outlook to use https://mail.example.com as the default RPC over HTTP proxy server, but the certificate is issued to a front-end server such as frontend.example.com, the connection is not successful because the client does not recognize the front-end server as a valid server to authenticate with.
To resolve this problem, follow these steps:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
To troubleshoot this problem, use one of the following methods.
Method 1: Use RPCPing.exeNote RPCPing.exe is included with the Windows Server 2003 Resource Kit Tools. To download the resource kit tools, visit the following Microsoft Web site:
http://www.microsoft.com/downloads/details.aspx?FamilyID=9d467a69-57ff-4ae7-96ee-b18c4790cffd&DisplayLang=enTo use RPCPing.exe to identify this problem, follow these steps:
Method 2: Verify the CertificateIf the RPC Proxy computer is also configured to be a Microsoft Outlook Web Access (OWA) server, start Microsoft Internet Explorer and log on to your OWA mailbox. When you log on, use the same server name that you used for your Outlook RPC Proxy. If you receive a message that you do not have access to the RPC Proxy computer, click View Certificate, and then verify that the certificate was issued to the server that you are trying to log on to.