That makes sense - I've not personally experienced that situation fortunately.
Thanks, Brian Desmond [email protected] c - 312.731.3132 From: Christopher Bodnar [mailto:[email protected]] Sent: Thursday, September 10, 2009 2:00 PM To: NT System Admin Issues Subject: RE: Inbound and Outbound replication on DC I just ran across this: http://support.microsoft.com/kb/875495 According to this article it looks like the server will automatically disable inbound and outbound replication under certain circumstances if it detects a USN rollback. Which can be seen by event IDs 1113 and 1115. Chris Bodnar, MCSE Sr. Systems Engineer Distributed Systems Service Delivery - Intel Services Guardian Life Insurance Company of America Email: [email protected]<mailto:[email protected]> Phone: 610-807-6459 Fax: 610-807-6003 ________________________________ From: [email protected] [mailto:[email protected]] Sent: Thursday, September 10, 2009 2:16 PM To: NT System Admin Issues Subject: RE: Inbound and Outbound replication on DC I've only ever seen this set when someone uses repadmin (or something direct like adsiedit) to set the flag on the connection object. Time delta wouldn't do this. Thanks, Brian Desmond [email protected]<mailto:[email protected]> c - 312.731.3132 From: Don Guyer [mailto:[email protected]] Sent: Thursday, September 10, 2009 12:44 PM To: NT System Admin Issues Subject: RE: Inbound and Outbound replication on DC Maybe the times got so far out of whack (I believe when it hits 5 minutes it starts causing issues) that replication disabled itself? Don Guyer Systems Engineer - Information Services Prudential, Fox & Roach/Trident Group 431 W. Lancaster Avenue Devon, PA 19333 Direct: (610) 993-3299 Fax: (610) 650-5306 [email protected]<mailto:[email protected]> From: Christopher Bodnar [mailto:[email protected]] Sent: Thursday, September 10, 2009 11:07 AM To: NT System Admin Issues Subject: Inbound and Outbound replication on DC Had an issue with a DC in a remote site. It ended up being that Inbound and Outbound replication on the DC was disabled which was shown by REPADMIN /SHOWREPS /V: DC Options: DISABLE_INBOUND_REPL DISABLE_OUTBOUND_REPL I enabled them and that seems to have fixed the problem. From what I am told by the onsite admin he was having some kind of issue with this DC yesterday and the server was eventually rebooted. The Netlogon and the Windows Time service didn't start after reboot and were manually started this morning around 6am (~9 hours later). My question is, if these 2 services didn't start. Would that cause something to flip the replication status to disabled? I don't think so, but I wanted to get the thoughts of the group here. Thanks, Chris ________________________________ This message, and any attachments to it, may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are notified that any use, dissemination, distribution, copying, or communication of this message is strictly prohibited. If you have received this message in error, please notify the sender immediately by return e-mail and delete the message and any attachments. Thank you. ________________________________ This message, and any attachments to it, may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are notified that any use, dissemination, distribution, copying, or communication of this message is strictly prohibited. If you have received this message in error, please notify the sender immediately by return e-mail and delete the message and any attachments. Thank you. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
