Trying to setup RPC over HTTP
Posted on 2006-06-05
I am attempting to setup RPC over HTTP, and have questions regarding the correct way to set this up for my scenario.
I am running a Windows Server 2003 computer as the AD/DNS server, and a Windows Server 2003 computer running Exchange 2003 with SP1. The Exchange server is running as a Backend server only (no front end). They are both using private IP's, however, DNS is setup externally (GoDaddy) to point to the internal domain. I other words, outside = mydomain.com, inside = mydomain.local. I have read this should work if you can ping the public hostname of the Exchange server from outside (for example exch.mydomain.com).
I've read that there must be a Global Catalog server available, and the AD serves that purpose.
1.) I am not sure which computer to install the RPC over HTTP proxy service. Should it be on the Exchange server or DC?
2.) I have enabled SSL on the RPC virtual directory. In addition, I set the Authentication to basic and set the default domain to mydomain.local (not sure if that's right, should it be mydomain.com?).
3.) There is a virtual directory named RPCWithCert. Is this the one that is used for SSL, or just the RPC one?
From the client computer, when I open Outlook, but before logging in, I check the connection status and see:
exch.mydomain.com Referral Https Connecting
As soon as I log in, the connection is exclusively TCP/IP. I tried closing all ports but 80 and 443, but then I couldn't connect at all. Nothing shows up in either server's event viewer logs. Basically, I've tried setting this up in several different configurations, and am having no luck. Any help would be appreciated.