How can I
configure RPC over HTTP/S on Exchange
2003 (single server scenario)?
RPC over HTTP/S is a cool
method for connecting your Outlook 2003
client to the corporate Exchange Server
2003 from the Internet or WAN, without
the need to establish a VPN session to
the corporate LAN and/or needing to open
many ports on your corporate firewall.
The only ports you'll need to open on
your firewall are TCP 80 and, if using
SSL, TCP 443.
Note: While RPC
over HTTP does not require SSL, you must
modify the registry to enable RPC over
HTTP if you do not want to use SSL. This
is why I've used the term "RPC over
HTTP/S" in this set of articles.
Basically, there are 2
configurations possible when configuring
RPC over HTTP/S:
-
Multiple servers
- In this scenario, you have
multiple servers in your
organization. These servers are
configured to function as Domain
Controllers, Global Catalog servers,
Exchange front-end servers, Exchange
back-end servers, and RPC proxy
servers. See
Exchange Server 2003 RPC over HTTP
Deployment Scenarios
-
Single server
- In this scenario, you have only
one server that is configured to
function as a Domain Controller, a
Global Catalog, an Exchange
computer, and an RPC proxy server.
This article discusses the
single-server configuration in
detail.
MS KB
833401 has more info, but as always,
I've written an article in order to make
the configuration process easier, as the
original KB tends to be too technical. |