hi - in my lab enviourment on VM .. i have my root domain dell.local. I am trying to add another tree in the same forest by name vodafone.local. when i run dcpromo at DNS registration window it fails and says that it will not allow to replicate. the ip of the dell.local is 10.10.10.10/8 and dns is the same the ip of vodafone.local is 10.10.10.28/8 - no matter if i put the dns server as 10.10.10.10 or 10.10.10.28 it will not correct the issue ?? any help is appreciated thanks Vic

See if open port for replication needs. "Best Practices", Event viewer, host file, perfmon, antivirus, anti-spyware, Live CD's, backups, are in my top 10

lvaibhavt what you describe has nothing to do with replication. it has everything to do with DNS and Active Directory. might want to refresh your understanding of forest and trees http://www.tech-faq.com/active-dire... you will see the correct name was not vodafone.local but vodafone.dell.local . dell.local is your root domain. You can only have one root domain.

wanderer ... vodafone.dell.local will come in picture when i am making vodafone as child domain ..... here i m talking about a new tree in an existing forest ........ i hope that makes things clear ! jefro - i'll check for the ports and update you ....

lvaibhavt you have no router or firewall between the DCs so ports don't apply. I understand you wish to create a new domain tree in the existing forest. You don't appear to undestand why your attempt failed so I will ask you a couple of questions; what is your root domain name presently? can you have multiple root domain trees in a forest? Did you review the link I gave you?

wanderer -- i understand what u r saying -- now the replication is not happening and it is because of DNS issue in event viewer........ i get the error rpc server is not available ...... i check in sites n services the settings .... even i have raised the DFL n FFL 2003 but no go ..... what i can do here ... thanks

here is what i got after running dcdiag -- i m nt sure how to fix this ip resolve concern here Domain Controller Diagnosis Performing initial setup: Done gathering initial info. Doing initial required tests Testing server: Default-First-Site-Name\STUDYDC2 Starting test: Connectivity The host c1244cb3-a96a-4648-a0d3-186b690442ce._msdcs.study.local could not be resolved to an IP address. Check the DNS server, DHCP, server name, etc Although the Guid DNS name (c1244cb3-a96a-4648-a0d3-186b690442ce._msdcs.study.local) couldn't be resolved, the server name (studydc2.study2.local) resolved to the IP address (10.12.12.15) and was pingable. Check that the IP address is registered correctly with the DNS server. ......................... STUDYDC2 failed test Connectivity Doing primary tests Testing server: Default-First-Site-Name\STUDYDC2 Skipping all tests, because server STUDYDC2 is not responding to directory service requests Running partition tests on : study2 Starting test: CrossRefValidation ......................... study2 passed test CrossRefValidation Starting test: CheckSDRefDom ......................... study2 passed test CheckSDRefDom Running partition tests on : Schema Starting test: CrossRefValidation ......................... Schema passed test CrossRefValidation Starting test: CheckSDRefDom ......................... Schema passed test CheckSDRefDom Running partition tests on : Configuration Starting test: CrossRefValidation ......................... Configuration passed test CrossRefValidation Starting test: CheckSDRefDom ......................... Configuration passed test CheckSDRefDom Running enterprise tests on : study.local Starting test: Intersite ......................... study.local passed test Intersite Starting test: FsmoCheck Warning: DcGetDcName(TIME_SERVER) call failed, error 1355 A Time Server could not be located. The server holding the PDC role is down.