If I’ve told you once I’ve told you a thousand times… When you build a Failover Cluster on Windows Server make sure you run the Validation Tests… and make sure those tests succeed (or at the very least nothing FAILS… Warnings are acceptable).
So as I sit at a client trying to cluster two Hyper-V Server 2016 hosts, I am frustrated by the big red FAILED on my Cluster Report.
Should you ever encounter this error, it is important to note that the network vEthernet (Data) is not the same network as Data. So the solution, which stymied me for about an hour, was simple:
In other words, I have to disable to TCP/IP v6 on the problematic binding, which I do with a simple PowerShell cmdlet:
PS c:\> Disable-NetAdapterBinding -Name “vEthernet (Data)” -ComponentId ms_tcpip6
(Remember that I have to put the “quotation marks” around the name because there is a space in it… otherwise I could leave them out.)
Also remember that because these hosts are Hyper-V Servers and not actual Windows Servers, I couldn’t use the GUI to do this. (There actually is a netsh command to accomplish this as well… but PowerShell rocks!)
Once I ran this cmdlet on both hosts, I re-ran my Validation Tests, and bingo!
Everything comes up roses, and I can continue my day happily.
I hope this helps you!