We have some issues brining up our Hyper-V Cluster after a reboot. We might have had an IP address conflict which has now been resolved (another computer was using the same IP as the Hyper-V Cluster IP).
Now we can't seem to bring up the IP address of the cluster - we get the following errors:
Encountered a failure when attempting to create a new NetBIOS interface while bringing resource 'Cluster IP Address' online (error code '1450'). The maximum number of NetBIOS names may have been exceeded.
Cluster resource 'Cluster IP Address' of type 'IP Address' in clustered role 'Cluster Group' failed.
Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it. Check the resource and group state using Failover Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet.
If I right click on the IP address in the Failover Cluster Manager and deselect "Enable NetBIOS for this address" I am able to bring the cluster IP back up and everything seems to work.
I guess there's a reason for why NetBIOS is enabled by default - so my question is: what could be preventing me from activating NetBIOS? This has never been a problem before - as mentioned above I suspect it has something to do with the IP address conflict.
Running Windows Server 2012 R2 Standard. Two identical nodes in a HA cluster.