Comments on: RPC over HTTP performance and bandwidth considerations http://blogs.msexchange.org/dalby/2006/06/12/rpc-over-http-performance-and-bandwidth-considerations/ Chris Dalby's blog focuses on Microsoft Exchange Server and the interaction and integration of Exchange Server within Windows, mixed networks, and mobile networks. The blog also includes tips and tweaks for Exchange Server within Small Business Server, both SBS 2000 and SBS 2003. It also reviews various Exchange tools and utilities plus Exchange scripts and codes for managing an Exchange enterprise Sun, 14 Mar 2010 08:50:34 +0000 http://wordpress.org/?v=MU by: thamil http://blogs.msexchange.org/dalby/2006/06/12/rpc-over-http-performance-and-bandwidth-considerations/#comment-27775 Sun, 09 Aug 2009 10:51:50 +0000 http://blogs.msexchange.org/dalby/2006/06/12/rpc-over-http-performance-and-bandwidth-considerations/#comment-27775 hi hi

]]> by: Chris Dalby http://blogs.msexchange.org/dalby/2006/06/12/rpc-over-http-performance-and-bandwidth-considerations/#comment-12112 Tue, 30 Oct 2007 21:14:21 +0000 http://blogs.msexchange.org/dalby/2006/06/12/rpc-over-http-performance-and-bandwidth-considerations/#comment-12112 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. 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.

]]> by: Chris Dalby http://blogs.msexchange.org/dalby/2006/06/12/rpc-over-http-performance-and-bandwidth-considerations/#comment-12110 Tue, 30 Oct 2007 10:59:55 +0000 http://blogs.msexchange.org/dalby/2006/06/12/rpc-over-http-performance-and-bandwidth-considerations/#comment-12110 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. 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.

]]> by: kirk lashbrook http://blogs.msexchange.org/dalby/2006/06/12/rpc-over-http-performance-and-bandwidth-considerations/#comment-12094 Mon, 29 Oct 2007 14:34:48 +0000 http://blogs.msexchange.org/dalby/2006/06/12/rpc-over-http-performance-and-bandwidth-considerations/#comment-12094 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. 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.

]]> by: Michele http://blogs.msexchange.org/dalby/2006/06/12/rpc-over-http-performance-and-bandwidth-considerations/#comment-10455 Thu, 13 Sep 2007 00:32:56 +0000 http://blogs.msexchange.org/dalby/2006/06/12/rpc-over-http-performance-and-bandwidth-considerations/#comment-10455 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. 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.

]]>