Re: RPC over HTTP for OWA
- From: "Colin M. McGroarty" <CMcGroarty@xxxxxxxxxxx>
- Date: Mon, 15 Aug 2005 17:40:29 -0500
Vitaly,
Setting up RPC over HTTPS is actually pretty easy and straight forward. You
can also configure the clients to look for a TCP/IP connection before an RPC
over HTTPS connection. This allows users to work as normal when they are
in-house.
Kind Regards,
--
Colin M. McGroarty, MCSE, MCP+I, NT-CIP
2004 Microsoft MVP, Windows Server - General
www.McGroarty.org
"Vitaly Markovsky" <VitalyMarkovsky@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:E7FA48D4-F687-4C42-86F3-91C59C8C2DCF@xxxxxxxxxxxxxxxx
Hey guys and gals,
Since we have internmittent issues with logging in periodically with our
current FE/BE setup in Exchange 2003 (every 8 or 10 logins or so, the
owaauth.dll screen just sits until timeout. Clicking refresh gets you in,
but
this behavior is unacceptable to our CEO) I an thinking about setting up RPC
over HTTP to see if that may correct the problem.
The potential issue: after reading up on the procedure, there is a statement
that says how to configure Outlook to use RPC over HTTP. I assume this is an
optional step, right? I want to make sure that our LAN can access Exchange
normally via Outlook, not via RPC/HTTP.
Is this true? The reason I say this is b/c we will likely use RSA tokens for
authentication and I will hear no end of hardship if users on the LAN have
to
use their tokens for email.
Thanks in advance as usual!
.
- References:
- RPC over HTTP for OWA
- From: Vitaly Markovsky
- RPC over HTTP for OWA
- Prev by Date: Re: proper dns listings for mail servers
- Next by Date: Re: Exchange SMTP holding tank?
- Previous by thread: RPC over HTTP for OWA
- Next by thread: Collaboration with outside users
- Index(es):
Relevant Pages
|