Directory Replication

[LordByron]

Enviroment:<br>
Single NT Domian, NT 4.0 SP4 on Servers and Workstations.<br>
PDC and some BDC's at HQ Building, BDC's at other sites across State. Some T1, some 56K links back to HQ.<br>
<br>
PDC currently replicates logon scripts and some templates from export folder to import folder on BDC's with a T1 link. Those BDC's then replicate from thier import directory to other BDC's close by with slow 56K links.<br>
<br>
Problem:<br>
Lots of Replicator errors 3216 and 3208 in event log. More disturbing is the appearance of seemingly corrpted directories with the name tmptree.RP$. <br>
Technet articles on this seem to piont to a problem with exlusive access to the files during export, but I'm not sure.<br>
<br>
Does anyone use replication in a similar way in a similar enviroment? Succesfully?<br>
<br>
I'm also having problems with user's profiles being corrupted, does anyone think this could be related?<br>
<br>
Thanks.<br>

 

[jsauce]

This is a problem with NTFS, If you set up a computer running Windows NT Server to export to itself using the<br>
Directory Replicator service on an NTFS partition, you receive the following<br>
errors:<br>
<br>
Event 3208 "The replication service could not update directory tmptree.rp$ from source on %3 due to error 183" Event 3216 "The system error 5 occurred" The errors may result from corruption in the NTFS permissions assigned to the export files.<br>
Stop the replication and copy the export files to a FAT partition. You could also try converting your NTFS partition to a FAT partition using a program like Partition Magic. Since this is most likely caused by the permissions, replacing the NTFS with FAt would stop this, since FAT does not support file and directory permission security.<br>
<br>

 

[SRG]

I have worked with this before as well over slow links. I have found that in some cases over a slow link a scheduled robocop works better that a directory replication.