REplication of Sysvol

[Bunj]

Hi Everyone

I am having trouble with multiple DCs and replicating the Sysvol to each other.... It doesnt happen.

There are no errors in either dc's event log but when i put a txt file in the sysvol scripts folder it doesnt get sent across.

I have looked at AD sites and services and looked at the connections and everthing seems ok but not sure why its not doing it. Can anyone suggest on where to look or check?

Thanks

 

[skialta]

how are you putting the files there? Are you doing via the netlogon mapping,I.E. \\servername\netlgon ? If so, that won't work..you have to go to c:\windows\sysvol\sysvol\domain_name\scripts

and place the batch files there...

 

[skialta]

I just forgot you're running Win2000..just sub in the correct path instead of Windows, use WinNT\\\

 

[Bunj]

Thanks skialta but what do you mean by sub in the correct path.

If you look at the shares of the dc's i see

\\DC1\Netlogon
\\DC1\Sysvol

Same for DC2

 

[skialta]

Nope..you need to copy the files via using Windows Explorer. What I mean is instead of just copying to \\servername\netlogon instead map a drive over to C$ on the server and navigate to C:\Winnt\system32\.....

Copy them that way...make sense?

 

[Bunj]

ok i tried that and found this error in the event log

Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13508
Date: 29/12/2005
Time: 18:13:26
User: N/A
Computer: NTS0016
Description:
The File Replication Service is having trouble enabling replication from DC1 to DC2 for c:\winnt\sysvol\domain using the DNS name DC1.domain.com. FRS will keep retrying.
Following are some of the reasons you would see this warning.

[1] FRS can not correctly resolve the DNS name nts0014.harrodsaviation.com from this computer.
[2] FRS is not running on nts0014.harrodsaviation.com.
[3] The topology information in the Active Directory for this replica has not yet replicated to all the Domain Controllers.

This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.

For more information, see Help and Support Center at

http://go.microsoft.com/fwlink/events.asp.

Data:
0000: 05 00 00 00 ....

I can resolve it quite easily in a command promt no problem so its not a dns issue that i can see?

 

[skialta]

okay..I think you have a DNS configuration problem. Do this:

1. Configure all of your servers to use static DNS settings for the internal DNS server. I assume that you have DNS on at least 1 of your DC's? Basically DC1 is an Active Directory Integrated DNS server so DC1 should point to itself for DNS info. DC2 is also an AD integrated DNS server so that should be the secondary DNS server.

2. On the 1/2 DNS servers you have, confgure the DNS pointer option to point to your ISP's DNS server.

I suspect that you are using strictly external DNS servers so that they can't find each other on the interal LAN. You may be able to ping each other, but that is because of NetBIOS resolution. AD is HIGHLY dependent on a correctly configured DNS infrastructure. Take a look at the link below:

http://support.microsoft.com/default.aspx?scid=kb;en-us;300202&Product=win2000

The article is for Win2000, but it's basically the same

 

[Bunj]

Ok i followed the instructions of the microsoft document you suggested and the settings are already setup. I have already got DNS fowarders setup for external address, and have reverse lookups on all three DC's.

I decided to stop and restart the FRS service and got the following error...
Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13568
Date: 03/01/2006
Time: 09:09:03
User: N/A
Computer: DC1
Description:
The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.

Replica set name is : "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
Replica root path is : "c:\winnt\sysvol\domain"
Replica root volume is : "\\.\C:"
A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to read from the NTFS USN journal is not found. This can occur because of one of the following reasons.

[1] Volume "\\.\C:" has been formatted.
[2] The NTFS USN journal on volume "\\.\C:" has been deleted.
[3] The NTFS USN journal on volume "\\.\C:" has been truncated. Chkdsk can truncate the journal if it finds corrupt entries at the end of the journal.
[4] File Replication Service was not running on this computer for a long time.
[5] File Replication Service could not keep up with the rate of Disk IO activity on "\\.\C:".
Setting the "Enable Journal Wrap Automatic Restore" registry parameter to 1 will cause the following recovery steps to be taken to automatically recover from this error state.
[1] At the first poll, which will occur in 5 minutes, this computer will be deleted from the replica set. If you do not want to wait 5 minutes, then run "net stop ntfrs" followed by "net start ntfrs" to restart the File Replication Service.
[2] At the poll following the deletion this computer will be re-added to the replica set. The re-addition will trigger a full tree sync for the replica set.

WARNING: During the recovery process data in the replica tree may be unavailable. You should reset the registry parameter described above to 0 to prevent automatic recovery from making the data unexpectedly unavailable if this error condition occurs again.

To change this registry parameter, run regedit.

Click on Start, Run and type regedit.

Expand HKEY_LOCAL_MACHINE.
Click down the key path:
"System\CurrentControlSet\Services\NtFrs\Parameters"
Double click on the value name
"Enable Journal Wrap Automatic Restore"
and update the value.

If the value name is not present you may add it with the New->DWORD Value function under the Edit Menu item. Type the value name exactly as shown above.

For more information, see Help and Support Center at

http://go.microsoft.com/fwlink/events.asp.

Data: