cluster problem server 2022

Question

I tried to create a cluster using Windows Server 2022, but I am facing the following problem

: finding a suitable controller for the node. The specified server cannot perform the requested operation, Windows Server 2022

Answer 1

Hello AHMED SULIMAN MEKAEIL ESTANBOOL,

The error about “finding a suitable controller for the node” in Windows Server 2022 usually points to prerequisites not being fully met before creating the cluster. Common causes include missing roles/features, misconfigured domain membership, or storage not being properly recognized by the Failover Cluster Manager.

First, please confirm that the Failover Clustering feature is installed on all nodes and that each server is joined to the same Active Directory domain. Next, run the Cluster Validation Wizard in Failover Cluster Manager, this tool will highlight any networking, storage, or configuration issues that prevent the node from being accepted. Also, check that your storage is shared and accessible to all nodes, as clustering requires consistent disk visibility.

If you are using SMB or iSCSI storage, verify that the connections are stable and that permissions are correctly set. In some cases, outdated drivers or firmware for storage controllers can cause the “specified server cannot perform the requested operation” error, so updating those components is recommended.

I hope the response provided some helpful insight. If you find this answer useful, please hit “accept answer” so I know it addressed your concern.

Jason.

Answer 2

The error "The specified server cannot perform the requested operation" when creating a Windows Server 2022 failover cluster typically indicates a problem reaching a domain controller (DC) or primary domain controller (PDC), or a general directory/namespace query failure.

Use the following checks and fixes:

1. Verify failover cluster prerequisites

• All servers that will be cluster nodes must:
  • Run the same version of Windows Server.
  • Be joined to the same Active Directory domain.
  • Be in the same time zone as the local domain controller.
  • Not host the domain controller role themselves.
• Optionally, place the cluster node computer accounts in a dedicated OU to avoid conflicting Group Policy or accidental deletion.

These prerequisites apply whether using Failover Cluster Manager, PowerShell, or Windows Admin Center.

2. Confirm domain controller reachability The error text closely matches DFS/LDAP issues where the DC or PDC cannot be contacted.

• Ensure the node where the cluster is being created can reach the DC/PDC over TCP/UDP port 389 (LDAP):
  • Check firewalls between the node and DC.
  • Confirm the DC/PDC is online.
• After fixing connectivity, close and reopen any management consoles (such as Failover Cluster Manager or DFS Management) so they pick up the new state.

3. Network and DNS checks

• Verify that DNS resolution for domain controllers and cluster-related names works from each node.
• Check network adapters, cables, switches, and any NIC teaming configuration for errors.
• Review the System event log for network-related errors on the node.

4. Review cluster logs if the Cluster service fails to start If the Cluster service is failing to start or cluster creation fails repeatedly:

• Generate a fresh cluster log on the affected node:

    Get-ClusterLog -Node 'LocalNodeName' -Destination C:\temp -UseLocalTime
  

• Review logs under Event Viewer → Applications and Services Logs → Microsoft → Windows → FailoverClustering-Client → Diagnostic.
• If deeper tracing is needed, use the logman and Netsh trace steps to capture detailed Failover Clustering traces, then regenerate cluster logs from those traces.

5. If using Windows Admin Center

• Ensure Windows Admin Center is not installed on the domain controller.
• Ensure the Windows Admin Center machine is joined to the same or a fully trusted domain.
• Use an account that is a member of the Gateway Administrators group or local Administrators on the Windows Admin Center server.

Once DC connectivity and prerequisites are satisfied, retry the cluster creation. If it still fails, use the cluster logs and FailoverClustering event logs to identify the exact step where the operation stops.

---

References:

• Create a failover cluster (failover-cluster-manager)
• Create a failover cluster (powershell)
• Create a failover cluster (windows-admin-center)
• Error "The namespace cannot be queried. The specified server cannot perform the requested operation" with DFS Namespaces
• Cluster service fails to start troubleshooting guidance