• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 734
  • Last Modified:

exchange 2003 and 2007 coexistence - OWA redirects to internal IP

I am in the process of migrating mailboxes from a 2003 exchange to a 2007.

so fareverything works fine, mailboxes get copied, mail flows, clients update their info after the move, everything looks ok

my only problem right now is that, when a user whose mailbox is stil on the 2003 server tries the external url https://server.domain.gr/exchange he gets redirected to the internal ip address of the 2003 server, which, of course, won't work outside our LAN.

how do I get OWA 2007 to redirect legacy mailbox users to the public address of the 2003 server?
1 Solution
globotechAuthor Commented:
thanks but it does not really address my problem!

users DO get automatically redirected, but they get redirected to a local address and not a public one. They therefore get an error message since public DNS servers don't have records for our internal FQDNs.
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

globotechAuthor Commented:
well, this one simply states that

# Davex will redirect a request based on the internal (intranet) name of the server. This means that users on the internet may receive a DNS error because the internal name of a server may not be the one that is exposed on the internet.

does that mean that you simply can't make it redirect users to a public IP?

any workarounds?

If you have all the roles (Exchange 2007) on one single server, then the Exchange 2007 server will not redirect any requests to other servers.

Incase your URL (server.domain.gr) is pointing to the Exchange 2007 server then it will not redirect request (https://server.domain.gr/exchange) to an Exchange 2003 server.

To resolve this issue, you will have to install CAS & MBX roles on separate servers.

globotechAuthor Commented:
thank you, that explained everything
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now