I've just brought up a new 2012R2 file server to add to our existing DFS infrastructure. All other DFS servers are 2008R2 and are working as expected.
The new 2012R2 server is getting the wrong AD site association for DFS folder targets. Instead of being associated with the site of the more specific subnet the file server resides in, it is being associated with one of the sites that is configured with a catch-all subnet.
nltest /dsgetsite shows that the file server itself is in the correct AD site (New York) while all folder targets on the file server show that they are associated with the catch-all AD site.
We have only IPV4 subnets configured for our AD sites. IPV6 is not disabled on this file server. From what I have read, Vista and beyond prefer to use IPV6 for determining AD site.
I'm wondering if something has changed in 2012R2 that is preventing this file server from using IPV4 to determine site association or maybe there is some 6TO4 conversion going on that is causing it to associated with the catch-all?
Or any other ideas?
Thanks,
Dan