Hello!
I have a problem in my test lab environment.
I created a Scale-Out File Server with my two nodes. One is 2012 R2 and other is 2016.
My idea was also to test the new cluster OS rolling upgrade feature.
I managed to get the cluster online and roles working BUT now I made some storage changes and restarted both nodes + DC and now node 2 says following when starting cluster manager and connecting the cluster:
Node is being process of being started:
The remote server has been paused or in the process of being started
Also in event viewer is following:
- DCOM was unable to communicate with the computer node1.test.lab using any of the configured protocols; requested by PID 1360 (C:\Windows\system32\mmc.exe).
- Node 'node1' failed to establish a communication session while joining the cluster. This was due to an authentication failure. Please verify that the nodes are running compatible versions of the cluster service software.
- Cluster node 'node2' failed to join the cluster because it could not communicate over the network with any other node in the cluster. Verify network connectivity and configuration of any network firewalls.
- Cluster failed to start. The latest copy of cluster configuration data was not available within the set of nodes attempting to start the cluster. Changes to the cluster occurred while the set of nodes were not in membership and as a result were not
able to receive configuration data updates. .
Votes required to start cluster: 1
Votes available: 0
Nodes with votes: node1
Guidance:
Attempt to start the cluster service on all nodes in the cluster so that nodes with the latest copy of the cluster configuration data can first form the cluster. The cluster will be able to start and the nodes will automatically obtain the updated cluster configuration data. If there are no nodes available with the latest copy of the cluster configuration data, run the 'Start-ClusterNode -FQ' Windows PowerShell cmdlet. Using the ForceQuorum (FQ) parameter will start the cluster service and mark this node's copy of the cluster configuration data to be authoritative. Forcing quorum on a node with an outdated copy of the cluster database may result in cluster configuration changes that occurred while the node was not participating in the cluster to be lost.
When I open FO Cluster Manager on Node1 I can connect to cluster and it shows my node2 offline but If I try to validate cluster my mmc.exe and therefore Failover cluster manager crashes!
There is same error in node 1 logs:
DCOM was unable to communicate with the computer node2.test.lab using any of the configured protocols; requested by PID 694 (C:\Windows\system32\mmc.exe).
I can communicate the nodes by pinging the IP or hostname.
I tried also file sharing communication by sharing a test folder to see if I can access it from another server.
Result: I can access it by IP: \\10.10.10.51\temp but not by \\node1\temp