What Port 3343 Is
Port 3343 sits in the registered port range (1024-49151), the space managed by IANA for services that apply for official assignments. IANA never assigned one here. By the registry, this port is blank.
In practice, it isn't.
Windows Server Failover Clustering uses UDP port 3343 for the Cluster Network Driver — the component that handles inter-node heartbeat and cluster network communication. When a cluster node needs to know whether its neighbor is still alive, that question travels over UDP 3343. When nodes negotiate cluster membership, UDP 3343 carries those packets. If a firewall blocks it, the cluster can't function, nodes can't join, and validation fails.
This is common enough that sysadmins have been troubleshooting blocked UDP 3343 for years, across Windows Server versions from 2008 through 2022. Microsoft's own documentation explicitly calls it out. It's simply never been formally registered.1
How the Cluster Uses It
The NetFT (Network Fault Tolerance) driver is the kernel-level component that makes Windows clustering work. It listens on UDP 3343 to receive cluster heartbeat packets from peer nodes. When a packet arrives, the destination node's cluster service processes it and responds. Miss enough heartbeats and the cluster marks that node as unreachable — triggering failover.
The practical consequence: every Windows Server Failover Cluster, every Storage Spaces Direct (S2D) cluster, every Hyper-V cluster using shared storage needs UDP 3343 open between all cluster nodes on all cluster networks.2
How to Check What's Using This Port
On Windows, to see if anything is listening on 3343:
If you're running cluster services, you'll see the Cluster Service (clussvc.exe) listening there.
On Linux or macOS, you're unlikely to encounter anything on 3343 — this is firmly Windows territory:
Why Unassigned Ports Still Get Used
The registered port range exists so services can stake a claim and avoid collisions. But registration is voluntary. Nothing stops software from picking a number and using it — and nothing forces that software to register with IANA afterward.
Port 3343 is a clean example of this gap. Microsoft chose it, built their cluster heartbeat around it, and never filed the paperwork. The result is a port that's "unassigned" in every official sense, and critical infrastructure in practice.
When you're troubleshooting a cluster validation failure and the test says "cluster nodes are not reachable on UDP port 3343," you've found the gap between the registry and reality.3
Firewall Checklist
If you're running Windows Failover Clustering, ensure UDP 3343 is open:
- Between all cluster nodes on all cluster networks
- In both directions (inbound and outbound)
- On host-based firewalls (Windows Firewall) and any network firewalls between nodes
Missing this is one of the most common causes of cluster validation failures and nodes failing to join existing clusters.
Ήταν χρήσιμη αυτή η σελίδα;