Hi, is it possible to set a default DFS root that the your client pcs connect to ?, im having major problems with users sharing files. When a user creates a new file on the public drive, another user then uses their pc to access public and because they are connected to a different version of public they cannot see the file until it is replicated over to the other public, this problem is even more apparent when a user creates a file in their home share, goes to another pc in another part of the building, logs in only to find the file they created is 'not there', because it hasn't yet replicated across. I need a way to fix what root people are connecting too so when they log onto a new pc they are all seeing the same folders, otherwise im going to have to just go back to the old shared folder method on one server.

Hello How is your DFS currently setup? maybe a brief description of this can help us assist you betterIsaac Oben MCITP:EA, MCSE

I have two dfs servers, I shall call them server1 and server2 on server one I have 5 shared folders : \\server1\public \\server1\staff_public \\server1\pupilhomedrives \\server1\staffhomedrives \\server1\media and the same one server two \\server2\public \\server2\staff_public \\server2\pupilhomedrives \\server2\staffhomedrives \\server2\media These are all added into dfs as replicating roots so I have : root1 - \\ourdomain.com\public root2 - \\ourdomain.com\staff_public etc etc... When someone logs on they seem to get at random either : \\server1\public or \\server1\public The problem occurs if this happens, if the person logs onto pc1 and creates a document in P: (Public Drive) \\server1\public\document1.doc they go to their colleague at pc50 who then opens the P: public drive only to find that the file doesn't exist, this is because their pc connected to \\server2\public when they logged in, eventually the file replicates across, but this isn't much help if they need it up to an hour after it has been created as its just not there. Ideally I would have them having the same server as the default so this problem doesn't happen.

Hello You can force all users to only use a particular server for referral by editing the registry as follows Go to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dfs Add: "PreferLogonDC" dword:Value of 1 This will force users to use this server as their default for referrals You may want to look into dfs target prioritization http://msdn.microsoft.com/en-us/library/bb524795(VS.85).aspxIsaac Oben MCITP:EA, MCSE

What happens if the other DC handles the login though, wont it then connect to that too, as both servers handle logins ?. I have gone into the DFS admin and turned off dfs referral for the slower server out of the two for its link, not sure if this will sort the problem by giving it only one choice ?.

If you do the registry entries above.. Add: "PreferLogonDC" dword:Value of 1 to the DC that you need to use as default Add: "PreferLogonDC" dword:Value of 0 to the DC that you don't want to use as defaultIsaac Oben MCITP:EA, MCSE

Thanks for that, I will give it a go and see how it goes :) , just another question, what does the dfs referral enable / disabled actually do other than stopping the other server version being available to connect to, is there any disadvantage of having it set to disabled ?.

Hi, As far as I know, the SiteCostedReferrals and PreferLogonDC registry keys only apply to SYSVOL and Netlogon DFS referrals. If the network speed is fast, I suggest you place your DFS server in two sites to force clients to choose the server in their own site. Thanks.This posting is provided "AS IS" with no warranties, and confers no rights. Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.