OWA Exchange 2007 redirect /exchange to /owa with ISA 2004

Background: We have recently put in a new Windows 2008 Server, Exchange 2007 to replace a Exchange 2003  to Exchange 2003 Server. The schema been updated, the mailboxes moved across and sending and receiving mail.

We still run a ISA 2004 Server to act as the company's firewall.

Issue:
The issue resides around OWA and the redirection of /exchange to /owa, I am not using SSL for owa and have removed these attributes from IIS 7, I can remotely access the website using http://mail.domain.com/owa but if I use http://mail.domain.com/exchange it redirect it to http://mail.domain.local/owa which of course fails from an external IP.

So is the issue around ISA 2004 that 2007 believes it is an internal address and instead of using the external redirect it uses the internal domain, if so is there a work around so that it publishes the external domain.

I have completed the internal and external url fields to be correct, other then this issue owa seems to be operating fine.

Any help will be greatly appreciated
NanosphereAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

aletjollyCommented:
Kindly give me more insight as what is happening as per your below description:
I can remotely access the website using http://mail.domain.com/owa but if I use http://mail.domain.com/exchange it redirect it to http://mail.domain.local/owa which of course fails from an external IP.

Now is http://mail.domain.com/exchange getting redirected to http://mail.domain.com/owa and are you successfully able to login internally or externally.
If this works internally (I mean on the Exchange Server) then it might be the problem with ISA, try including the "/owa" in the OWA publishing rule.
0
NanosphereAuthor Commented:
The redirection is happening for /exchange to /owa, and internally this works fine as the internal domain is used.

But from a external entry point the external domain is substituted for the internal domain in the redirection. It is still trying to redirect it to /owa but exchange still thinks the device is coming from an internal domain, this is my assumption for using the internal domain to pass to the client.

I have done a work around to this issue, although I would like to resolve the issue better, I have using ISA changed the  firewall policy to change any code that pass through the policy from http://mail.domain.local  coverts to  http://mail.domain.com

This means the external domain is given the correct details, not ideal but it works.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
aletjollyCommented:
I appreciate the information that you have shared, but I am not sure with the configurations on ISA so cannot comment on it.
0
AAunspawCommented:
have you found a better resolve to this issue or figure out how to modify the redirect from the local FQDN to the external FQDN?
0
NanosphereAuthor Commented:
Sorry not found any better way to do it. I have to live with the work around thanks guys for all your help now closing this question
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.