Re: Two Questions abt RPC over HTTP

From: Johan Rydin (na_at_na.na)
Date: 12/02/04


Date: Fri, 3 Dec 2004 00:08:45 +0100

1. Try changing authentication method to NTLM (guess you are currently
running basic) in the client connection settings.

2. Didn't catch your scenario completly but RPC over HTTP is configured on
MAPI profile basis (per Exchange Profile). If yout front-end / RPC-proxy is
accessable from the inside you really doesn't have to configure the client
to use "TCP". If the clients can't access the RPC-proxy from the inside you
should be fine by configuring your client to try TCP first.

Best regards,
Johan Rydin

"Bryan Linton" <blinton@nospam.connellinsurance.com> wrote in message
news:uTI7pNOzEHA.3588@TK2MSFTNGP14.phx.gbl...
> 1. I've set up and tested RPC over HTTP on my personal machine, so far
> just
> on the local LAN. It works, but every time I start Outlook I'm prompted
> for
> my login credentials (Domain/username, Password), and it has prompted me a
> few times while Outlook is running. It's not giving me an option to save
> those credentials when I enter them, and I don't want my boss to ever have
> to mess with that. How can I make sure those credentials are always
> passed
> in the background automatically?
>
> 2. We have a remote office staffed by 1 employee, but soon, two employees
> will take turns alternating between that office and our main office. This
> means that (if I impement RPC over HTTP) these two users will alternate
> between connecting to exchange locally and connecting over a WAN link from
> our remote office. Is the setting for RPC over HTTP configured per
> Windows
> profile or per Exchange profile? I'm assuming that for this to work, I
> need
> to either set up two standard profiles on the remote machine and configure
> Outlook in them to use RPC over HTTP, or, I need to join the machine to
> the
> domain so their roaming profiles can follow them to the remote office, and
> configure Outlook in the roaming profiles to try TCP first, then HTTPS.
> This introduces other problems with roaming profiles over slow links, of
> course, because the users *will* need access to their documents, etc...but
> that's beyond the scope of my question here; I'll deal with that
> separately.
> Any guidance welcome on this one.
>
> Thanks in advance,
>
> Bryan
>
>
>
>
>
>



Relevant Pages

  • Re: RPC over HTTP - Sure wish I could get this working again!
    ... Are there any users that are still able to use Outlook with RPC over HTTP to ... remotely are there any event messages showing up on the server at all? ... and created a brand new profile ...
    (microsoft.public.windows.server.sbs)
  • Re: RPC over HTTP Part II
    ... Connection tab> Enable proxy settings? ... Why is it not using RPC over HTTP....Anyone to help please? ... previous profile; should be profile setting as long as no other ... How do i try to connect RPC over HTTP within the LAN? ...
    (microsoft.public.exchange.admin)
  • Re: RPC over HTTP Part II
    ... "MSExchangeStudent" wrote: ... Why is it not using RPC over HTTP....Anyone to help please? ... previous profile; should be profile setting as long as no other ... How do i try to connect RPC over HTTP within the LAN? ...
    (microsoft.public.exchange.admin)
  • Re: Pitfalls with RPC over HTTP(S)
    ... SBS Rocks!!! ... I noticed on another thread that once you enable a client ... > for RPC over HTTP, the client will use that for all communication to the ...
    (microsoft.public.exchange.connectivity)
  • Re: Configure Outlook with RPC over HTTP
    ... If you follow the instructions on how to setup RPC over HTTP found in the ... Outlook will connect using RPC over HTTP and you will not ... > existing Outlook 2003 profile which also happens to be an "Exchange Server ...
    (microsoft.public.windows.server.sbs)