DC's netlogon share is not replicating

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: RoadRunner (rr_at_rr.com)
Date: 02/12/04 

Date: Thu, 12 Feb 2004 13:20:07 GMT

I have 3 domain controllers in the same domain. All 3 were upgraded from
NT4.

When making a change to the netlogon share on either the first or second DC,
the change is immediately replicated to the other, but never makes it to the
third.

If I make a change to the netlogon share on the third DC, it never
replicates to the first or second DC.

I need to manually copy the files over.

So in short, the third DC's netlogon share is not replicating at all. Any
ideas on how I can troubleshoot this problem? There are no errors in the
NTFRS logs and the service is running.

TIA

Relevant Pages

  • Re: 1 PC sloooow after W2K upgrade
    ... It sounds like the NETLOGON is where your problem lies. ... domain controllers for MYDOMAIN. ... Can you ping both domain controllers OK? ...
    (microsoft.public.win2000.setup_deployment)
  • Re: Logon Banner
    ... >create the 9X policy and copy it to the NETLOGON ... folder on the DC ... >Robert Vegas ... >> from the domain controllers? ...
    (microsoft.public.win2000.networking)
  • Re: Netlogon & Sysvol Shares disappear after reboot
    ... >I have one of my 3 domain controllers that continues to lose the Netlogon ... >and Sysvol shares. ... If I reboot the server they don't appear after startup. ...
    (microsoft.public.win2000.active_directory)
  • Re: Site Question
    ... > To add a bit to this, one advantage of more site links would be if you ... > with B but not C, B replicates with C and not A, etc. IE more fine-grained ... >> If there are domain controllers at each of the three sites this would ... No matter how fast and reliable a WAN link is you ...
    (microsoft.public.win2000.active_directory)
  • Re: login.bat on server 2003
    ... \\<server name>\netlogon the Netlogon share replicates to all DCs ... > Where do I save the login.bat files on Server 2003? ...
    (microsoft.public.windows.server.scripting)