RE: [ActiveDir] FRS/SYSVOL replication errors

[Jorge de Almeida Pinto]

Hi Todd,   Looking at the FRS event ids there is a DNS problem. Besides FRS (SYSVOL) replication, is AD replication working OK?   Did you also perform a domain controller rename after the domain rename? Renaming a domain does not modify the DNS suffix of the domain controllers in the domain that was renamed. DCs replicate with each using the objectGUID which can also be found in DNS zone _msdcs.ForestRootDomain as a CNAME record that points to the FQDN name of the DC. If you did not rename the DC but the old zone containing the old A records of the DCs of the renamed domain has already been removed, the DCs cannot communicate with each other. If you renamed the DC be sure the CNAME record (objectGUID) points to the new FQDN of the DC. Try: "net stop netlogon & net start netlogon" OR "netdiag /fix" to re-register all DNS records. Netdiag /fix compares the records in netlogon.dns with the records in DNS and re-registers if something is missing. Hope this helps you.   Is this the only DC that's not replicating?   Regards, Jorge   Met vriendelijke groet / Kind regards, Jorge de Almeida Pinto Microsoft Infrastructure Consultant NOTE: This posting is provided "AS IS" with no warranties! ________________________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Byrd, Todd Sent: Wednesday, February 18, 2004 20:44 To: [EMAIL PROTECTED] Subject: [ActiveDir] FRS/SYSVOL replication errors Hey All,   We are having a bit of an issue with our production network, and I’ve been troubleshooting till I’m blue in the face, so I thought I’d ask here and see if anyone else has had a similar issue.   We have a fairly typical multiple site network that we have recently upgraded from win2k3 from win2k, and then gone through the domain rename procedure (it works pretty well BTW as long as your DNS setup is error free.)  The problem occurs where our SYSVOL folder are not replicating properly between all DCs.  I am getting ntfrs error 13508 (sometimes followed by 13509, sometimes not) on occasion (not regularly) but on the workstations and DC’s I’m getting Userenv 1030 and 1058 quite often. Using the frsdiag utility from Microsoft, I’m finding several errors (mostly RPC) on my PDC, and on 3 out of 4 of my other DC’s….   ATM I can’t push GPO’s out to the enterprise as they are not replicating off of my PDC, and while I’m pretty sure that a FSMO role transfer to another box, demoting and repromoting the PDC and one of my GC servers (the boxes that the others are having a hard time communicating with) will fix the problem, I’d rather fix it without having to go to such drastic measures.     Any insight anyone can provide would be a great help.   --Todd   This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.