Re: RPC Over HTTP Security

From: Greg Mansius [MSFT] (gregmans_at_online.microsoft.com)
Date: 02/25/04 

Date: Wed, 25 Feb 2004 18:04:50 -0500

Todd,

Please also see the following KB article on how to see this all up.

833401 How to configure RPC over HTTP in Exchange Server 2003
http://support.microsoft.com/?id=833401

Thanks, 

-- 
Greg Mansius [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights
"Michael Palermiti [MSFT]" <michaelp@online.microsoft.com> wrote in message
news:OkemfO1%23DHA.1732@TK2MSFTNGP12.phx.gbl...
> With RPC over HTTP users can have security-enhanced access to their
Exchange
> Server accounts from the Internet when they are working outside your
> organization's firewall. This is accomplished because RPC over HTTP
actually
> requires a secure HTTPS connection to the proxy server, therefore the
> transmission of data is encrypted.  Users do not need any special
> connections or hardware, such as smart cards and security tokens, and they
> can still get to their Exchange accounts even if the Exchange server and
> client computer behind the firewall are on different networks.
> RPC over HTTP works by having an Exchange Server front-end computer
> configured as an RPC proxy server. This RPC proxy server then specifies
> which ports to use to communicate with the network's domain controller,
> global catalog (GC) servers, and all Exchange servers that the client user
> requires. The Exchange group in your organization must first deploy RPC
over
> HTTP for the Exchange servers you use, and then you can configure user
> accounts that access those Exchange servers to use RPC over HTTP.
>
> Check out the "Exchange Server 2003 RPC over HTTP Deployment Scenarios"
> guide at
>
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/exchange/Exchange2003/proddocs/library/ex2k3rpc.asp
>
> ---------------------------------
> Michael Palermiti
> Enterprise Messaging Support
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> © 2004 Microsoft Corporation. All rights reserved.
>
>
> "Todd" <toddm@rahul.net> wrote in message
> news:%23gZQuM0%23DHA.2348@TK2MSFTNGP09.phx.gbl...
> > When using RPC over HTTP, is data automatically encrypted, or do I need
to
> > select the "encrypt" option on the security page in the Outlook email
> > account setup?  What kind of encryption is used?  Is it an acceptable
> > replacement for VPN?
> >
> >
>
>

Relevant Pages

  • RE: RPC over HTTP troubleshooting
    ... When we connect to the server through RPC over HTTPS, ... HTTP Error 401.3 - Unauthorized: Access is denied due to an ACL set on the ... 833401 How to configure RPC over HTTP on a single server in Exchange Server ...
    (microsoft.public.exchange.connectivity)
  • RE: RPCPING error 12007
    ... Mailbox definately exists. ... Confirmed that RPC Proxy is using default ports, ... I can NOT access OWA via HTTPS but I can via HTTP. ... > You are unable to use RPC over HTTP to connect to the Exchange Server. ...
    (microsoft.public.exchange.connectivity)
  • Re: Exchange, Outlook and DNS problem
    ... > Company deceided to switch from ISP POP3 to local Exchange server. ... > Cisco routes to local ISA IP address.ISA is configured to do RPC over ... > HTTP routing for Exchange which is also located in internal network. ... > Outlook while connected internal network. ...
    (microsoft.public.win2000.dns)
  • Re: RPC over HTTPS woes
    ... I have gone over just about every article in my attempt to set up RPC ... on the on the exchange server: ... directory tab> application name rpc> execute permissions: ... Outside the the network, i receive the logon but never connects, ...
    (microsoft.public.exchange.admin)
  • RE: RPCPING error 12007
    ... You are unable to use RPC over HTTP to connect to the Exchange Server. ... Microsoft Online Partner Support ...
    (microsoft.public.exchange.connectivity)