I have a Windows Failover Cluster set up with a file Server. There are two nodes and two networks.
Network 1 used for LAN SMB access and Network 2 used for private SMB storage for a bunch of Hyper-V Server hosts that are otherwise not associated with the Failover Cluster.
Network 2 is where the issue is. It's configured with a static IPv4 address 10.10.11.10/24 and the Hyper-V hosts are on the same subnet. DNS is set up with an A record that points to this address.
I want to switch it over to IPv6. I configured Node1 with address fdbb::1/64 and Node2 with fdbb::2/64 I added an "IPv6 Address" resource to the cluster with address fdbb::ffff/64, to the same group as the IPv4 address, stopped the Network Name resource, created a dependency from the Network Name resource to the new IPv6 Address resource, same as the v4 address, and started the Network Name and File Server resources:
Add-ClusterResource -Name 'IP Address fdbb::ffff' -Group 'HvStor' -ResourceType 'IPv6 Address'
Get-ClusterResource "IP Address fdbb::ffff" | Set-ClusterParameter -Multiple @{"Network" = "Network 2"; "Address" = "fdbb::ffff"; "PrefixLength" = 64}
Stop-ClusterResource 'HvStor'
Add-ClusterResourceDependency 'HvStor' 'IP Address fdbb::ffff'
Start-ClusterResource 'HvStor'
Start-ClusterResource 'File Server (\\HvStor)'
When I go to \\10.10.11.10 in explorer, I see files. When I go to \\fdbb--ffff.ipv6-literal.net I get "This folder is empty".
I checked output from Get-SmbServerNetworkInterface on the current owner node for the cluster and it shows fdbb::ffff address as being associated with scope HvStor which is the same as the working 10.10.11.10 address. The address is also associated with the same interface as the IPv4 address.
I'm at a bit of a loss. I've tried removing the IPv6 address and readding but this failed to work.
Any help would be greatly appreciated.
