Hello
A client of ours has an Exchange 2013 environment consisting of 2 Server 2012 Standard servers running Exchange 2013 SP1 setup in a failover DAG. The servers are on different sites linked with a fibre connection (different subnets but can see each other
fine).
We've noticed that if we try to access the ECP on the second server via "https://secondserver/ecp/" it brings up the logon page but when we log in with the admin account it redirects us to the account's OWA page.The OWA is reached through the external
name for the firstserver (mail.domain.com) which has an internal DNS entry on the domain to link to the internal IP address (issues with certificate and external dns forced us to do this).
If we log onto the first server via "https://firstserver/ecp/" it brings up the logon page then brings up ECP fine. We can manage both servers from the ECP fine but if the link between the sites go down we can't access the ECP for the second server at all (just get a "page cannot be displayed" as it tries to redirect to the first server external OWA url).
I've checked IIS and there seems to be no redirect in place that we can tell. DNS seems to be fine (no errors) and both servers have different external URL's set for virtual directories. There's NO exchange 2010 server at all - it's purely 2013.
I've also re-created the ECP directory, this had no effect at all.
Running out of ideas so hoping someone can let us know what may be causing this or at least point us int he right direction. The client doesn't want to start replicating the databases until this issue is fixed.
Many thanks in advance for assistance given.
Regards,
Andy
Andy Morton Oriium IT Support MCP, MCTS, MCITP-SA