[isalist] Re: Publishing Exchange 2007 on ISA 2006
- From: Rob Moore <RMoore@xxxxxxxx>
- To: <isalist@xxxxxxxxxxxxx>
- Date: Thu, 6 Nov 2008 13:19:53 -0500
Thanks. I'll be waiting. Meanwhile, I'll answer the other two.
Rob
From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx]
On Behalf Of Ball, Dan
Sent: Thursday, November 06, 2008 11:53 AM
To: 'isalist@xxxxxxxxxxxxx'
Subject: [isalist] Re: Publishing Exchange 2007 on ISA 2006
I had a VERY familiar sounding error last summer when I put Exchange
2007 in (co-existing with a 2003 server)... After a lot of looking at
the ISA server and scratching my head I found the cause of it after
searching for the exact error message in Google. It turned out to be a
permissions error on the Exchange IIS server, and if I recall correctly,
I removed OWA from Exchange and then re-installed it to get it working
correctly.
I'll look and see if I can find the page that described exactly what to
do... If I find it, I'll post it.
From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx]
On Behalf Of Steve Moffat
Sent: Thursday, November 06, 2008 11:25 AM
To: ISA Mailing List
Subject: [isalist] Re: Publishing Exchange 2007 on ISA 2006
And why 3 pub rules if you are using host headers?
S
From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx]
On Behalf Of Jim Harrison
Sent: Thursday, November 06, 2008 12:12 PM
To: ISA Mailing List
Subject: [isalist] Re: Publishing Exchange 2007 on ISA 2006
(sent from Haifa via Istanbul)
"403" isn't enough information to help you.
ISA *always* provides another code that will be between 2 and 5 digit.
What is that other code?
Jim
From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx]
On Behalf Of Rob Moore
Sent: Wednesday, November 05, 2008 8:51 AM
To: isalist@xxxxxxxxxxxxx
Subject: [isalist] Re: Publishing Exchange 2007 on ISA 2006
Our Hub server is also our Client Access server. (We have limited
resources.)
Thanks,
Rob
From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx]
On Behalf Of Thomas W Shinder
Sent: Wednesday, November 05, 2008 11:47 AM
To: isalist@xxxxxxxxxxxxx
Subject: [isalist] Re: Publishing Exchange 2007 on ISA 2006
you need a Client Access Server, not a Hub Transport Server to do this
kind of routing.
____________________________________________
TOM SHINDER | Sr. Consultant/Technical Writer
206.443.1117 | SHINDER@xxxxxxxxxxxxxxx
5701 Sixth Avenue South | Seattle, WA 98108
PROWESS | WWW.PROWESSCORP.COM <http://www.prowesscorp.com/>
____________________________________________
From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx]
On Behalf Of Rob Moore
Sent: Wednesday, November 05, 2008 10:41 AM
To: isalist@xxxxxxxxxxxxx
Subject: [isalist] Publishing Exchange 2007 on ISA 2006
Hello all-
I'm trying to get Exchange 2007 published on my ISA 2006 Standard server
(SP1). For reference I'm using the article at
http://technet.microsoft.com/en-us/library/bb794751.aspx
<http://technet.microsoft.com/en-us/library/bb794751.aspx> .
I've run into a problem. I guess it's some interaction between the
Exchange server and ISA, but I'm not positive, and I'm not sure where to
look. We have to coexist with our existing Exchange 2003 server, so that
complicates things a bit.
Internal OWA DNS points to our Exch07 Hub server. The Hub server then
determines if the client is on our Exch03 server or our Exch07 server,
and it directs them to the appropriate site. That part works fine.
Externally, our OWA DNS points to our ISA server. Exch03 clients get in
just fine. Exch07 clients get the authentication box (we've tried it
with both integrated authentication and with forms authentication).
After correctly entering credentials, we get a 403 Forbidden error
message.
We are currently set up NOT to encrypt traffic between ISA and the Hub
server, but we've also tried it with encrypting that traffic.
What are we missing? Is there a better resource to use for publishing
Exchange 2007 on ISA 2006?
Thanks,
Rob
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Rob Moore
Network Manager
215-241-7870
Help Desk: 800-500-AFSC
Other related posts:
