DFS-N will not fail over
Posted on 2014-10-15
Two brand new Dell servers, Win 2008 R2, all patched. Both are DCs in new domain. Set up DFS-R, folders are replicating without issue. Both are at the same site and connected to the same switch, everything.
Set up DFS-N with both servers as nameservers. Namespace works fine - when users go to the namespace address, they see the files. Plus since the namespace is pointing to folders replicated with DFS-R, changes are replicated between the servers. So far, so good.
When I attempt to test by disconnecting one server from the network, users who were pointed to the "down" server remain pointed there (at least according to the client's DFS tab in folder properties), and I am unable to change settings on the "up" server (nothing can be changed while the other namespace server is down).
How to configure the namespace servers for high availability? Someone suggested clustering, but I thought the whole point of multiple namespace servers is to prevent this need for clustering.