• It could be that the IP cluster resource is unable to determine which node of the cluster is the owner of the group. I'm not a Windows cluster administrator so I don't know how to resolve this nicely. When that happened we just rebooted one of the (2-node) cluster nodes.

    Perheps it can be solved if you delete and re-create the IP-resource?

    ** Don't mistake the ‘stupidity of the crowd’ for the ‘wisdom of the group’! **