RPC over HTTP   

Dear all,

I am configuring RPC on HTTP on Exchange 2003. Some question find and want
to ask for help.

Here is the environment:
1 x Exchange back-end resides on the Intranet, RPC-HTTP back-end server has
been selected.
2 x Exchange front-end work as load-balance act as OWA and RPC proxy reside 
on DMZ, RPC-HTTP
front-end server has been selected.
A firewall with 3 interfaces, to Internal network, DMZ and Internet.

For testing purpose, all ports on firewall between front-end and backend is
opened temporarily

When I configure the Outlook client, I got a question, since the Exchange
server field need a FQDN point to the Exchange backend server. So, as the
backend reside on the private intranet, should I 1. register the exchange
backend with a Public access IP, 2 then enable NAT on the firewall and
forward this IP to Exchange Backend (Intranet IP), 3. what is the port
needed to open on this connection. Furthermore, could I use Internal Cert
authority on the front-end or I must install a public Cert on the front-end 
server? Can I use 1 instead of 2 on front-end?

Best,
Andrew

date: Fri, 13 Jun 2008 14:40:31 +0800   author:   Andrew Chan

Re: RPC over HTTP   

Andrew Chan  wrote:
> Dear all,
>
> I am configuring RPC on HTTP on Exchange 2003. Some question find and
> want to ask for help.

Hi - you've posted this as a reply in an existing, old, and unrelated 
thread. You should post all new questions as new messages, so other people 
are more likely to see them.
>
> Here is the environment:
> 1 x Exchange back-end resides on the Intranet, RPC-HTTP back-end
> server has been selected.
> 2 x Exchange front-end work as load-balance act as OWA and RPC proxy
> reside on DMZ, RPC-HTTP
> front-end server has been selected.
> A firewall with 3 interfaces, to Internal network, DMZ and Internet.
>
> For testing purpose, all ports on firewall between front-end and
> backend is opened temporarily
>
> When I configure the Outlook client, I got a question, since the
> Exchange server field need a FQDN point to the Exchange backend
> server. So, as the backend reside on the private intranet, should I
> 1. register the exchange backend with a Public access IP, 2 then
> enable NAT on the firewall and forward this IP to Exchange Backend
> (Intranet IP), 3. what is the port needed to open on this connection.
> Furthermore, could I use Internal Cert authority on the front-end or
> I must install a public Cert on the front-end server? Can I use 1
> instead of 2 on front-end?
> Best,
> Andrew

date: Thu, 3 Jul 2008 09:00:25 -0400   author:   Lanwench [MVP - Exchange]