I have a 2-node Windows 2008 cluster that has been working fine for over a year. Recently, we moved the resources from the one node to the other and everything failed. We are able to bring up all of the resources in the Core Cluster Resources (quorum and
cluster IP) online except for the Cluster Name.
The original running node also had some DC connectivity issues that rebooting the DC seemed to resolve. When I check AD, the CNO is there and the objectGUID is the same when viewed through PowerShell on the node and in "Computers and Users" on the
DC. The CNO does have a recent bad-password-time so I wanted to try to "Repair the Active Directory" objects from the Failover Cluster Manager but it is greyed out. The cluster log doesn't show any logon problems and it is able to find the CNO in
the DC but it does say logging in with "secondary password".
Is there a way to manually force a reset of the CNO without going through the Cluster Failover Manager?
Anything else to check?
You can find a sample cluster log when one node is up and the other is down at:
Thanks in advance for any suggestions.