RE: RPC over HTTPS and Outlook 2003

  • From: "Periyasamy, Raj" <Raj.Periyasamy@xxxxxxxxxxxx>
  • To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
  • Date: Tue, 14 Sep 2004 12:06:44 -0400

I forgot to answer the second part of your post. To create the Outlook
profile for RPC over HTTP, you have to be in the LAN. That requires RPC
connectivity. Once you have the profile configured, you can use only
HTTPS to send/receive. That can be seen as a limitation by some, but I
feel it is an added level of security to ensure mailboxes cannot be
downloaded to unauthorized private computers, such as home PCs. This was
seen as a major plus in our company, which is very security focused. 



-----Original Message-----
From: Mustafa Cicek [mailto:mbcicek@xxxxxxxxx] 
Sent: Tuesday, September 14, 2004 12:13 PM
To: [ExchangeList]
Subject: [exchangelist] RE: RPC over HTTPS and Outlook 2003

Hi Raj,

I tested RPC over HTTPS without any problem in internal network.
I tried long before all steps that you listed in your mail. No chance!

I followed also Microsoft Knowledge Base Article - 833401 to configure
over HTTP.
Each time Outlook tries to connect over Port 135, not over HTTP(S). I
in the discussion group that Outlook 2003 need to be in internal network
(Exchange network) to create an outlook profile. If it's true that is
against the Architecture of RPC over HTTP(S)!!!
I am very sure that there is another bug in Outlook 2003 for RPC over
HTTP(S) connections. It is unfortunately also my work to find out this

Best Regards

List Archives:
Exchange Newsletters:
Exchange FAQ:
Other Internet Software Marketing Sites:
World of Windows Networking:
Leading Network Software Directory:
No.1 ISA Server Resource Site:
Windows Security Resource Site:
Network Security Library:
Windows 2000/NT Fax Solutions:
You are currently subscribed to this Discussion List as:
To unsubscribe visit
Report abuse to listadmin@xxxxxxxxxxxxxx

Other related posts: