higgsy
asked on
DFS Domain.local share
Hi
I have set up DFS between 2 servers to work in realtime with DFS named spece domain.local i have redirected users desktop to be \\domain.local\users so that in effect the users desktops are now working from the name space DFS share.
Sometimes but not all the time if i copy a file to the desktop or create a new file on the desktop it will not appear for 30 second (ish) or i will have to press "refresh" to be able to see the file. I assume this is something to do with the DFS named space share but has anyone had this before???
Higgsy
I have set up DFS between 2 servers to work in realtime with DFS named spece domain.local i have redirected users desktop to be \\domain.local\users so that in effect the users desktops are now working from the name space DFS share.
Sometimes but not all the time if i copy a file to the desktop or create a new file on the desktop it will not appear for 30 second (ish) or i will have to press "refresh" to be able to see the file. I assume this is something to do with the DFS named space share but has anyone had this before???
Higgsy
I would consider this normal. You are writing to a server's share, and thus it's not local. It will take a moment to refresh.
ASKER
yes but desktop redirect is a standard GPO function and this is interminitent, you would expect a couple of seconds delay but not 30 seconds.
You're writing to a DFS share - it is queued up before it is written.
You can test this with one workstation and a NON-DFS share. It should happen pretty-much immediately.
You can test this with one workstation and a NON-DFS share. It should happen pretty-much immediately.
ASKER
how do i make it instant then rather than queing up??? and how would this explain the fact i have to refresh to make it appear????
The desktop is loaded at startup. Anything saved to it is generally instant - however, you are saving the file to a DFS share. What you are staring at on the PC is not local.
There is nothing I know about to make this instant.
There is nothing I know about to make this instant.
ASKER
ok but what we are dealing with is 30 seconds for a 5 kb file. And if you instantly right click refresh it will appear striaght away, we are not talking about a file copy issue its a DFS name space share.
regards
Higgsy
regards
Higgsy
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I just ran across this: http://support.microsoft.com/kb/899409/en-us
Not sure if it fits, but it sounds suspicious.
Let me know.
Not sure if it fits, but it sounds suspicious.
Let me know.
ASKER
cheers dude i will try this tongiht
ASKER
Sir i think this is going beyond the limits of experts exchange but I am going to report on it anyway for the benefit of the community i will award points for your efforts cheers for the involvment and will post another question anyway ( so if you do solve it will get 2 lots of points)
---- What i basically has is a problem with the Name Space in DFS Using Windows 2003 R2 -----
I set up a replication group betwen the users folder on 2 servers \\SERVER01\users and \\SERVER02\users this works absolutely fine in realtime. I have set up a namespace being \\domain.local\dfs\users which obviously mapps in AD and on the namespace servers the locations of the 2 shares for this namespace and which one is the master.
The issue that we have is that when you copy a file to a name space share it does not appear till you press F5 or close the folder and go back to it. Please see below for tests i conducted and history:
-Tests-
- Opened the \\SERVER01\users and \\SERVER02\users shares in 2 seperate windows and dragged a file into \\SERVER01\users which instantly replicated to the other share without having to press F5
- With these 2 windows still open I opened another window \\domain.local\dfs\users if i drag a file into this share it instantly appears in the \\SERVER01\users and \\SERVER02\users windows but i have to press F5 in the namspace share window to make it appear which proves that the copy works well but the name space has problems returning the file list for that folder untill you refresh.
-History-
- This is release candidate server 2 which is meant to have a different DFS setup.
- I have un-installed the name space and reinstalled with different names. ( i like to break fix break fix for education)
- This did work initially then it kind of stopped working slowly untill now all the time we have this issue
- I have uninstalled and reinstalled the service
-Conclusion-
I think this is an issue with DFS and active directory, AD has DFS system keys in which control information about the name space share which i think is now messy as i have uninstalled and re-installed the name spaces. This is obviously not a network / replication group isssue I think AD has beome messy and the DFS part of it needs to be cleaned / restored.
Can anyone help
Higgsy
---- What i basically has is a problem with the Name Space in DFS Using Windows 2003 R2 -----
I set up a replication group betwen the users folder on 2 servers \\SERVER01\users and \\SERVER02\users this works absolutely fine in realtime. I have set up a namespace being \\domain.local\dfs\users which obviously mapps in AD and on the namespace servers the locations of the 2 shares for this namespace and which one is the master.
The issue that we have is that when you copy a file to a name space share it does not appear till you press F5 or close the folder and go back to it. Please see below for tests i conducted and history:
-Tests-
- Opened the \\SERVER01\users and \\SERVER02\users shares in 2 seperate windows and dragged a file into \\SERVER01\users which instantly replicated to the other share without having to press F5
- With these 2 windows still open I opened another window \\domain.local\dfs\users if i drag a file into this share it instantly appears in the \\SERVER01\users and \\SERVER02\users windows but i have to press F5 in the namspace share window to make it appear which proves that the copy works well but the name space has problems returning the file list for that folder untill you refresh.
-History-
- This is release candidate server 2 which is meant to have a different DFS setup.
- I have un-installed the name space and reinstalled with different names. ( i like to break fix break fix for education)
- This did work initially then it kind of stopped working slowly untill now all the time we have this issue
- I have uninstalled and reinstalled the service
-Conclusion-
I think this is an issue with DFS and active directory, AD has DFS system keys in which control information about the name space share which i think is now messy as i have uninstalled and re-installed the name spaces. This is obviously not a network / replication group isssue I think AD has beome messy and the DFS part of it needs to be cleaned / restored.
Can anyone help
Higgsy
ASKER
i have still not got this solved im going to have to put a call into Microsoft.