Directory Replication

There are some registry parameters that can affect network traffic, all of which are values found in HKEY_LOCAL_MACHINESystem\CurrentControlSet\Services\Replicator\Parameters.
*Guard time?This value (default of 2 minutes) sets the amount of time that the export folder must be stable (i.e., with no changes made to it).
*Interval?This value (default of 5 minutes) specifies how often the export server looks for changes in the export folders.
*Pulse?This value (default of 3 minutes) specifiesthe number of times import machines repeat the change notice after the initial announcement of changes.
*Random?This value (default of 60 seconds) specifies the maximum time that the import machines can wait before requesting an update. An import server uses the export server's value of Random to generate a random number of seconds (from 0 to the value of Random). The import machines will wait this long after receiving an update notice before requesting the replica from the export server. This prevents the export server from being overloaded by simultaneous update requests.

There are some registry parameters that can affect network traffic, all of which are values found in HKEY_LOCAL_MACHINESystem\CurrentControlSet\Services\Replicator\Parameters.
*Guard time?This value (default of 2 minutes) sets the amount of time that the export folder must be stable (i.e., with no changes made to it).
*Interval?This value (default of 5 minutes) specifies how often the export server looks for changes in the export folders.
*Pulse?This value (default of 3 minutes) specifiesthe number of times import machines repeat the change notice after the initial announcement of changes.
*Random?This value (default of 60 seconds) specifies the maximum time that the import machines can wait before requesting an update. An import server uses the export server's value of Random to generate a random number of seconds (from 0 to the value of Random). The import machines will wait this long after receiving an update notice before requesting the replica from the export server. This prevents the export server from being overloaded by simultaneous update requests.

Ok... I'm not writing this to get rejected by you...but, you have given too little information to address this issue.

Have you monitored your NETWORK TRAFFIC? How many users on the Domain? Are you using SCSI drives on both servers? How much memory do you have vs. how many services on each server? What topography (type network; 100Mb, 10Mb, Tocken..) do you have? And are you using any mix-match topographies where you might use T3, T1, DSL or some other sort? Are you running across routers? How many directories are you replicating and are they REQUIRED? Some replication are NESTED with subdirectories that are not needed.

These questions can help us help you.
Do me a favor and COMMENT here with some of your answers...

Latez-

Please don't be worried about rejection, your questions are valid and I am pleased to answer them. Your exactally what I was looking for! Here we go. I have done network monitoring and nothing seems unusual. No SCSI, all IDE drives. It's a Win NT 4.0 server enterprise edition running SP5 with 64mb of ram on an 10baseT star network with a passive hub. There are 25 users on the network, but I am only trying to replicate between 2 machines. The folder I am replicating is small, 30k at best. This is a classroom project and I always plan on going to lunch after it's implemented because I know I will get back before it completes the replication. I though someone out there would have a registry edit or other "trick" I could use to impress my classmates and gain some serious knowledge, but if it's gonna be all about more memory, T1's and SCSI's I guess I will have to take a longer lunch. Thank you for your time Latez-

To kickstart directory replication, on the exporting server (presumeably the PDC) stop and start the Directory Replication Service (from the Services applet in Control Panel).

Be aware that directory replication is very limited and should be usedonly to replicate the NETLOGON directory between a PDC and its BDCs. Anything beyond that exceeds the scope of Directory Replication.

This question was closed by the author