I have a server running SBS 2003 with Exchange Server 2003 latest service packs. I have several remote users and would like to move them from imap to full exchange syncing. The problem I'm having is that I can't get my outlook 2003 clients to connect to the server when over the internet. RPC works great on the internal network but once I leave the net it all falls apart. I've run through just about every tutorial and walkthough I can but nothing has worked. The error I'm getting is:Task 'Microsoft Exchange Server' reported error (0x80040115) : 'The connection to the Microsoft Exchange Server is unavailable. Outlook must be online or connected to complete this action.'I can connect to OWA fine but RPC refuses to work.

Hi, The error 0x80040115 means MAPI_E_NETWORK_ERROR. I suggest that we attempt the following method to troubleshoot the issue: Please firstly configure a client (not join domain) to connect to your RPC Proxy Server (Front-End Server) directly and set the Outlook Profile to connect to the Server through RPC over Http. Please check whether client can connect to RPC Proxy Server successfully and whether the issue 0x80040115 still persists. Note: Please ensure that the connection type is HTTPS. You can check On fast networks, connect using HTTP first, then connect using TCP/IP for testing. If the local client can connect to RPC Proxy Server through RPC over Http successfully, please check the following settings: 1. Remote User profile are configured correctly (I suggest that you configure the Basic Authentication method to troubleshoot the issue) 2. Ensure the SSL certificate from a trusted certification authority (CA). If you used an in house CA to create a self singed certificate, you will need to add the CA to the list of trusted CAs on the server and all clients. 3. Check the firewall setting between the remote client and RPC Proxy Server 4. Please ensure that the remote client is able to resolve the DNS name of the RPC Proxy server If the local client encountered the error 0x80040115 either, please check the local server setting: 1. The correct ports are configured on the Back-End server 2. The correct authentication methods are configured on the Web Sites | Default Web Site | RPC. I suggest that you use Basic Authentication for testing purpose. For your reference: Troubleshoot RPC over HTTP communications: http://technet.microsoft.com/en-us/library/bb124649.aspx http://www.msexchange.org/tutorials/Troubleshooting-RPC-over-HTTPS-Part1.html http://www.msexchange.org/tutorials/Troubleshooting-RPC-over-HTTPS-Part2.html Mike

Mike,I'm not totally sure what you mean with these instructions. I only have a single exchange server I'm not using a front-end/back-end setup. I know I can resolve the IP address of the server because I can remote login for OWA. I'm still getting error: Task 'Microsoft Exchange Server' reported error (0x8004011D) : 'The server is not available. Contact your administrator if this condition persists.'I don't know what I'm doing wrong as I checked all my ports are open and I can resolve the address of my server.

Hi, Please understand that the error code 0x8004011D is a general error. After making some research, I have concluded some possible causes. Hope it is helpful 1. Client time is incorrect and cannot sync with the Exchange Server http://www.pcreview.co.uk/forums/thread-2442197.php 2. The HKLM\SOFTWARE\Microsoft\Rpc\Rpcproxy ValidPorts key is incorrect. Regarding the issue, you should be able to get a Event 2 in the Application Event regarding RPC Proxy http://forums.msexchange.org/m_140039400/mpage_1/key_/tm.htm#1800403357 3. Certificate issue: http://www.chicagotech.net/exchange/rpcoverhttp1.htm Mike

The problem was with my certificates. Once I manually installed the certificate into the physical local computer, trusted store it worked like a charm. Thanks for all your help and research with this problem.