DFS Folder Target Site Associations Incorrect With Server 2012


i've brought new 2012r2 file server add our existing dfs infrastructure. other dfs servers 2008r2 , working expected.

the new 2012r2 server getting wrong ad site association dfs folder targets. instead of being associated site of more specific subnet file server resides in, being associated 1 of sites configured catch-all subnet.

nltest /dsgetsite shows file server in correct ad site (new york) while folder targets on file server show associated catch-all ad site.

we have ipv4 subnets configured our ad sites. ipv6 not disabled on file server. have read, vista , beyond prefer use ipv6 determining ad site.

i'm wondering if has changed in 2012r2 preventing file server using ipv4 determine site association or maybe there 6to4 conversion going on causing associated catch-all?

or other ideas?

thanks,
dan

found problem here. our nic binding order had our iscsi nics @ top uses 172 private ip space. causing folder targets match ad site catch-all subnet configured of our private ip space


Windows Server  >  File Services and Storage



Comments

Popular posts from this blog

WIMMount (HSM) causing cluster storage to go redirected (2012r2 DC)

Failed to delete the test record dcdiag-test-record in zone test.com

Azure MFA with Azure AD and RDS