How To: RPC over HTTP

Greetings,

I am trying to setup RPC over HTTP/HTTPS in a test
environment. So far all the directions I have found have
not led me to success. I have several questions.

1. Can it be done with only 1 exchange server, or is a
FE/BE configuration required?
2. Can someone tell me where I went wrong with the
following configuration?


I have a router with a static public IP, it forwards port
25, 80, & 443 to 192.168.0.108. The router does not have
a DMZ port.

.108 is configured as a front end server
.107 is a back end server and thus holds the mailboxes
.105 & .106 are my domain controllers/global catalogs &
CA's

I have tested mail flow and OWA over SSL successfully. I
then create a Outlook profile to connect to Exchange while
on that subnet. I created a second profile to use RPC
over HTTPs setting the Exchange proxy server to
exchange.domain.com. Note that exchange.domain.com
resolves publicly to my IP. I take the PC home and try to
connect using the RPC profile. It doesn't connect.

Mark
Fri Apr 23 09:30:40 CDT 2004

Yes it can be configured with a single server and here is a link that
explains how to do it:
http://support.microsoft.com/default.aspx?scid=kb;en-us;833401

--
Mark Fugatt
Exchange MVP
http://www.exchangetrainer.com
http://www.msexchange.org
"W" <anonymous@discussions.microsoft.com> wrote in message
news:33b701c4293e$b749ba30$a601280a@phx.gbl...
> Greetings,
>
> I am trying to setup RPC over HTTP/HTTPS in a test
> environment. So far all the directions I have found have
> not led me to success. I have several questions.
>
> 1. Can it be done with only 1 exchange server, or is a
> FE/BE configuration required?
> 2. Can someone tell me where I went wrong with the
> following configuration?
>
>
> I have a router with a static public IP, it forwards port
> 25, 80, & 443 to 192.168.0.108. The router does not have
> a DMZ port.
>
> .108 is configured as a front end server
> .107 is a back end server and thus holds the mailboxes
> .105 & .106 are my domain controllers/global catalogs &
> CA's
>
> I have tested mail flow and OWA over SSL successfully. I
> then create a Outlook profile to connect to Exchange while
> on that subnet. I created a second profile to use RPC
> over HTTPs setting the Exchange proxy server to
> exchange.domain.com. Note that exchange.domain.com
> resolves publicly to my IP. I take the PC home and try to
> connect using the RPC profile. It doesn't connect.
>
>
>
>

W
Fri Apr 23 13:13:01 CDT 2004

Thank you for the response. The scenario reference in the
article seems to be for a Exchange server that is also a
Global Catalog.

Would there be any different instructions if the Exchange
Server was just a member server, not a global catalog?

Thanks

>-----Original Message-----
>Yes it can be configured with a single server and here is
a link that
>explains how to do it:
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;833401
>
>--
>Mark Fugatt
>Exchange MVP
>http://www.exchangetrainer.com
>http://www.msexchange.org
>"W" <anonymous@discussions.microsoft.com> wrote in
message
>news:33b701c4293e$b749ba30$a601280a@phx.gbl...
>> Greetings,
>>
>> I am trying to setup RPC over HTTP/HTTPS in a test
>> environment. So far all the directions I have found
have
>> not led me to success. I have several questions.
>>
>> 1. Can it be done with only 1 exchange server, or is a
>> FE/BE configuration required?
>> 2. Can someone tell me where I went wrong with the
>> following configuration?
>>
>>
>> I have a router with a static public IP, it forwards
port
>> 25, 80, & 443 to 192.168.0.108. The router does not
have
>> a DMZ port.
>>
>> .108 is configured as a front end server
>> .107 is a back end server and thus holds the mailboxes
>> .105 & .106 are my domain controllers/global catalogs &
>> CA's
>>
>> I have tested mail flow and OWA over SSL successfully.
I
>> then create a Outlook profile to connect to Exchange
while
>> on that subnet. I created a second profile to use RPC
>> over HTTPs setting the Exchange proxy server to
>> exchange.domain.com. Note that exchange.domain.com
>> resolves publicly to my IP. I take the PC home and try
to
>> connect using the RPC profile. It doesn't connect.
>>
>>
>>
>>
>
>
>.
>