DFS Namespace questions

Hi all,

I was wondering if someone could help me out with a weird issue I'm experiencing with DFS. I have a namespace, \\mycompany.com\namespace, which I created some time ago. However, I've now got a server that I added the DFS role on and wish to add as a namespace server. I replicated the data over manually (as it was a huge directory) and set replication to go on a schedule. The problem I'm getting is that when people go to \\mycompany.com\namespace, they're hitting the new location (which doesn't get replication until the evening after 5PM). It should be going to the original location.

I added this namespace server, so we could have redundancy among our organization regarding our shared resources. Put another way, if server1 goes down (original namespace server), then server2 (secondary namespace server) should pick up right away with no issues. We lose the data after the previous replication, but that should be all.

*Note: I did not use the C:\DFSRoots folder. I created a replicated directory and pointed the namespace to this directory. Please advise if there could be something I missed (or if you need more information)? Thanks in advance, guys.

Roy BeneVP/Director - IT | ISOAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

It sounds to me like you are confusing various parts of DFS namespace. There are DFS namespace servers, and they hold the namespace share that contains the pointers to the shares that actually contain your files. The physical companyname directory should not have any files, but just the directories representing the structure of you namespace and the namespace targets. Adding a namespace server should only refer to adding another server that has the pointers to the data, and is in no way related to having an additional server that actually has any data files.

In am guessing that you are also looking at having an additional DFS namespace target where you are manually replicating the files after 5 pm. This you can do this with or without having multiple DFS namespace servers. The trick is that since your files are not up to date on the second server, client machines shouldn't use them unless the other DFS target is unavailable. The only reliable way to do this IMHO is to disable the DFS target links to the secondary server. Leave them there, but disabled. This way the only available DFS target is your primary server. If the primary server goes down you will need to manually activate the DFS target links to the other server.
Aaron TomoskySD-WAN SimplifiedCommented:
while I'm by no means an expert in dfs, I do know it's tied into sites and services just like all other active directory integrated services like dns. That means you can control what ip ranges are part of what sites and which servers they should hit in what order by using weights. Depending on your exact setup, you can probably get the functionality you desire by adjusting things in sites and services.
I started using DFS namespace with Windows NT 4. The AD Site costing isn't reliable in my experience. I often connect to a server in a different site across the WAN instead of the server in my local site. This is why I recommend only having 1 active DFS target if it really matters that you connect the correct server.
Roy BeneVP/Director - IT | ISOAuthor Commented:

I'm trying to disable the namespace server (secondary) but receiving an error. Upon looking at your comment again, I noticed you said disable the target 'links' to the namespace server. Can you elaborate on that for me? Thanks so much!

Take a look at this blog post about DFS Namepsace, and search for the Multiple Targets section. The screen shot shows two targets configured. Just right click on the target pointing to your secondary server and select "Disable Folder Target".


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.