Friends, good afternoon.
I'm doing a lab with Exchange 2016 in coexistence with Exchange 2010.
My scenario is as follows:
- SERVERDC (10.10.0.10)
- Windows 2012 R2
- CA Internal
- SERVEREXC01 (10.10.0.11)
- Exchange 2010 SP3 UR11
- SERVEREXC02 (10.10.0.13)
- Exchange 2016 / Database DAG: Lab2-Lab3 / Primary: SERVEREXC02
- User 2 in Database: Lab2
- SERVEREXC03 (10.10.0.14)
- Exchange 2016 / Database DAG: Lab3-Lab2 / Primary: SERVEREXC02
- User 3 in Database: LAB3
- SERVEREXC04 (10.10.0.18)
- Exchange 2016 / Database: Lab4
- User 4 in Database: Lab4
Before changing InternalURL settings for a single FQDN and change certificates, Microsoft Outlook is connected perfectly with certificate error, but it worked.
After several problems with certificates deleted certificates and created new self-signed I returned the InternalURL to the FQDN of each serverexc02 and 03.
I installed a new SERVEREXC04 new server without having changed nothing and created an account in AD called User4.
To my surprise all users, including the new (User4) which is in SERVEREX04, which I did not do anything, also does not connect in Microsoft Outlook.
Looking at the conexções with (-ano netstat), I realize that Microsoft Outlook when you do the autodiscovery, he always tries first of SERVEREX01, then the 02, then 03 and the last on 04.
The problem is when he finds SERVEREXC04, it returns to the SERVEEXC03 and generates an error in Microsoft Outlook.
NOTE: The servers 01,02,03 are down at the time of testing. But the problem happens to them online too.
What I have to check to find the problem?
Thank you.