We've about 20 different customers with Exchange 2013 running, but since Friday we've trouble with an OWA that has worked before (no idea what changed).
The situation is as follows:
On customer site there is an Exchange 2013 Standard on premise installed with all roles on one server. It's a SME with about 25 mailboxes - nothing very complicated or large scaled.
All updates are installed and the current version is
Name AdminDisplayVersion ExchangeVersion
---- ------------------- ---------------
SRVEX01 Version 15.0 (Build 516.32) 0.1 (8.0.535.0)
The server itstelf works fine: ActiveSync, ECP, mailbox and mailtransmission - everything without problem.
However, when accessing OWA (doesn't matter if locally or externally) the OWA redirects the user to the Back End Site (https://internalservername:444/owa
) which isn't available externally and throws a 404 when accessing from the exchange server itself (resource /owa/auth/logon.aspx isn't available on the Back End Site). I've played around with the internal and external hostname of the OWA installation, recreated the OWA virtual directory via shell and ECP - but the problem is still the same.
Does anyone has an idea why the login redirects me to the Back End Site (and port)? The same login works with the ECP like a charm.
The OWA is shown an version 2010, but I think this is just a MS bug, isn't it?
Name Server OwaVersion
---- ------ ----------
owa (Default Web Site) SRVEX01 Exchange2010
Any suggestion is appreciated,