I am trying to get RPC over HTTPS to work with my Exchange 2003 server. As you can guess without much success. I have gotten a certificate and am able to connect to Outlook Web Access just fine (using HTTPS), without a certificate error. So I am assuming that my firewall ports are setup properly. I have checked and the RPC services are running on the server. The directory in IIS seems to be ok also. I am connecting using basic authentication. Outlook tries to connect and then just disconnects when using RPC over HTTPS. I have run Outlook with the rpcdiag switch, and here is where I think the problem might lie. It shows Outlook trying to connect to myserver.local, which is the Exchange server name that clients resolve when they are being used within the network. Wheras my certificate is myserver.com. Is there a detail in my setup that I am missing? Hope I have given enough info to describe the problem. Let me know if there is anything else about the problem that I should post. I do truly appreciate any help on this! PS--> I am not using a front end server.

You must configure your outlook client to connect to your myserver.com instead of the myserver.local on the client profile You did configure your client to connect to your exchange server via HTTP in the profile settings? Outlook profile -More Settings - Connection Select Connect to Exchange using HTTP and Configure Exchange Proxy settings Type myserver.com in the Exchange Proxy URL Deli

So you are saying that when I create the Microsoft Exchange account, that I need to use the https name of the server that is on the Internet? I tried that with the PC connected to the LAN, and it still resolves the Exchange server name as myserver.local. Yes---I did enable the settings to connect my Exchange mailbox via HTTP. The information entered in the https area is: www. myserver.com. This is the name that the security certificate is issued in. When I do Outlook /rpcdiag, it shows Outlook trying to connect to myserver.local.

It is normal that you see outlook connecting to the internal server name. If you use only one server (no front-end back-end scenario) you should make some changes to the registry to forward requests in your rpc proxy Check this article http://www.petri.co.il/configure_rpc_over_https_on_a_single_server.htm Deli