Exchange 2016 – ClusterNetwork Current State is ‘Partitioned’

We receive a case from client saying that it show the following error message when they run “Test-ReplicationHealth” in their Exchange 2016 Server

We tried to ping the IP Address of both Exchange 2016 Servers, and obviously the IP is reachable and Exchange 2016 Servers are running fine without any issue

However, it return the DAG IP Address instead of the Production IP Address when we tried to ping the hostname & FQDN and we suspected that this might due to the Network Binding issue

Please refer to the PowerShell below to modify the Network Binding in Windows 2016

  1. Check the InterfaceAlias Name for Network Connection with IPv4 only
Get-NetIPInterface -AddressFamily IPv4
  1. Set the InterfaceMetric to the lowest number for “Production LAN”
Set-NetIPInterface -InterfaceAlias "Production LAN" -InterfaceMetric 1  
Set-NetIPInterface -InterfaceAlias "DAG LAN" -InterfaceMetric 2
  1. Production IP Address should be return when you try to ping the hostname & FQDN of both Exchange 2016 Server again
  2. However, the error message is still there until we restarted 1 of the Exchange 2016 Server
  3. Run “Test-ReplicationHealth” again, and all the tests should show PASSED now

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top