We have had 2 very weird instances when the Config DC has a network connection interupted, that almost to the second 12 hours later all Exchange Cluster communications stop. We lose connections to EVS and the passive node of A/P cluster service goes into a restarting state. We cannot gain any access to the cluster resources with out a reboot of the Active node, and as soon as it resumes control of the cluster everything is functional again. The only error/warn events are at the exact time the Config DC is unreachable. To me this seems that DSAccess is missing the DC communication event and doesn't move the Config DC connection to a new DC. We have 5 GC and 2 standard DC available for Exchange to talk too. We have only experienced this when a site that contains a DC has a network interuption. A reboot of the DC that holds the Config doesn't affect the cluster other than a brief pause while it moves to a new Config DC. Any ideas? I want to call Support but have no events to provide as backup as there is only the Config DC lost communication event 12 hours before. The EVS runs perfectly until is hits the 12 hour mark then totaly hangs the Cluster. Thanx
