NETLOGON not replicating files?

  • Thread starter Thread starter Carlton Whitmore
  • Start date Start date
C

Carlton Whitmore

I have five win2k servers in my AD all except one
replicate my login scripts just fine. If I go into AD
Sites And Services I can manually replicate AD stuff, but
my NETLOGON files won't replicate. Can someone help?
Carlton.
 
Could you please check if the Sysvol share on all DC's contains the same
folders?

Are there any errors or warnings in the File Replication Service Eventlog?

Christian
 
I checked and all Sysvol's have the same folders.
I did see error 13555 in the event logs and restarted
NTFRS on that server, but the error continues to come up.
It mentioned restoring the system state. Is there
something else I can try first?
 
Yes, do the following:

-Stop the File Replication Service on the failing DC
-Set the "BurFlags" Value in the following registry key to "D2"(DWORD):
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters\Backup
/Restore\Process at Startup

-Start the File Replication Service.

After that the Sysvol Folder should be reinitialized with the contents of
the other DC's.

Christian
 
You might also try making a copy of a "correct DC's" Sysvol and then
copying it BACK over the top (same DC, just to get a "file change
notification").
This will signal that all files need replication.

You might check your DNS on each DC (especially if AD isn't replicating to
that
sick DC.)

You might also run DCDiag and dump the output to a file to search for FAIL,
WARN,
and ERROR.
 
Carlton Whitmore said:
I checked and all Sysvol's have the same folders.
I did see error 13555 in the event logs and restarted
NTFRS on that server, but the error continues to come up.
It mentioned restoring the system state. Is there
something else I can try first?
Click to expand...

Make sure your DNS settings are correct and that the DNS server(s) are
operating correctly.
I had a similar problem and it turned out that another admin had been
playing around with the DNS server settings on the DC and set it to
incorrect values. This was stopping the FRS from starting.

Fixing the DNS settings allowed the FRS to start and replication began
again.
 
Christian,
That fixed it. Thanks.


-----Original Message-----
Yes, do the following:

-Stop the File Replication Service on the failing DC
-Set the "BurFlags" Value in the following registry key to "D2"(DWORD):
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs \Parameters\Backup
/Restore\Process at Startup

-Start the File Replication Service.

After that the Sysvol Folder should be reinitialized with the contents of
the other DC's.

Christian




.
Click to expand...
 
I had been having the same problems for a few months on my 65 domain
controllers. After trying everything under the sun to fix it and
hours upon hours of searching the net for info, I tried the
non-authoritative restore using the BurFlags entry in the registry.
NTFRS works like a champ now.


No On Fri, 6 Feb 2004 14:48:04 -0800, "Carlton Whitmore"
 
Back
Top