Dear, after I post this message, I verify the 2 new DC don´t have the SYSVOL
and NETLOGON folders, only the first DC

I trnsfer FSMO and GC to first DC and tomorrow I will be let down the 2 new
DC (Windows 2003 Server).

After I repeat the DCPROMO to promote the Windows 2003

I pray to solution

Thanks

Jorge Nunes
Support Analyst
São Paulo / Brazil



You have DNS resolution problems.  Point all three DCs at one DC for DNS and
restart NETLOGON on each DC after verifying your DNS zone (that maps to your
AD namespace) is configured to accept dynamic updates.

Once this is done, run the following command to verify all DCs have
registered in DNS:

nslookup -type=srv _ldap._tcp.dc._msdcs.domain-name.com


If that returns all three DCs, fire up REPLMON and force replication.

Also, ensure that the GC is registered in DNS:

nslookup -type=srv _ldap._tcp.gc._msdcs.forest-root-name.com

If one system has SYSVOL and the other two don't, you need to perform a
non-auth restore on the two that don't have SYSVOL.  Before doing this,
ensure that FRS is OK on the working system.  If it is, do the following on
each of the two broken systems:

1.  net stop ntfrs
2.  Set the BurFlags reg value to "D2" (without the quotes). [1]
3.  net start ntfrs


If there are problems on the server that has SYSVOL.  See kb315457 for info.
on how to rebuild from scratch.


---
[1] The BurFlags value can be found at:
HKLM\ SYSTEM\ CurrentControlSet\ Services\ NtFrs\ Parameters\
Backup/Restore\ Process at Startup\

Password Complexity
ADAM Subset
Fsmo question
Upload tool
Best DNS set up for multiple sites
Group Policy Problems on new server
AD Error - Urgent
DC hosted on Virtual Server 2005 Time Sync Problem
User Account Lockout
IP Printer assignment in AD