Re: AD Error - Urgent
- From: "Jorge Nunes - Europa Filmes" <webmaster@xxxxxxxxxxxxxxxxxxx>
- Date: Wed, 8 Mar 2006 17:31:17 -0300
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
--
Paul Williams
Microsoft MVP - Windows Server - Directory Services
http://www.msresource.net | http://forums.msresource.net
.
- Follow-Ups:
- Re: AD Error - Urgent
- From: Paul Williams [MVP]
- Re: AD Error - Urgent
- Prev by Date: difference in groups
- Next by Date: Re: ADAM Install Error - Error Code: 0x8008041d
- Previous by thread: Re: AD Error - Urgent
- Next by thread: Re: AD Error - Urgent
- Index(es):
Relevant Pages
|