hadame
asked on
AD Sites and Replication Implementation.
I've setup AD single domain with child domains underneath.
I want my root DC to replicate to all 31 child domain controllers. Is it a good idea to replicate all dc's among each other or just all child dc's to root dc. Also, in one of the child domains I accidentally erased the ndts settings from the AD Sites and Services MMC. Cannot bring it back, to specify who it will be replicating to. Any clues or suggestions.
I want my root DC to replicate to all 31 child domain controllers. Is it a good idea to replicate all dc's among each other or just all child dc's to root dc. Also, in one of the child domains I accidentally erased the ndts settings from the AD Sites and Services MMC. Cannot bring it back, to specify who it will be replicating to. Any clues or suggestions.
Housenet
-Configure bridgehead servers to handle replication trafic for the sites. You can setup schedules to have the traffic send at off hrs or via smtp.. I would perform a non-authoritative restore of the system state of the DC with the deleted objects with ntdsutil.
ASKER
I've designated my root dc as the preferred bridgehead server with the IP transport. I also have created sites and moved their proper child dc to it. Additionally, created site links betweeen each child dc to the root dc. Subnets were created and assigned to their respective site.
Should I designate each child dc as bridgehead server too? My network consists of 31 T1 lines coming to a Central Office location, which is where my root dc is at.
Should I designate each child dc as bridgehead server too? My network consists of 31 T1 lines coming to a Central Office location, which is where my root dc is at.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I setup the root domain controller of each site as a global catalog server. Also all root child dc are setup to replicate with the main root bridgehead server. I'm goin to designate each root child dc as bridgehead server as sugested. I'm noticing that each root child dc is being getting automatic connections among each other by itself. I guess is a KCC process. I did a non authorative restore on my failed dc, and it worked. Now I can see those lost NTDS settings from that server. Let me try that.
-I'm goin to designate each root child dc as
bridgehead server as sugested.
-Thats very good.
-I'm noticing that each root child dc is being getting automatic connections among each other by itself. I guess is a KCC process.
-Yes , among each other within the site is perfectly normal. If they're replicating between sites to each other, thats okay too but you want to make sure this only happens in the bridgehead is down, so... Assign a higher cost to any connections you do not want used frequently.
-Default cost is 100 ...A good hogh cost number is 200..
bridgehead server as sugested.
-Thats very good.
-I'm noticing that each root child dc is being getting automatic connections among each other by itself. I guess is a KCC process.
-Yes , among each other within the site is perfectly normal. If they're replicating between sites to each other, thats okay too but you want to make sure this only happens in the bridgehead is down, so... Assign a higher cost to any connections you do not want used frequently.
-Default cost is 100 ...A good hogh cost number is 200..
-Any news Hadame ?>
ASKER
I'm still having problems with 3 dc's not replicating properly. I've tried a force replicate, the repadmin, and no success. Here are the messages:
Partner Name: sgm-site\SGM-DC
Partner GUID: A4F28F29-C75C-4F8E-9207-AA
Last Attempted Replication: 6/18/2001 6:34:56 AM (local)
Last Successful Replication: 6/14/2001 6:03:15 PM (local)
Number of Failures: 56
Failure Reason Error Code: 1722
Failure Description: The RPC server is unavailable.
Synchronization Flags: DRS_PER_SYNC,DRS_USE_COMPR
USN of Last Property Updated: 196247
USN of Last Object Updated: 196247
Transport: Inter-Site RPC
Partner Name: um-site\UM-DC
Partner GUID: 0B748D9D-85DB-4E33-B7F1-AC
Last Attempted Replication: 6/18/2001 6:35:19 AM (local)
Last Successful Replication: 6/11/2001 11:51:34 AM (local)
Number of Failures: 110
Failure Reason Error Code: 1722
Failure Description: The RPC server is unavailable.
Synchronization Flags: DRS_PER_SYNC,DRS_USE_COMPR
USN of Last Property Updated: 143896
USN of Last Object Updated: 143896
Transport: Inter-Site RPC
Partner Name: fe-site\FE-DC
Partner GUID: 5FA9E947-87F9-493F-B629-23
Last Attempted Replication: 6/18/2001 5:53:39 AM (local)
Last Successful Replication: 6/6/2001 2:59:23 PM (local)
Number of Failures: 186
Failure Reason Error Code: 1723
Failure Description: The RPC server is too busy to complete this operation.
Synchronization Flags: DRS_WRIT_REP,DRS_PER_SYNC,
USN of Last Property Updated: 17103
USN of Last Object Updated: 17103
Transport: Inter-Site RPC
I already checked the connections, ping, UNC, http, and they are working fine. Any suggestions?
Partner Name: sgm-site\SGM-DC
Partner GUID: A4F28F29-C75C-4F8E-9207-AA
Last Attempted Replication: 6/18/2001 6:34:56 AM (local)
Last Successful Replication: 6/14/2001 6:03:15 PM (local)
Number of Failures: 56
Failure Reason Error Code: 1722
Failure Description: The RPC server is unavailable.
Synchronization Flags: DRS_PER_SYNC,DRS_USE_COMPR
USN of Last Property Updated: 196247
USN of Last Object Updated: 196247
Transport: Inter-Site RPC
Partner Name: um-site\UM-DC
Partner GUID: 0B748D9D-85DB-4E33-B7F1-AC
Last Attempted Replication: 6/18/2001 6:35:19 AM (local)
Last Successful Replication: 6/11/2001 11:51:34 AM (local)
Number of Failures: 110
Failure Reason Error Code: 1722
Failure Description: The RPC server is unavailable.
Synchronization Flags: DRS_PER_SYNC,DRS_USE_COMPR
USN of Last Property Updated: 143896
USN of Last Object Updated: 143896
Transport: Inter-Site RPC
Partner Name: fe-site\FE-DC
Partner GUID: 5FA9E947-87F9-493F-B629-23
Last Attempted Replication: 6/18/2001 5:53:39 AM (local)
Last Successful Replication: 6/6/2001 2:59:23 PM (local)
Number of Failures: 186
Failure Reason Error Code: 1723
Failure Description: The RPC server is too busy to complete this operation.
Synchronization Flags: DRS_WRIT_REP,DRS_PER_SYNC,
USN of Last Property Updated: 17103
USN of Last Object Updated: 17103
Transport: Inter-Site RPC
I already checked the connections, ping, UNC, http, and they are working fine. Any suggestions?
ASKER
I'm still having problems with 3 dc's not replicating properly. I've tried a force replicate, the repadmin, and no success. Here are the messages:
Partner Name: sgm-site\SGM-DC
Partner GUID: A4F28F29-C75C-4F8E-9207-AA
Last Attempted Replication: 6/18/2001 6:34:56 AM (local)
Last Successful Replication: 6/14/2001 6:03:15 PM (local)
Number of Failures: 56
Failure Reason Error Code: 1722
Failure Description: The RPC server is unavailable.
Synchronization Flags: DRS_PER_SYNC,DRS_USE_COMPR
USN of Last Property Updated: 196247
USN of Last Object Updated: 196247
Transport: Inter-Site RPC
Partner Name: um-site\UM-DC
Partner GUID: 0B748D9D-85DB-4E33-B7F1-AC
Last Attempted Replication: 6/18/2001 6:35:19 AM (local)
Last Successful Replication: 6/11/2001 11:51:34 AM (local)
Number of Failures: 110
Failure Reason Error Code: 1722
Failure Description: The RPC server is unavailable.
Synchronization Flags: DRS_PER_SYNC,DRS_USE_COMPR
USN of Last Property Updated: 143896
USN of Last Object Updated: 143896
Transport: Inter-Site RPC
Partner Name: fe-site\FE-DC
Partner GUID: 5FA9E947-87F9-493F-B629-23
Last Attempted Replication: 6/18/2001 5:53:39 AM (local)
Last Successful Replication: 6/6/2001 2:59:23 PM (local)
Number of Failures: 186
Failure Reason Error Code: 1723
Failure Description: The RPC server is too busy to complete this operation.
Synchronization Flags: DRS_WRIT_REP,DRS_PER_SYNC,
USN of Last Property Updated: 17103
USN of Last Object Updated: 17103
Transport: Inter-Site RPC
I already checked the connections, ping, UNC, http, and they are working fine. Any suggestions?
Partner Name: sgm-site\SGM-DC
Partner GUID: A4F28F29-C75C-4F8E-9207-AA
Last Attempted Replication: 6/18/2001 6:34:56 AM (local)
Last Successful Replication: 6/14/2001 6:03:15 PM (local)
Number of Failures: 56
Failure Reason Error Code: 1722
Failure Description: The RPC server is unavailable.
Synchronization Flags: DRS_PER_SYNC,DRS_USE_COMPR
USN of Last Property Updated: 196247
USN of Last Object Updated: 196247
Transport: Inter-Site RPC
Partner Name: um-site\UM-DC
Partner GUID: 0B748D9D-85DB-4E33-B7F1-AC
Last Attempted Replication: 6/18/2001 6:35:19 AM (local)
Last Successful Replication: 6/11/2001 11:51:34 AM (local)
Number of Failures: 110
Failure Reason Error Code: 1722
Failure Description: The RPC server is unavailable.
Synchronization Flags: DRS_PER_SYNC,DRS_USE_COMPR
USN of Last Property Updated: 143896
USN of Last Object Updated: 143896
Transport: Inter-Site RPC
Partner Name: fe-site\FE-DC
Partner GUID: 5FA9E947-87F9-493F-B629-23
Last Attempted Replication: 6/18/2001 5:53:39 AM (local)
Last Successful Replication: 6/6/2001 2:59:23 PM (local)
Number of Failures: 186
Failure Reason Error Code: 1723
Failure Description: The RPC server is too busy to complete this operation.
Synchronization Flags: DRS_WRIT_REP,DRS_PER_SYNC,
USN of Last Property Updated: 17103
USN of Last Object Updated: 17103
Transport: Inter-Site RPC
I already checked the connections, ping, UNC, http, and they are working fine. Any suggestions?
Hey hadame... So there does not seem to be a true RPC problem ?
-I'll tell you, your errors do not seem too good. Info on them seems also non-existant.. not very encouraging...
-I suggest you read these 2 articles..
-http://www.windows2000faq.com/Articles/Index.cfm?ArticleID=20348
http://www.windows2000faq.com/Articles/Index.cfm?ArticleID=13400
-And these results..
http://search.support.microsoft.com/kb/psssearch.asp?SPR=win2000&T=B&KT=ALL&T1=7d&LQ=replication+failure&PQ=PastQuery&S=F&A=T&DU=C&FR=0&D=ntrelease&LPR=&LNG=ENG&VR=http%3A%2F%2Fsupport.microsoft.com%2Fsupport%3Bhttp%3A%2F%2Fsupport.microsoft.com%2Fservicedesks%2Fwebcasts%3Bhttp%3A%2F%2Fsupport.microsoft.com%2Fhighlights&CAT=Support&VRL=ENG&SA=GN
-I'll tell you, your errors do not seem too good. Info on them seems also non-existant.. not very encouraging...
-I suggest you read these 2 articles..
-http://www.windows2000faq.com/Articles/Index.cfm?ArticleID=20348
http://www.windows2000faq.com/Articles/Index.cfm?ArticleID=13400
-And these results..
http://search.support.microsoft.com/kb/psssearch.asp?SPR=win2000&T=B&KT=ALL&T1=7d&LQ=replication+failure&PQ=PastQuery&S=F&A=T&DU=C&FR=0&D=ntrelease&LPR=&LNG=ENG&VR=http%3A%2F%2Fsupport.microsoft.com%2Fsupport%3Bhttp%3A%2F%2Fsupport.microsoft.com%2Fservicedesks%2Fwebcasts%3Bhttp%3A%2F%2Fsupport.microsoft.com%2Fhighlights&CAT=Support&VRL=ENG&SA=GN
-Look here also..
http://63.88.172.128/faq/query.html?col=faq&qt=replication%20failure
http://63.88.172.128/faq/query.html?col=faq&qt=replication%20failure
-I remember using this tool before.. Its pretty good..& can test replication & offer advice... try it..
http://www.netiq.com/ADcheck/ThankYou.asp?prod=
http://www.netiq.com/ADcheck/ThankYou.asp?prod=
ASKER
Replication is getting better after applying these changes. Also your links are very useful. Thanks again Housenet :-)