One NODE of Exchange 2016 not respond

Copper Contributor

Hello everyone. We use Microsoft Exchange 2016 CU23 at the customer. Exchange is installed directly in the user’s domain. Now we have a problem that if one of the domain controllers goes down, suddenly one Exchange node stops communicating. There are three domain controllers in the domain, and it cannot figure out why the implicated node doesn’t switch to another available domain controller.

 

Process is always same
MSExchange ADAccess errors

Process Microsoft.Exchange.Directory.TopologyService.exe (PID=5928). The site monitor API was unable to verify the site name for this Exchange computer. Error Message No suitable domain controller was found in domain xxx

Then MSExchange Submission and FrontEnd Transport and other say the same - Process Could not find any available Domain Controller

Has anyone else encountered a similar issue and found a solution?

 

0 Replies