I'm having intermittent problems with a DFS namespace we use for our filestore management.The problem happens randomly and is not specific to any machine. When a folder or file is created, the name is not visible unless manually refreshing by pressing F5 or navigating back and forward.This is particularly annoying and disruptive for the users.All client machines in the organisation are fully patched to XP SP3. I found a hotfix document, but it seemed like the problem should have been resolved in SP3?The Organisation has 2 servers both running Server 2008 R2 Standard and DFS replication of the filestore between sites.They are part of a wider network domain which also has other domain controllers (Server 2003) and clients.The diagnostic report confirmed that replication is working successfully.If connecting to the local network share (rather than published DFS), then the problem doesn't occur.Any help would be appreciated. Problem is very intermittent and frustrating.

Hi, To better understand the issue, please help confirm the following: 1. Do you mean that every time the issue occurred, the file or folder got visible immediately after you pressed F5? 2. Was the file/folder affected newly created? Or all files/folders in the target folder was not visable? 3. Had you checked if the target folders were synchronized between the servers when the issue occurred? Thanks. I look forward to your response.This posting is provided "AS IS" with no warranties, and confers no rights.

Hi , Please provide the OS version along with the sp level. How have you configured the DFS , is it a Mesh mode or Hub and spoke ?" When a folder or file is created, the name is not visible unless manually refreshing by pressing F5 or navigating back and forward."does this behavior happens to old namespace --> folders ? or happening when you create a new namespace --> folders --> files ?

Hi,Thanks very much for response.1. Yes- file/folder is not visible until pressing F5. Then need to rename the file/folder from default and press F5 again for the change to take place. Problem doesn't occur if using standard folder share and not DFS.2. All files/folders are visible in DFS share. It only happens when creating a new file/folder. And it is random - sometimes no refresh is required. For example a user said everything was ok in the morning, then the problem occurred in the afternoon. It's fine if working on existing files/folders.3. I created standard word docs - and they replicated instantly. Used fileshare path to test, rather than DFS share.4. All client machines are XP SP3. Servers with DFS Namespace and replication are Server 2008 Standard R2.5. I'm sure its Full Mesh mode (how can I double-check? - can't see anything to confirm). The verify topology confirms fully connected for data flow. Bandwidth 64Kbps Mon-Fri 9-5. Full bandwidth replication at other times. There's shadow copies on the volume - I don't suppose that would cause problems?Many Thanks

One additional thing to add- it's not specific to 1 site. Problem occurs in both sites at random times on random machines.

Hi, Thanks for your information. This looks more like a client side issue. I notice that you have already installed Windows XP SP3. Please also check if the registry values NoSimpleNetIDList at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer is set to1 on Windows XP client. 823291 File list in the Windows Explorer folder is not refreshed after you create, move, or delete files http://support.microsoft.com/default.aspx?scid=kb;EN-US;823291 Meanwhile, please perform a clean boot and temporarily uninstall Anti-virus software on some client machines to test issue. How to configure Windows XP to start in a "clean boot" state http://support.microsoft.com/kb/310353 In addition, please check if the following registry values exist: NoRemoteRecursiveEvents NoRemoteChangeNotify HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer If there are, please ensure that the value of them is 0. This posting is provided "AS IS" with no warranties, and confers no rights.