Re: RPC over HTTPs works, but...

  • From: Sudeep Raikar <raikar.sudeep@xxxxxxxxx>
  • To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
  • Date: Tue, 22 Nov 2005 22:04:48 +0900

I ddon't think that Putting that name is a Requirement in For outlook.
 Please let us know what is the Operation Service Pack Level on your
Exchange Server. IS it that only the Remote Clients facing the problem then
it is surely with the Service Pack. I think this is a known issue if the
Service Pack2 for Remote Clients.
 Please download the latest Servie pack and install that. That should Solve
your problem.

 On 11/22/05, Chris Wall <Chris.Wall@xxxxxxxxxxxxxxxxxxx> wrote:
> <>
> Hello all,
> I have RPC over HTTPs running great everywhere for our users, except users
> in Venezuela.
> I have tested the config with 2 users in our Venezuela offices however
> they are unable to connect when attempting RPC over HTTPs. If I try the
> configs here in the US with their profiles, everything works great. I have
> verified that both users have fully patched Office 2003 installs and both
> are running XP with SP2 for the OS. Also, our cert is through an accepted
> publisher, so there are no issues with the certificate.
>  The only thing that I can think of is the language of their OS is in
> Spanish. Although most of the RPC config is selecting Radio buttons and
> Check boxes, I am concerned about the entry under Exchange Proxy Settings.
> In the US, I have our users specify the 'principal name of the proxy
> server:' as ''. Does anyone know if the
> language will affect the 'MSSTD' specification or what else could be
> preventing these users from successfully connecting via RPC?
>   Thanks for any ideas…
> Chris
> ------------------------------------------------------
> List Archives:
> Exchange Newsletters:
> ------------------------------------------------------
> Visit for more information about our other sites:
> ------------------------------------------------------
> You are currently subscribed to this Discussion List as:
> raikar.sudeep@xxxxxxxxx
> To unsubscribe visit
> Report abuse to listadmin@xxxxxxxxxxxxxx

Other related posts: