DFS driving me bananas

[guinnessman]

I have installed the DFS that now operates on two DCs.
DFS points to a number of shared files on server1. Each share has an identical replica partner which has been linked and set to automatic replication with an identiacl shared folder on server 2.
The problem is that some clients using Sage Accounts production are not seeing all the newly created files. DFS is creating a new subfolder on the DFS relica (on server2) called NTFRS pre-existing **** and this is where the new files are being replicted to instead of in the original shared folder on server2.
The mapped drives on all clients point to \\domain.com\all data.

The rsult being that some clients are being directed to server2 where the folder only has some original data and new files etc are created in this new NTFRS folder.

It's driving me bananas.

Can anyone tell me why DFS is crating these new folders and why some clients seem to be now accessing the

Remember, it's all just ones and zeros!

 

[aftertaf]

i think i might pull the plug on DC1, a swift dcpromo in the gut, restart it all....
damn thing crashed each time i tried querying AD with .NET anyway.... i think its a bit scrambled since day one...
some ones in the wrong places, too many zeros involved on a daily basis


thx

 

[aftertaf]

i have extra dfs tips in case anyone can benefit:

if you have replication problems... try using a different dfs root DC, and try using a different server as a replication partner (i.e. test 2 dfs roots independantly on both DCs, using a third server as a replica of nodes on both DFS trees.... if only one of them fails, you have isolated the DC that has a problem... works in my case)

once you have managed to get something working:
take care in planning your dfs namespace and shares....
-No dfs root or share should have the same name as an existing share on any one of your Domain Controllers... cos the dfs topology is replicated in AD, when you access the share on the DC, you wind up in the dfs share instead....
basically, use distinct, separate names for each element of the dfs tree, otherwise it will mess itself up...