Re: NTFRS

I think I have resolved it. Added the registry key for auto recovery on the
one with the WRAP_Error and now it has re-enabled replication of the sysvol
on both.

I was worried this would create a new sysvol but it hasn't so it looks to be
working. The window2003 machine is now reporting success on the widnows 2003
machine and sysvol is populated.

Also passing FSMO test on the 2000 machine.

Looks to have been this way for months, I only was looking in detail as I am
adding a Windows 2007 exchange server and wanted to check the domain was ok
before domain prep.

Many thanks.

"Meinolf Weber" wrote:

Hello RobWUK,

Please post an unedited ipconfig /all from both DC's. Also check in a command
line on both DC's with "netdom query /domain:yourdomain FSMO" without the
qoutes and put the output here.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

Hi Meinolf,

Yes there are a few errors but he output is too large to post fully.

I get FSMO role error in the Win2000 machine - these are ok on Win2003
which is the role hold for all but infrastucture.

I have no outbound replication showing from repadmin on Win2003
machine.

Win2000 -
Running enterprise tests on : rasoft.co.uk
Starting test: Intersite
Skipping site Default-First-Site-Name, this site is outside
the scope
provided by the command line arguments provided.
......................... rasoft.co.uk passed test Intersite
Starting test: FsmoCheck
GC Name: \\win2000.rasoft.co.uk
Locator Flags: 0xe00001fc
Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355
A Primary Domain Controller could not be located.
The server holding the PDC role is down.
Time Server Name: \\win2000.rasoft.co.uk
Locator Flags: 0xe00001fc
Preferred Time Server Name: \\win2000.rasoft.co.uk
Locator Flags: 0xe00001fc
KDC Name: \\win2000.rasoft.co.uk
Locator Flags: 0xe00001fc
......................... rasoft.co.uk failed test FsmoCheck
The command completed successfully
Default-First-Site-Name\WIN2000
DSA Options : IS_GC
objectGuid : eea5afd6-6376-4fa1-80f4-4f427c7fe1da
invocationID: eea5afd6-6376-4fa1-80f4-4f427c7fe1da
==== INBOUND NEIGHBORS ======================================

CN=Schema,CN=Configuration,DC=rasoft,DC=co,DC=uk
Default-First-Site-Name\WIN2003 via RPC
objectGuid: a2fc0e91-d832-4079-a6f1-a7819d078b3b
Last attempt @ 2008-05-14 09:57.51 was successful.
CN=Configuration,DC=rasoft,DC=co,DC=uk
Default-First-Site-Name\WIN2003 via RPC
objectGuid: a2fc0e91-d832-4079-a6f1-a7819d078b3b
Last attempt @ 2008-05-14 09:57.51 was successful.
DC=rasoft,DC=co,DC=uk
Default-First-Site-Name\WIN2003 via RPC
objectGuid: a2fc0e91-d832-4079-a6f1-a7819d078b3b
Last attempt @ 2008-05-14 10:03.07 was successful.
==== OUTBOUND NEIGHBORS FOR CHANGE NOTIFICATIONS ============

CN=Schema,CN=Configuration,DC=rasoft,DC=co,DC=uk
Default-First-Site-Name\WIN2003 via RPC
objectGuid: a2fc0e91-d832-4079-a6f1-a7819d078b3b
CN=Configuration,DC=rasoft,DC=co,DC=uk
Default-First-Site-Name\WIN2003 via RPC
objectGuid: a2fc0e91-d832-4079-a6f1-a7819d078b3b
DC=rasoft,DC=co,DC=uk
Default-First-Site-Name\WIN2003 via RPC
objectGuid: a2fc0e91-d832-4079-a6f1-a7819d078b3b
"Meinolf Weber" wrote:

Hello RobWUK,

RUn diagnostic tools on both DC's to check for errors. dcdiag /v,
netdiag /v and repadmin /showreps If you get errors post the complete
output here.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and
confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
I have two DCs on a site. One a Windows 2000 SP4 and the other
Windows 2003 - no other controllers.

I have no Sysvol on the Windows 2003 server. On the Windows 2000
server I have a sysvol which is populated correctly. The domain is
functioning ok as long as the sysvol/netlogon server is up.

On the windows 2000 with sysvol I get the dreaded ntfrs Event ID
13568. On the Windows 2003 its a simple replication failure message
- cannot contacted etc.

On the 2000 box -

The File Replication Service has detected that the replica set
"DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.

I have seen various KBs about this but not sure what my best
solution is. One I have seen suggests the burflag D4 on the Windows
2000 and D2 on the 2003 to get it to authorative restore the sysvol.

Any suggestions welcome.




.

Relevant Pages

  • Re: Unable to decommission a Windows 2008 DC via dcpromo
    ... Can you open and compare sysvol and netlogon share on both DCs? ... Verifying that the local machine server2, ... The File Replication Service Event log test ... Latency information for 8 entries in the vector were ...
    (microsoft.public.windows.server.active_directory)
  • Re: Unable to decommission a Windows 2008 DC via dcpromo
    ... You can not create sysvol and netlogon share manual, ... Neither server has a firewall active on them. ... The File Replication Service Event log test ... The File Replication Service is having trouble enabling ...
    (microsoft.public.windows.server.active_directory)
  • NTFRS if possible
    ... File Replication service issue. ... I have 2 DCs (2003 server) and since an error a while back FRS has stopped ... Guid: 0dce41cc-7b2a-467a-9b817052d5918495 ... DOMAIN SYSTEM VOLUME (SYSVOL SHARE) ...
    (microsoft.public.win2000.active_directory)
  • Re: Setting up SBS 2003 and Windows Server 2003, same domain, 2 sites..
    ... Generally speaking, when checking the replication status for a specifiedDC, ... 327644 How to configure licensing on an additional Windows server in an SBS ...
    (microsoft.public.windows.server.sbs)
  • Re: NTFRS
    ... The server holding the PDC role is down. ... Default-First-Site-Name\WIN2003 via RPC ... I have no Sysvol on the Windows 2003 server. ...
    (microsoft.public.win2000.active_directory)