RPC over HTTP performance and bandwidth considerations
RPC over HTTP is a great way of connecting directly to your exchange server mailbox over the internet. This is in fact the only way I check my email as we have our production servers on an isolated network with a dedicated leased line. So I am never on the corporate network.
I have also been rolling this out for customers with SBS 2003 and Exchange 2003 and it works really well. Below is a collection of articles with regards to deployment and bandwidth requirements.
I’ll be blogging more about this.
Planning Exchange Architecture in a Bandwidth-Sensitive Environment
Performance Considerations When You Configure Exchange Server 2003 for RPC Over HTTPConnections on Low-Bandwith Networks
http://support.microsoft.com/kb/817322/en-us
http://support.microsoft.com/kb/817322/en-us
TechNet Support WebCast: An overview of RPC over HTTP in Microsoft Exchange Server 2003 and Microsoft Office Outlook 2003
http://support.microsoft.com/kb/888812/en-us
http://support.microsoft.com/kb/888812/en-us
Exchange Server 2003 RPC over HTTP Deployment Scenarios
http://www.microsoft.com/technet/prodtechnol/excha...c.mspx http://www.microsoft.com/downloads/details.aspx?fa...ang=en
http://www.microsoft.com/technet/prodtechnol/excha...c.mspx http://www.microsoft.com/downloads/details.aspx?fa...ang=en
Del.icio.us : httpoverrpc, rpc
Michele Says:
September 12th, 2007 at 7:32 pm
I am at wit’s end in setting up RPC over HTTPS for the 3rd time. I have it running on our production Exchange 2003 server. Two Domain controllers are separate computers and are both global catalogs. The production exchanger server is a back-end server (no front end) and has two DNS names. one for webmail and one for the machine name. The certificate is for the webmail and is from our inhouse CA. EVERYTHING WORKS. I’ve duplicated this setup from two years ago, pretty good documentation of everything that needed to be done onto a new Exchange server. We’re planning a migration soon. The certificate is registered to the new server name and during our migration we’ll change it over to webmail certificate. I’m pretty sure the cert is good. My desktop PCs have trusted the root certificate. I’ve gone through Microsoft’s Troubleshooting RPC to the T. This is the problem. It’s working fine from intranet computers on the domain. It is not working for extranet PCs and one computer on the intranet which is not a domain computer. I’ve run rpcping utility and get 12175 errors & 1722 errors trying to connect to the store port. rpcping works though to both servers from my computer on the intranet that is a domain computer. I’ve had Outlook at home configured with RPC over HTTPS on my home computer but I can’t get it configured now going to the new server. If you want the results of my rpcping, I’ll send them to you. I’d like to setup a dialog. I really need help.
kirk lashbrook Says:
October 29th, 2007 at 9:34 am
If your domain computers are working and external are not… it sounds like a certificate issue.
Your external computers would need to trust the certificate you issued from your “inhouse CA”
Or you can obtain a trusted public cert for well under $100.00 that would automatically be trusted on of the external computers as well as all the internals.
I’ve setup RPC over HTTPS using the simple godaddy SSL certs 5 or 6 times and have never had a problem. They are about $20.00 per year. Their intermediate cert was added to microsoft’s list of trusted certs in a windows “root certs” update about a year ago.
Chris Dalby Says:
October 30th, 2007 at 5:59 am
Michele
How you getting on with this? It is possible that communication is not happening between your backend sever and your AD. Didyou config the registry sttings and have you opened ports on your firewall to allow comms between your DMZ etc?
Have you run outlook/ rpcdiag and what sort of connection results do you get? I have a bunch of troubleshooting stuff on this, come back to me if you need help.
Chris Dalby Says:
October 30th, 2007 at 4:14 pm
OK, here is the bookmark to my del.icio.us links on RPC over HTTP. These link sare my troubleshoting bible. You don’t need to look further. All answers reside here:
http://del.icio.us/yellowpark/rpchttp
Read and try and leave a comment.