RPC over HTTPS Question
Posted on 2007-11-15
I'm having a problem setting up RPC over HTTPS for a client. Here's the rundown:
Windows Server Ent. Edition 2003 SP2 - single server environment.
Exchange 2003 SP2
CA Trusted from GoDaddy
Client using Outlook 2007
I have uninstalled and reinstalled the RPC proxy. I have applied a CA from GoDaddy and tested it. I have used rpccfg to check the proxy ports. I have tested internally and externally, and it continues to fail to connect. I have used rpcdiag to test it.
I have checked the IIS VD's and they are as follows:
Default Web Site - Requires SSL, Anonymous only checked
Exadmin - SSL not required, Integrated and Basic checked. Default domain is domain.local
Exchange - Requires SSL, Integrated and Basic checked. Default domain is domain.local
ExchWeb - Requires SSL, Anonymous, Integrated, and Basic checked. Default domain is domain.local
Public - Requires SSL, Integrated and Basic checked. Default domain is domain.local
RPC - Requires SSL, Integrated and Basic checked. Default domain is domain.local
I have browsed from outside the network to https://mail.domain.com/rpc and gotten the 401.3 error, which is expected. Rpcdiag shows the server name and Directory attempting to connect, then it fails. The cert is the same as the external domain name. The ncan registry entry is visible. The RPC tab in ESM shows "Not part of an Exchange managed RPC topology". Port 443 is forwarded properly as well.