RE: RPC over HTTPS and Outlook 2003

  • From: "Sarbjit Singh Gill" <ssgill@xxxxxxxxxxxxxxxxxxxx>
  • To: "'[ExchangeList]'" <exchangelist@xxxxxxxxxxxxx>
  • Date: Fri, 17 Sep 2004 11:18:00 +0800

But what if rpc and OWA use different authentication mechanisms, how can you
get rpc and OWA configured on the same publishing rule?

/Gill


-----Original Message-----
From: Periyasamy, Raj [mailto:Raj.Periyasamy@xxxxxxxxxxxx] 
Sent: Friday, September 17, 2004 1:25 AM
To: [ExchangeList]
Subject: [exchangelist] RE: RPC over HTTPS and Outlook 2003

http://www.MSExchange.org/

Hi Mustafa,
You don't need 2 different publishing rules for OWA and RPC. Just add the
/rpc* to the OWA publishing and disable the other publishing rule.
Secondly, you don't need an entry in the external DNS for BE server for
configuring profile using RoHTTP Proxy. That is the whole point of using
RoHTTP Proxy. All your RPC requests are encapsulated and delivered to the
RPC Proxy for doing "whatever" and deliver the results "whatever"
back to the client encapsulated in HTTPS. All the client needs is an HTTPS
connection to the FE server either directly or through ISA.Outlook does not
use the forms based authentication that you configure for the listener.
Outlook uses the authentication method configured within your Outlook
profile. This should be set to Basic for RPC over HTTPS.



Regards,

Raj



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

http://www.MSExchange.org/

Hi Raj,
I have created a seperat publishing rule for RPC over HTTPS and added
/rpc/* to path. I removed other paths: /exchange/*, /exchweb/*, /public/*.

It is interesting to know for me:
I used the same listener in RPC over HTTPS publishing like in OWA
publishing. It menas that the Listener has the authentication Forma-based
authentication. But I tried both form-based and standard authentication for
RPC over HTTPS. It didn't help me.

To your previous mail:
I didn't have the record of EXchange back-end server in the external DNS.
THat is also not my wish. I want o protect back-end from hackers.
Because
of that I have twio Firewalls and ISA 2004 in Lab. Only ISA external IP
address should be connected by extern clients. THen, you know, ISA will
forwar (SSL bridging) traffic to front-end.

I tested your suggestion before. If I have the back-end in the DNS list and
type back-end Exchange in Exchange Server field, I can connect me over RPC
over HTTPS.

Best Regrads
Mustafa 

------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp
Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ
------------------------------------------------------
Other Internet Software Marketing Sites:
World of Windows Networking: http://www.windowsnetworking.com Leading
Network Software Directory: http://www.serverfiles.com
No.1 ISA Server Resource Site: http://www.isaserver.org Windows Security
Resource Site: http://www.windowsecurity.com/ Network Security Library:
http://www.secinf.net/ Windows 2000/NT Fax Solutions:
http://www.ntfaxfaq.com
------------------------------------------------------
You are currently subscribed to this MSEXchange.org Discussion List as:
psraj@xxxxxxxxxxxx
To unsubscribe visit
http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Report abuse to listadmin@xxxxxxxxxxxxxx



------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp
Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ
------------------------------------------------------
Other Internet Software Marketing Sites:
World of Windows Networking: http://www.windowsnetworking.com Leading
Network Software Directory: http://www.serverfiles.com
No.1 ISA Server Resource Site: http://www.isaserver.org Windows Security
Resource Site: http://www.windowsecurity.com/ Network Security Library:
http://www.secinf.net/ Windows 2000/NT Fax Solutions:
http://www.ntfaxfaq.com
------------------------------------------------------
You are currently subscribed to this MSEXchange.org Discussion List as:
ssgill@xxxxxxxxxxxxxxxxxxxx To unsubscribe visit
http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Report abuse to listadmin@xxxxxxxxxxxxxx



Other related posts: