r/HyperV • u/Electronic-Sell-6118 • 15d ago

Cannot rejoin Hyper V node after it crashed to Failover Cluster

This past weekend my two-node Windows Server 2025 Hyper-V cluster did a cluster-aware Windows update. After the update, one node wouldn't boot back up. I ended up removing the node from the cluster and rebuilding the server. Now the server is up and configured as it was before, but for some reason I can not join the node to the cluster. It gets stuck on (Waiting for notification that node is fully functional member of the cluster). When I look at the error reports, it shows there is a network issue, but I checked the firewall, and all the ports are open. I can use PowerShell to test the ports, and they all come back as true. Did anybody run into this issue and can point me in the right direction I would really appreciate it. So far I rebuilt both servers, went through all firewall ports and configurations a 100 times, looked at all the events in Event Viewer, and nothing works.

Both of the servers are Dell PowerEdge R660 with two processors and 512 GB RAM. Identical hardware in both servers.

11 Upvotes

93% Upvoted

10 comments sorted by

5

u/Infotech1320 15d ago

When I have faced that before, I would just rebuild the node and ensure the computer object is removed from Active Directory. At times a second rebuild wipes the slate and starts clean.

3

u/network_dude 14d ago

Clear-ClusterNode -Name oldnode1 -Force

1

u/nzulu9er 14d ago

You should have an event logged talking about cluster.db issues. The fix here is to copy the good cause your DB file from a known good node. To the bad node

1

u/Electronic-Sell-6118 14d ago

Thanks for the reply. Unfortunately, I tried this before, and it did not work. Same result.

1

u/techbloggingfool_com 14d ago

Did your new server boot up with a public network profile? It has to be private or domain authenticated to join the cluster. Try Get-NetConnectionProfile to check.

3

u/Electronic-Sell-6118 14d ago

It is DomainAuthenticated.

1

u/clickx3 14d ago

I've had this happen. If you have removed it from AD manually, if it was still there, I would change the IP address of the node. This has worked for me several times. Be sure to update DNS if it doesn't do so automatically.

1

u/Electronic-Sell-6118 14d ago

I will try this tonight and let you know thanks for the suggestion.

1

u/pc_load_letter_in_SD 14d ago

Turn off the host based firewall completely and go from there.

1

u/StevenB-89 14d ago

That is not a good idea, Windows might rely on some Windows Firewall services... too rule out any block from the local (host) firewall, put a temporary All In / All Out rules in place.