SYSVOL / NETLOGON not share

[mikiemov]

Hi guys,

We have a 2000 domain, with 2 DC's running 2000 server with SP4. I noticed that sysvol / netlogon havent been replicating, so took the action of dcpromo'ing one dc, then back to a DC again.

Now, on the "new" dc the syscol and netlogon folders are not automatically shared ? therefore replication wont take place between the DC's...any ideas as we use GPOs and Logon scripts.

Thanks.

 

[keeyw]

Hi mikiemov,
If u run dcpromo on the Active Directory DC it will unistall the Active Directory and become normal W2k Server

 

[mikiemov]

Hi Keeyw, maybe I didnt make myself clear..I ran dcpromo to unpromote it, rebooted server, ran dcpromo again to make it a DC, then rebooted...

 

[keeyw]

Hi Mikiemov,
Are u are running the 2 DC under the same Domain ?

 

[mikiemov]

yes...

 

[keeyw]

When u running 2 DC under the same Doamin, the netlogon folder will automatic replicate each other. If your new DC is not having the Sysvol and Netlogon share after the DCpromo, most likely it is something went wrong during u unpromo and re- promo the DC. You may need to re-install the W2k and re-run dcpromo.

 

[mikiemov]

thanks keeyw, you have confirmed my worst thoughts....

 

[nhidalgo]

Make sure that the file replication service is running on both domain controllers and that there arent' any errors in the event log pertaining to file replication service. If there is an error on the original domain controller it will not replicate to the other one and the netlogon share will not be created. The file replication service is responsible for the netlogon share being replicated. You may want to download the 2000 support tools and run dcdiag on both server to make sure everything is working correctly. Reinstalling the second domain controller may not fix your problem.

Nick

 

[ecunupe]

check on the older DC in the File Replication Service event logs and make sure you do not have a 13568 or 13567 on this DC. You could be in journal wrap on this DC and therefore not be able to replicate sysvol.

 

[mikiemov]

Hi guys, thanks for response, was getting journal wrap errors on "old" DC, resolved by:

To modify the default behavior, make the following changes in the registry to
instruct FRS to handle the JRNL_WRAP_ERROR status automatically:
1. Stop FRS.
2. Start Registry Editor (Regedt32.exe).
3. Locate and click the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters
4. On the Edit menu, click Add Value, and then add the following registry value:
Value name: Enable Journal Wrap Automatic Restore
Data type: REG_DWORD
Radix: Hexadecimal
Value data: 1 (Default 0)
5. Quit Registry Editor.
6. Restart FRS.