Yep, you have good AD replication at PSDC1 as well. This would tell me that the underpinnings should be ok and the problem is most likely strictly in FRS which sucks, I hate troubleshooting FRS. :op
The duplicate connections I saw the error for would be visible in sites and services and you should see one connection that doesn't have a GUID name, it has a name of a domain controller. Err back to FRS, are there any errors in the FRS log besides the, SYSVOL is not shared out right now? If not we will have to start digging into the actual FRS debug logs located in %winnt%\debug - usually c:\winnt\debug. You will find logs that start with NTFRS and start scanning through looking for anything that could indicate an error. Possibly if the most recent one (should be named ntfrs_005.log) isn't too long you can post it so we can take a peek. Also Deji's post may have something to it in terms of the upgrade and something happening there. I am not a fan at all of in place upgrades, we did it once to the PDC for each of our domains to get the users and groups and then we quickly promoed a pure W2K machine and moved the fsmo's and wiped out the upgraded machine. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rittenhouse, Cindy Sent: Sunday, August 31, 2003 6:04 PM To: '[EMAIL PROTECTED]' Subject: RE: [ActiveDir] sysvol not replicating results from, repadmin on PSDC1 seems to indicate successful replication (lancco.root is an empty root domain for the forest). ECPDC is not listed as an outbound neighbor, I'm not sure what that implies. I did not see any duplicate connections. C:\Documents and Settings\Administrator.LC_POLICE>repadmin /showr Default-First-Site-Name\PSDC1 DSA Options : IS_GC objectGuid : 01dd65d5-caee-4e09-8cb3-85a7d4642ae9 invocationID: 5d17cfd7-0d9d-4f10-bf89-b5fbba2dc6d2 ==== INBOUND NEIGHBORS ====================================== DC=police,DC=lancco,DC=pa,DC=us EastCocalicoPD\ECPDC via RPC objectGuid: 261bdbfc-59ef-4aa8-b087-36fe5e363e9f Last attempt @ 2003-08-31 17:40.47 was successful. Default-First-Site-Name\PSDC2 via RPC objectGuid: a584f646-c7ea-48de-a08d-dfc938ba959a Last attempt @ 2003-08-31 17:47.09 was successful. CN=Schema,CN=Configuration,DC=LANCCO,DC=ROOT Default-First-Site-Name\LANCCODC3 via RPC objectGuid: 9e4c1826-5051-4c89-8016-ebc9f36f0156 Last attempt @ 2003-08-31 17:12.34 was successful. Default-First-Site-Name\PSDC2 via RPC objectGuid: a584f646-c7ea-48de-a08d-dfc938ba959a Last attempt @ 2003-08-31 17:12.34 was successful. Default-First-Site-Name\LANCCODC2 via RPC objectGuid: 0472b4a6-ae4b-44a9-afae-805e24ce729e Last attempt @ 2003-08-31 17:12.35 was successful. EastCocalicoPD\ECPDC via RPC objectGuid: 261bdbfc-59ef-4aa8-b087-36fe5e363e9f Last attempt @ 2003-08-31 17:40.47 was successful. CN=Configuration,DC=LANCCO,DC=ROOT Default-First-Site-Name\LANCCODC2 via RPC objectGuid: 0472b4a6-ae4b-44a9-afae-805e24ce729e Last attempt @ 2003-08-31 17:35.43 was successful. EastCocalicoPD\ECPDC via RPC objectGuid: 261bdbfc-59ef-4aa8-b087-36fe5e363e9f Last attempt @ 2003-08-31 17:40.47 was successful. Default-First-Site-Name\PSDC2 via RPC objectGuid: a584f646-c7ea-48de-a08d-dfc938ba959a Last attempt @ 2003-08-31 17:44.59 was successful. Default-First-Site-Name\LANCCODC3 via RPC objectGuid: 9e4c1826-5051-4c89-8016-ebc9f36f0156 Last attempt @ 2003-08-31 17:45.43 was successful. DC=LANCCO,DC=ROOT Default-First-Site-Name\LANCCODC3 via RPC objectGuid: 9e4c1826-5051-4c89-8016-ebc9f36f0156 Last attempt @ 2003-08-31 17:12.35 was successful. EastCocalicoPD\ECPDC via RPC objectGuid: 261bdbfc-59ef-4aa8-b087-36fe5e363e9f Last attempt @ 2003-08-31 17:40.47 was successful. Default-First-Site-Name\LANCCODC2 via RPC objectGuid: 0472b4a6-ae4b-44a9-afae-805e24ce729e Last attempt @ 2003-08-31 17:46.04 was successful. ==== OUTBOUND NEIGHBORS FOR CHANGE NOTIFICATIONS ============ DC=police,DC=lancco,DC=pa,DC=us Default-First-Site-Name\LANCCODC1 via RPC objectGuid: 3f95d0a2-8baf-48d5-83c0-c14b2e5ab02a Default-First-Site-Name\LANCCODC3 via RPC objectGuid: 9e4c1826-5051-4c89-8016-ebc9f36f0156 Default-First-Site-Name\PSDC2 via RPC objectGuid: a584f646-c7ea-48de-a08d-dfc938ba959a CN=Schema,CN=Configuration,DC=LANCCO,DC=ROOT Default-First-Site-Name\LANCCODC2 via RPC objectGuid: 0472b4a6-ae4b-44a9-afae-805e24ce729e Default-First-Site-Name\LANCCODC1 via RPC objectGuid: 3f95d0a2-8baf-48d5-83c0-c14b2e5ab02a Default-First-Site-Name\LANCCODC3 via RPC objectGuid: 9e4c1826-5051-4c89-8016-ebc9f36f0156 Default-First-Site-Name\PSDC2 via RPC objectGuid: a584f646-c7ea-48de-a08d-dfc938ba959a CN=Configuration,DC=LANCCO,DC=ROOT Default-First-Site-Name\LANCCODC2 via RPC objectGuid: 0472b4a6-ae4b-44a9-afae-805e24ce729e Default-First-Site-Name\LANCCODC1 via RPC objectGuid: 3f95d0a2-8baf-48d5-83c0-c14b2e5ab02a Default-First-Site-Name\LANCCODC3 via RPC objectGuid: 9e4c1826-5051-4c89-8016-ebc9f36f0156 Default-First-Site-Name\PSDC2 via RPC objectGuid: a584f646-c7ea-48de-a08d-dfc938ba959a -----Original Message----- From: Joe [mailto:[EMAIL PROTECTED] Sent: Sunday, August 31, 2003 8:23 AM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] sysvol not replicating Ok Cindy, with this information we know your time information is ok or else ECPDC couldn't pull AD replication across. However you also want a repadmin /showreps from the other side to make sure that the other DC's can resolve and pull data from ECPDC. Anytime you are checking replication, you have to check both side, checking one side only tells you half the story. This is because AD and FRS replication is not one connection going both ways but actually two connections, both of them pull. So you can actually have one DC pulling from another ok but not vice versa. So go to PSDC1 and run the same showreps command to verify that you see successful replications being pulled from ECPDC. You may have a case where some data needed hasn't made it back to the rest of the forest so it isn't allowing you to pull the NTFRS data. Also we may have to look at the seeding server (if it is other than PSDC1) and verify that it is replicating with the rest of the domain/forest ok. There was also one post I saw where it mentioned duplicate connections. I.E. Someone may have manually created a connection between ECPDC and PSDC1. If that is the case I think I would remove it for now and see if we can get the topology to correct itself. joe -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rittenhouse, Cindy Sent: Friday, August 29, 2003 10:51 PM To: '[EMAIL PROTECTED]' Subject: RE: [ActiveDir] sysvol not replicating results from repadmin look fine, server is running SP4 C:\Documents and Settings\Administrator.LC_POLICE>repadmin /showreps ecpdc EastCocalicoPD\ECPDC DSA Options : IS_GC objectGuid : 261bdbfc-59ef-4aa8-b087-36fe5e363e9f invocationID: 9f91ded7-35c3-47a9-a30f-312f51da6f3a ==== INBOUND NEIGHBORS ====================================== DC=police,DC=lancco,DC=pa,DC=us Default-First-Site-Name\PSDC1 via RPC objectGuid: 01dd65d5-caee-4e09-8cb3-85a7d4642ae9 Last attempt @ 2003-08-29 22:42.22 was successful. CN=Schema,CN=Configuration,DC=LANCCO,DC=ROOT Default-First-Site-Name\PSDC1 via RPC objectGuid: 01dd65d5-caee-4e09-8cb3-85a7d4642ae9 Last attempt @ 2003-08-29 22:42.22 was successful. CN=Configuration,DC=LANCCO,DC=ROOT Default-First-Site-Name\PSDC1 via RPC objectGuid: 01dd65d5-caee-4e09-8cb3-85a7d4642ae9 Last attempt @ 2003-08-29 22:42.22 was successful. DC=LANCCO,DC=ROOT Default-First-Site-Name\PSDC1 via RPC objectGuid: 01dd65d5-caee-4e09-8cb3-85a7d4642ae9 Last attempt @ 2003-08-29 22:42.22 was successful. ==== OUTBOUND NEIGHBORS FOR CHANGE NOTIFICATIONS ============ -----Original Message----- From: Joe [mailto:[EMAIL PROTECTED] Sent: Friday, August 29, 2003 5:28 PM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] sysvol not replicating This is probably a silly question, but you have applied all of the latest SP's and hotfixes correct and this machine isn't sitting at like SP1 or something? There are a ton of fixes for FRS out there. Other than that I would be looking at DNS very carefully and also checking regular replication (repadmin /showreps) to make sure that was working as well. joe -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rittenhouse, Cindy Sent: Friday, August 29, 2003 10:33 AM To: [EMAIL PROTECTED] Subject: [ActiveDir] sysvol not replicating Two days ago a consulting firm upgraded a BDC at a remote location to Windows 2000. After the upgrade users had all types of trouble connecting. It seems the sysvol is not replicating because the Do_Not_Remove_NtFrs_PreInstall_Directory, Policies directory, and Scripts directory do not exist on the remote server in either the sysvol\domain or the sysvol\sysvol directory. The rest of AD seems to be replicating fine. Can I simply copy those directories from one of my DCs to the DC in the remote location? Thanks Cynthia Rittenhouse MCSE,CCNA LAN Administrator County of Lancaster Lancaster, PA 17602 List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
