I would focus on resolving the memory leak issue you mentioned. Here is some helpful resources specific to DFS (in no particular order):
List of currently available hotfixes for Distributed File System (DFS) technologies in Windows Server 2003 and in Windows Server 2003 R2: http://support.microsoft.com/default.aspx?scid=kb%3bEN-US%3b958802 You experience synchronization problems if you do not disable the cache option for offline files on roaming user profile shares in Windows Server 2003: http://support.microsoft.com/kb/842007 An update to turn off default SNP features is available for Windows Server 2003-based and Small Business Server 2003-based computers: http://support.microsoft.com/kb/948496 "The network BIOS command limit has been reached" error message in Windows Server 2003, in Windows XP, and in Windows 2000 Server: http://support.microsoft.com/kb/810886/en-us DFS clients may access the DFS root server in the remote site even though the DFS root server in the local site is available in a Windows Server 2003-based domain: http://support.microsoft.com/kb/944505/en-us Distributed File System Replication in Windows Server 2003 R2 performs unnecessary replication when an antivirus application is installed: http://support.microsoft.com/kb/944804 The Storage Team at Microsoft - File Cabinet: http://blogs.technet.com/filecab/archive/tags/DFS+Replication/default.aspx Top 10 Common Causes of Slow Replication with DFSR: http://blogs.technet.com/askds/archive/2007/10/05/top-10-common-causes-of-slow-replication-with-dfsr.aspx Replicated files are copied over the network when you use the Distributed File System (DFS) Replication feature on a Windows Server 2003 R2-based computer: http://support.microsoft.com/kb/931685 Microsoft DFS (Technet): http://technet.microsoft.com/en-us/library/bb735136.aspx Distributed File System Replication: Frequently Asked Questions: http://technet.microsoft.com/en-us/library/cc773238.aspx An update is available to support the DFS Namespaces Client failback feature on Windows Server 2003 SP1-based computers and on Windows XP SP2-based computers: http://support.microsoft.com/kb/898900/en-us *Memory Leak Resources:* http://support.microsoft.com?kbid=260055<http://support.microsoft.com/?kbid=260055>"OHCI1394 Driver May Cause a Memory Leak During Asynchronous Write Operation<http://www.pcreview.co.uk/forums/thread-1510669.php#> " http://support.microsoft.com?kbid=262386<http://support.microsoft.com/?kbid=262386>"Non-Paged Pool Memory Leak on Master Browser" http://support.microsoft.com?kbid=264223<http://support.microsoft.com/?kbid=264223>"How to Troubleshoot <http://www.pcreview.co.uk/forums/thread-1510669.php#> 'Stop 0x0000001E' with First Parameter of 0xC0000044" http://support.microsoft.com?kbid=272568<http://support.microsoft.com/?kbid=272568>"Event ID 2019 or 2020 or 'Insufficient System Resources' Error Returned When Logging On" http://support.microsoft.com?kbid=286060<http://support.microsoft.com/?kbid=286060>"Mapping Shared Local Printers to Central Share Causes Server to Crash Generates Event ID 2020 from SRV" http://support.microsoft.com?kbid=293857<http://support.microsoft.com/?kbid=293857>"'Stop 0x0000007' Error Message Because of a Memory Leak in the Daprotim.sys File" http://support.microsoft.com?kbid=296265<http://support.microsoft.com/?kbid=296265>"Windows 2000 Non-Paged Pool Is Exhausted by Afd.sys" http://support.microsoft.com?kbid=299623<http://support.microsoft.com/?kbid=299623>"'Stop OxAB' Error Message May Be Displayed on the Terminal Server<http://www.pcreview.co.uk/forums/thread-1510669.php#> " http://support.microsoft.com?kbid=316102<http://support.microsoft.com/?kbid=316102>"DFS Root Servers Leak Non-Paged Pool Memory in Dfs.sys in Windows 2000" http://support.microsoft.com?kbid=317249<http://support.microsoft.com/?kbid=317249>"How to Troubleshoot Event ID 2021 and Event ID 2022" http://support.microsoft.com?kbid=815493<http://support.microsoft.com/?kbid=815493>"Paged Pool Memory Leak with Increase in Handle Count for Services.exe" http://support.microsoft.com?kbid=830067<http://support.microsoft.com/?kbid=830067>"Event 2020 error message when you run WQuinn's QuotaAdvisor 4.1 build 452 or earlier on Windows 2000 Server or on Windows NT Server <http://www.pcreview.co.uk/forums/thread-1510669.php#>" http://support.microsoft.com?kbid=832762<http://support.microsoft.com/?kbid=832762>"Slow system performance <http://www.pcreview.co.uk/forums/thread-1510669.php#>or your computer stops responding because of a memory leak in paged pool memory in Windows 2000 SP4" - Sean On Wed, May 27, 2009 at 8:18 AM, John Aldrich <[email protected]>wrote: > We have two machines set up with DFS replication between them for the > files. It seems that one of the machines lost synchronization with the other > and has been a bit “behind” the other server by about 30 minutes or so. That > is to say that there was a different version of the same file on each > server. I have resolved this by rebooting the “delayed” server, but it seems > to me that we should not have to do this. The “primary” server (the “up to > date” one) reboots every night as it’s got a bad memory leak. The other > server reboots every week. Is this what is causing the replication issues? > > > > [image: John-Aldrich][image: Tile-Tools] > > > > > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
<<image002.jpg>>
<<image001.jpg>>
