Hi,
We're experiencing a strange problem when connecting to OWA/ECP.
Since a week or two, we get a popup for credentials when logging onto
https://mail.customer.com/owa.
When the credentials are filled in the first time, we keep receiving the popup, and can't get through.
We're using integrated authentication internally.
When connecting externally, we get a popup from a non domain-joined pc, but get passed correctly to owa and ECP.
We're using a load balancer that uses mail.customer.com, and distributes it over the 3 exchange servers.
When connecting directly to each exchange server, we get a certificate warning (which is logic), but after confirming we get passed to ecp or owa correctly.
Works :
https://exchangeserver1.customer.com/owa (after receiving certificate warning)
https://exchangeserver2.customer.com/owa (after receiving certificate warning)
https://exchangeserver3.customer.com/owa (after receiving certificate warning)
https://10.10.10.30/owa (after receiving certificate warning) > 10.10.10.30 is the VIP ip address used for loadbalancing
Doesn't work :
https://mail.customer.com/owa
When changing the hosts file, and set mail.customer.com to point directly to one of the exchange servers, it doesn't work either.
PS :
So mail.customer.com gets forwarded to the VIP ip address.
We don't experience any problems with outlook.