You might want to try the FRS troubleshooter.
http://www.microsoft.com/windowsserver2003/technologies/fileandprint/file/dfs/tshootfrs.mspx
Download the FRS Monitoring Help File; the troubleshooter is under one of
the topics.
Here are some things to check.
* Make sure your topology didn't change.
* Make sure each of the 3 machines' views of the replication topology agree
with each other. Topology information is stored in AD, so AD replication
latencies and FRS AD polling latencies could cause topologies to go out of
sync.
* Try creating new files with different names in the replica tree on each of
the three machines. Verify these files reach the other machines. Note if
you are relying on existing files in the replica to see if they are
replicating, you could be in a sharing violation situation which will block
replication. It will look like FRS isn't working, but in fact, FRS is
waiting for the application(s) to close their handle.
* Make sure you're not creating files that are being filtered by FRS (e.g.
foo.tmp).
* Consider installing Ultrasound to monitor FRS. Ultrasound also has the
capability to create propagation test files (automates the test in the above
bullet).
Please post any other questions and follow-ups regarding FRS to
microsoft.public.windows.server.dfs_frs.
--Richard
Please post FRS related questions to microsoft.public.windows.server.dfs_frs
and prefix the subject line with "FRS:" to make it easier to spot. Note that
FRS is used to replicate SYSVOL on domain controllers and DFS root and link
targets.
For additional FRS resources, please visit
http://www.microsoft.com/frs.
This posting is provided "AS IS" with no warranties, and confers no rights.
