Cluster Network Stuck in 'Already Online' — 0X000013C7 Fix

When This Error Shows Up

You're in Failover Cluster Manager, right-click a cluster network (like the heartbeat or public network), select 'Bring Online', and instead of it going green, you get this message: ERROR_CLUSTER_NETWORK_ALREADY_ONLINE (0X000013C7). The network already shows 'Online' in the state column, but something's off — maybe it's not passing traffic, or you just rebuilt the cluster and the state cache is stale. I've seen this mostly on Windows Server 2016 and 2019 clusters after a reboot or a node eviction.

Root Cause

The cluster service keeps a cached state for each network object. When the state in memory says 'Online' but the underlying network adapter is disconnected or the DNS registration failed, the cluster won't let you force a state change — it thinks it's already done. The culprit here is almost always a race condition during cluster startup or a leftover state from a failed node removal. Don't bother restarting the Cluster service on all nodes — that rarely helps and takes everything down.

Fix It in 2 Steps

Skip the GUI for this one. The real fix is to clear the cached state via PowerShell. Here's what you do:

Step 1: Identify the Stuck Network

Run this command on any node with admin rights:

Get-ClusterNetwork | Format-Table Name, State

Look for the network that's showing 'Online' but shouldn't be — maybe it's a public network that lost its uplink, or a heartbeat network with a dead NIC. Note its exact name.

Step 2: Force the State Change

Use this PowerShell command to clear the stuck state. Replace YourNetworkName with the actual name:

Get-ClusterNetwork "YourNetworkName" | Set-ClusterParameter -Name "State" -Value 1
Start-Sleep -Seconds 5
Get-ClusterNetwork "YourNetworkName" | Start-ClusterNetwork

What this does: it forces the state to 'Offline' (value 1) behind the scenes, waits a few seconds for the cluster to process it, then tells it to come online fresh. You'll see the state flicker to 'Offline' then back to 'Online' in the GUI.

If That Doesn't Work

Sometimes the network adapter itself is the problem. Check three things:

1. Physical connectivity — is the cable plugged in? Is the switch port up? Check event logs for network adapter warnings.
2. DNS registration — cluster networks need DNS to work. Run ipconfig /registerdns on each node for that adapter.
3. Cluster validation — run a validation report focused on network settings. Look for mismatched MTU or IPv4/IPv6 settings between nodes.

If the network is still stuck after the fix, you might have a corrupted cluster database. I've only seen that twice in 14 years, but when it happens, you'll need to evict and re-add the node. Save yourself the headache — check the event viewer for Cluster Networks errors (source: Microsoft-Windows-FailoverClustering).

Bottom line: this error is a state cache issue, not a real problem. The PowerShell trick fixes it 9 times out of 10. If not, go check the hardware.