RPC over HTTPS Configuration

Wacek Ormicki · Joined: 30 Jan 2008 Posts: 3

Hello,

I've a question about RPC over HTTPS Exchange 2003 server configuration:

How to deploy RPC over HTTP for the Exchange Server 2003. We have no
front-end server.
Our back-end server has installed IIS with OWA. This is a member server
only (without Global Catalog services - AD Controller and GC is on
separate machine).
We configured all but Outlook 2003 cannot connect to Exchange from
internet. Within lan all is OK but in /rpcdiag window wee see that Outlook
connect directly to our AD controller via TCP/IP.

Best regards

Thanks

Wacek

--
U¿ywam klienta poczty Opera Mail: http://www.opera.com/mail/

Archived from group: microsoft>public>exchange>connectivity

Lanwench [MVP - Exchange] · Joined: 05 Aug 2007 Posts: 875

Wacek Ormicki wrote:
> Hello,
>
> I've a question about RPC over HTTPS Exchange 2003 server
> configuration:
> How to deploy RPC over HTTP for the Exchange Server 2003. We have no
> front-end server.

OK - that doesn't matter.

> Our back-end server has installed IIS with OWA. This is a member
> server only (without Global Catalog services - AD Controller and GC
> is on separate machine).

That's good, although not relevant here...

> We configured all but Outlook 2003 cannot connect to Exchange from
> internet.

Not sure what "configured all" means, but these may help:

http://www.msexchange.org/tutorials/2003exchangerpc.html
http://www.msexchange.org/tutorials/outlookrpchttp.html
http://www.msexchange.org/tutorials/Configuring-Exchange2003-HTTP-Remote-Access.html
and
http://www.msexchange.org/tutorials/Outlook_2003_Connect_Exchange_2003.html

> Within lan all is OK but in /rpcdiag window wee see that
> Outlook connect directly to our AD controller via TCP/IP.
>
> Best regards
>
> Thanks
>
> Wacek

That's normal on your LAN unless you told outlook to always try HTTPS first,
even on fast connections.

Wacek Ormicki · Joined: 30 Jan 2008 Posts: 3

Lanwench [MVP - Exchange]
wrote: ...

> Not sure what "configured all" means, but these may help:

We configured first Exchg 2003 server according to instruction from
http://www.petri.co.il
(it was exchg server on machine with ad, gc, iis ...)

Next we installed second Exchg 2003 server on member server machine. We
configured access by rpc over https using rpc proxy server on first
server. It works fine.

But we want to deinstall first Exchg server in near future. Then we tried
make a separate second rpc proxy server for second Exchg server.

>
> http://www.msexchange.org/tutorials/2003exchangerpc.html
> http://www.msexchange.org/tutorials/outlookrpchttp.html
> http://www.msexchange.org/tutorials/Configuring-Exchange2003-HTTP-Remote-Access.html
> and
> http://www.msexchange.org/tutorials/Outlook_2003_Connect_Exchange_2003.html

Thanks very much.

>
>> Within lan all is OK but in /rpcdiag window wee see that
>> Outlook connect directly to our AD controller via TCP/IP.
>
> That's normal on your LAN unless you told outlook to always try HTTPS
> first, even on fast connections.

We have checked always try http everywhere. And it is impossible to
connect with GC when we make connection with new rpc proxy server.

But we will study above materials and search the solution.

Best regards,

Wacek Ormicki

Lanwench [MVP - Exchange] · Joined: 05 Aug 2007 Posts: 875

Wacek Ormicki wrote:
> Lanwench [MVP - Exchange]
> wrote: ...
>
>> Not sure what "configured all" means, but these may help:
>
> We configured first Exchg 2003 server according to instruction from
> http://www.petri.co.il
> (it was exchg server on machine with ad, gc, iis ...)
>
> Next we installed second Exchg 2003 server on member server machine.
> We configured access by rpc over https using rpc proxy server on first
> server. It works fine.
>
> But we want to deinstall first Exchg server in near future. Then we
> tried make a separate second rpc proxy server for second Exchg server.

OK - just follow the steps in the KB article -
http://support.microsoft.com/kb/822931
>
>>
>> http://www.msexchange.org/tutorials/2003exchangerpc.html
>> http://www.msexchange.org/tutorials/outlookrpchttp.html
>> http://www.msexchange.org/tutorials/Configuring-Exchange2003-HTTP-Remote-Access.html
>> and
>> http://www.msexchange.org/tutorials/Outlook_2003_Connect_Exchange_2003.html
>
> Thanks very much.
>
>>
>>> Within lan all is OK but in /rpcdiag window wee see that
>>> Outlook connect directly to our AD controller via TCP/IP.
>>
>> That's normal on your LAN unless you told outlook to always try HTTPS
>> first, even on fast connections.
>
> We have checked always try http everywhere. And it is impossible to
> connect with GC when we make connection with new rpc proxy server.
>
> But we will study above materials and search the solution.
>
> Best regards,
>
> Wacek Ormicki

Yet another RPC/HTTPS Problem Hello! I have just managed to our exchange server off the ground and up and running this week. Following lots of tutorials, running into lots of problems along the way, I finally managed to get it delivering mail, receiving mail, OWA working, AD setup, mu

RPC over HTTPS on non-standard port Hi, I'm running my web based Exchange services on a high https port. (e.g. port 8888). Outlook Web Access works fine. Is there a way to setup RPC over HTTPS to use the non-standard https port as well ? It seems that I cannot force Outlook to use a differe

Connection to OWA by HTTPS is very slow. I have a big regular interval when I try to open OWA (Exh2003) by https from outside; at this time other sites opened quickly. It takes around 15 min for IE to open authorization dialog. Is this problem with IE7 or OWA? The OWA Server works fine without o

Urgent! Please Help! Outlook (RPC over HTTPS) connection to Emergency! I have had RPC over HTTPS running on my SBS2003 (SP2) for over 2 years and suddenly since yesterday, laptops and remote machines cannot connect to the Exchange 2003 via RPC-HTTPS! Nothing had changed on the server and nothing in the event logs

Connecting to owa via https://servername/owa/userid not poss Is this technique not possible anymore.. or is there another way to do so? If not, it seems then the only way to access a mailbox, even if you have full rights.. is to do it via then the domain\userid and password routine? Cheers