RE: Publish OWA and RPC over HTTP through ISA?

  • From: "Thomas W Shinder" <tshinder@xxxxxxxxxxx>
  • To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx>
  • Date: Thu, 28 Oct 2004 06:50:52 -0500

Hi Jason,
 
Kai Wilke and I did an article on how to solve this problem over at
www.isaserver.org several months ago.
 
HTH,
 
Tom
www.isaserver.org/shinder <http://www.isaserver.org/shinder> 
Tom and Deb Shinder's Configuring ISA Server 2004
http://tinyurl.com/3xqb7 <http://tinyurl.com/3xqb7> 
MVP -- ISA Firewalls

 

________________________________

From: Jason Merrique [mailto:j.merrique@xxxxxxxxxxxxxxx] 
Sent: Thursday, October 28, 2004 6:33 AM
To: [ISAserver.org Discussion List]
Subject: [isalist] Publish OWA and RPC over HTTP through ISA?


http://www.ISAserver.org

Hi Chaps,
 
Is it possible to publish OWA with FBA enabled and RPC over HTTP on ISA
2004? The problem seems to be with the weblistener.....they can't both
use it if OWA requires FBA, and they can't each have a separate one as
the ISA server only has one external IP. 
 
Any ideas?
 
Cheers,
 
Jason
------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=isalist
ISA Server Newsletter: http://www.isaserver.org/pages/newsletter.asp
ISA Server FAQ: http://www.isaserver.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 Exchange Server Resource Site: http://www.msexchange.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 ISAserver.org Discussion List as:
tshinder@xxxxxxxxxxxxxxxxxx
To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=isalist
Report abuse to listadmin@xxxxxxxxxxxxx 

Other related posts: