Noah,
  I had a feeling this might be the problem.  So I need to change the DNS server to AD Integrated on the 2nd DC.  Now, the first DC with AD-DNS is pointing to itself for DNS.  Should the 2nd DC also point to itself for DNS, or should it point to the 1st DC?
 
  I went ahead and did the GC on the 2nd DC anyhow, we may be moving to native mode pretty soon.
 
Thanks for the replies!  I hope I finally get this working correctly.
 
Ernest
 
----- Original Message -----
Sent: Friday, May 31, 2002 9:03 AM
Subject: RE: [ActiveDir] 2 AD DCs but only one accepting authentication

En,

            Your problem appears to be how your DNS setup. The Active Directory Integrated Zone will not replicate with a standard Primary, since both believe they are the master for the zone. I would set both you DC’s to AD Integrated, and if you want create a third on a member server as a secondary. Also make sure your clients point to more than one DNS server. Since you only have one domain a GC not critical, unless you implement Exchange 2000.

 

Noah Ravenscroft

 

-----Original Message-----
From:
EN [mailto:[EMAIL PROTECTED]]
Sent:
Friday, May 31, 2002 9:26 AM
To: [EMAIL PROTECTED]
Subject: [ActiveDir] 2 AD DCs but only one accepting authentication

 

I have 2 AD DCs, and when the first created DC of the domain fails, the 2nd DC doesn't accept logons.

I'm running mixed mode the GC only being on the first DC shouldn't matter right?  Has anyone else

encounted this type of problem?  When I promoted the 2nd server to a DC, everything went smoothly,

sysvol and netlogon shares were created properly. 

 

  Each DC has a DNS server as well, with the 1st DC having an AD Integrated DNS, while the 2nd has a Primary DNS, and yet another stand alone has a secondary dns.  All the dns records "seem" right, in that the svr records are showing up in each DNS server.

 

  Any ideas on what too look for to maybe solve this problem?

 

thanks

 

Ernesto

 

Reply via email to