I have managed to bork a client's Exchange server and need some help getting things back to normal.
Scenario:
Server: Windows Server 2012 (not R2) (Hyper-V VM)
Exchange: Exchange Server 2013 CU5 Build: 913.22 ( single-server - Mailbox+Client Access )
Problems:
a) Outlook clients cannot connect (just keep prompting for password)
b) EAC and OWA do not work -- login screen appears but gives an error or just hangs after entering credentials
Mail is still flowing through the server, and (interestingly) Windows Phones and iPhones can still connect and send/receive emails (??).
Background:
This all began when I attempted to do two things:
1) add a new SAN certificate (and remove the old one)
2) configure redirection to simplify OWA URL ( mail.domain.com.au instead ofhttps://mail.domain.com.au/owa )
After doing both things, above symptoms appeared and I have so far been unable to find a solution despite several hours of googling and trying every promising lead I could find.
Everything I have done since has been in the areas of Certificates, and IIS website / virtual directory configurations.
Some things I have tried:
- removed the new certificate and reverted to the old one and checked/verifed the service bindings via Exchange Shell -- no joy.
- gone right through all the redirection settings and compared them with another 'good' server and could not find any errors (and the redirection is working as far as the login screen).
- checked the OWA and ECP virtual directory Internal Authentication Methods are set to Basic and Forms (and matched against a working server)
- removed (and subsequently reinstated) the 127.0.0.1 bindings on the Default Web Site that some links I found suggested could be a problem (although they are also present on my working server)
The symptoms suggest to me that the main problem is to do with authentication as everything seems to break at the credentials stage, but I have absolutely no idea how to fix what I have broken.
Is there anyone out there who can give me a hand or some fresh ideas?
Is there a simple way of doing a 'repair' on Exchange 2013? Or fo rebuilding the Exchange website?
Regards,
Gerry Ryan