globotech
asked on
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?
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?
ASKER
hi,
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.
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.
ASKER
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?
# 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?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
thank you, that explained everything
here is a link that can help:
http://www.exchangelog.info/2007/05/outlook-web-access-owa-implementation.html