Hello,
I was successfully running a two node Windows Failover Cluster of Windows Server 2012 Hyper-V VMs. Now the problem is that Failover Cluster shows Node1 is Up and Node2 is Down.
Cluster Event on Node2 shows the following two errors:
1) "Attempting to use IPv4 for 'Microsoft Failover Cluster Virtual Miniport' network adapter failed. This was due to a failure to disable IPv4 auto-configuration and DHCP. This may be expected if the DHCP Client service is already disabled. IPv6 will be used if enabled, otherwise this node may not be able to participate in a failover cluster. Event ID: 1289 "
2) "The Cluster Service was unable to access network adapter 'Microsoft Failover Cluster Virtual Miniport'.Verify that other network adapters are functioning properly and check the device manager for errors associated with adapter 'Microsoft Failover Cluster Virtual Miniport'. If the configuration for adapter 'Microsoft Failover Cluster Virtual Miniport' has been changed, it may become necessary to reinstall the failover clustering feature on this computer."
On running the Validate Configuration test of this cluster, it throws the error: "Unexpected error while validating File and Print Sharing network binding on node Node2: The server threw an exception."
DHCP Client and Cluster Service, both of these services are running on both nodes. I have also tried restarting both of these services on Node2. Then I manually removed and reinstalled the network adapter from Device Manager on Node2. Then tried rebooting the Node2. The issue is still unresolved.
Node1 and Node2 are able to Ping each other. We are using Static IP addressing for all servers.
Please help and advice.
Thank you.
~ Hasan Bin Hasib