• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 543
  • Last Modified:

rpc over https singel exchange srv sp2.

Hi pros.

Need some help with this,

Our domain got one Exchange2k3srv,one dc srv, and 3 member srv. No ISA (not my call).

some questions first:

I have read alot of articles about implemet RPC o https, but I got troubble decide the article to follow.

If I only got one Exchage srv, is it classified as a Back-end server ?
On properties on the exchange server object in ESM there is a RPC o https tab, Do I need to change this ?
Do I need do change the registy ?(I have not done that) or is it just for sp1 servers?

What I did so far:

installed rpc proxy on exchange2k3 srv.
installed 3-party ssl serct,configuerd IIS (RPC to use basic auth. ssl 128-bit)
opend firewall to port 443.

Tried the connection according to Microsoft:

Alternatively, you can use the Web browser to locate the Rpcproxy.dll file that is hosted in the RPC virtual directory. To do this, follow these steps:1. On the client computer, start Internet Explorer, type the URL of the Rpcproxy.dll file that is hosted in the RPC virtual directory in the Address list, and then click Go.

For example, type https://mail.contoso.com/rpc/rpcproxy.dll, and then click Go.  
2. When you are prompted for your credentials, type your user name in the UNC format (domain\username), type your password, and then click OK.

You see a blank page in your browser together with a lock icon in the Internet Explorer status bar.

And that Worked!

But when i Use Outlook 2003, It will go so far as want my username/pass.
After that I will get: could not contact exchange server.

what to do?

  • 2
2 Solutions
This is a good step by step article from MS about this


You do need to do some reg entries etc to get this to work, but this article shows you how to do it all on the one server.

The documentation from Microsoft seems to be interpreted by many as indicating that you either need a frontend/backend scenario or an ISA server. You don't need either.
However, Microsoft haven't made it easy for single server user - you need to make some registry changes. These are well documented - on the MS KB, msexchange.org and at my own web site: http://www.amset.info/exchange/rpc-http.asp

You do need to ensure that you meet the requirements of Exchange 2003 on Windows 2003, with a Windows 2003 GC/DC available.

ulfhas4623Author Commented:

I will take a look at the reg settings
ulfhas4623Author Commented:

I had to test a cuple of configurations in the register. beacuse my exchange also were a DC/GC did not configure ports for the dc in the Location: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\RpcProxy. But that did not work, so I configured the ports to my other DC/GC and ti worked great!! (http://www.amset.info/exchange/rpc-http-server.asp)


Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now