Hi,
We setup an exchange 2013 server and want to have co-existence with our current 2007 server. Small and simple domain setup and no load balances. All roles on single server. The legacy name space was created but does not work externally. We have recreated the certificates on both 2013 and 2007 and both have mail.abc.com and legacy.abc.com in their subject alternate names.
1. Internally : when a user goes to https://mail.abc.com/owa and enter a mailbox which is on exchange 2007, it redirects to https://legacy.abc.com/owa and he is able to get to his mailbox. We have internal DNS A and PTR records and a zone created for this as well.
2. Externally: when a user goes to https://mail.abc.com/owa and enter his username and password, it just stays trying to redirect, the URL stays at https://mail.abc.com/owa/auth.owa
We can ping legacy.abc.com and telnet on port 80 and 443, but if you try and enter it in URL, its not loading. My confusion is :
a) Do we need to create the legacy.abc.com hosted A record externally or reverse record as well (we only have a small firewall which cant be used anything other than NAT)
b) on IIS on Exch 2013, under Default Website and Exchange Back End, owa website, the authentication is different.
Default Website : owa only Basic Authentication is enabled. Whereas under Exchange Back End, anonymous, forms and windows is enabled. On ECP 2013, the owa for 2013 uses form based authentication.
c) on the certificate, we have legacy.abc.com and mail.abc.com on both servers, is this correct configuration?
Since this works internally fine, I am inclined to think it may be a DNS/certificate issue, but any advise is much appreciated.
Regards,
Ramu
Ramu V Ramanan