RE: sysvol replication problems
From: piakter (piakter_at_discussions.microsoft.com)
Date: 03/23/05
- Next message: ptwilliams: "Re: Why GPO doesn't work?"
- Previous message: Roy T: "Why GPO doesn't work?"
- In reply to: Allen Firouz: "RE: sysvol replication problems"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 22 Mar 2005 23:11:02 -0800
Immediately after I posted this message, I decided to configure another
domain controller within the same site as the problem one. This seemed to
solve the problem though I do not know why. I got event ID 13509 and now
am continuosly getting 13516 which is a good sign ( I demoted the new one
afterwards). However, when I run sonar on the previously problem DC, the
DataCollectionState shows failed while the other two are successful. Could
there still be a problem?
"Allen Firouz" wrote:
> Piakter:
>
> Are you seeing Event 13509 in the logs? If you are, then it is not a big
> cause for concern. However, if event 13508 is showing up and 13509 is not,
> then you need to further troubleshoot. Below is the Microsoft procedure for
> troubleshooting this error (http://tinyurl.com/5phyb ). Post back the
> results:
>
> To troubleshoot FRS Event 13508 when FRS Event 13509 does not occur, perform
> the following steps:
>
> 1. Examine the Event 13508 in the FRS Event Log to determine the computer
> with which FRS has been unable to communicate.
> 2. Determine whether or not the remote computer is working properly, and
> verify that FRS is running on it. A good method for doing this to execute
> NTFRSUTL VERSION <FQDN_of_remote_DC_name> from the computer logging the 13508
> event. If this fails, check network connectivity by sending an ICMP packet to
> the <FQDN_of_remote_DC_name> from the machine logging the 13508 event. If
> this fails, troubleshoot as a Domain Name System (DNS) or TCP/IP issue. If it
> succeeds, confirm that FRS is started on the remote domain controller.
> 3. Determine whether or not FRS has ever been able to communicate with the
> remote computer by looking for event 13509 in the event log and review recent
> change management to networking, firewalls, DNS configuration and Active
> Directory infrastructure to see if there is a correlation.
> 4. Determine whether there is anything between the two machines that is
> capable of blocking Remote Procedure Call (RPC) traffic, such as a firewall
> or router.
> 5. Confirm that Active Directory replication is working.
>
> -Allen Firouz
>
> "piakter" wrote:
>
> > I have 3 win 2003 domain controllers in 3 different sites. One site was
> > continually giving me this error "FRS has failed to add computer %1 to the
> > replica set c:\windows\sysvol \domain ...etc, while the replica DC %2 was
> > giving me Event ID. 13508. I decided to demote DC %1 and then promoted it
> > again. Now I am getting Event ID 13565 on DC %1 and still same Event ID
> > 13508 on DC %2. All other replication is working fine.
> > Some one please help, am getting desperate
> > --
> > El diri diri kalafala
- Next message: ptwilliams: "Re: Why GPO doesn't work?"
- Previous message: Roy T: "Why GPO doesn't work?"
- In reply to: Allen Firouz: "RE: sysvol replication problems"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
