Windows Server 2022 File Server Cluster | Network Teaming

Hi, I would be cautious changing networking under an existing file server cluster, especially with clustered IP resources already in play.

For file server clusters, first consider whether you really need NIC teaming, or whether SMB Multichannel with separate NICs gives you the redundancy/performance you want with less cluster pain. If you do proceed with teaming, do it one node at a time in a maintenance window: drain roles, create the team, verify bindings/DNS, bring the node back, and run cluster validation for networking.

The duplicate IP event on the clustered roles suggests the cluster IP resource is seeing an address conflict or stale network identity after the team is introduced. Check old hidden adapters on every node, DNS records for the clustered name, ARP/neighbor cache on the network, and the cluster network/resource configuration. I would not make this change in production until the exact test-lab duplicate-IP cause is understood.