Domain Controllers

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi,

I have just introduced a second domain controller into our network and given in a copy of the global catalogue.

When I take the first dc off he network users cannot authenticate onto the network.

What else do I need to do to get the second domain controller to authenticate users when the first domain controller is down ???

Many Thanks

Paul..
 
Check the Master Roles/FSMO on 1st DC (the DC you take off
the line)Also check the DNS IP address that your clients
are pointing to (they should have both)

-----Original Message-----
Hi,

I have just introduced a second domain controller into
our network and given in a copy of the global catalogue.
When I take the first dc off he network users cannot authenticate onto the network.

What else do I need to do to get the second domain
controller to authenticate users when the first domain
controller is down ???
 
DNS is the important part. Logons, etc. don't require the FSMO roles. What
you need is to have the clients have both DCs listed as DNS servers. The
DCs should point to themselves and each other, each other and themselves or
both at one first and the other second (it doesn't matter). But they too
need to point to both.

Sometimes making a DC a GC requires a reboot...


--

Paul Williams
_________________________________________
http://www.msresource.net


Join us in our new forums!
http://forums.msresource.net
_________________________________________


Check the Master Roles/FSMO on 1st DC (the DC you take off
the line)Also check the DNS IP address that your clients
are pointing to (they should have both)

-----Original Message-----
Hi,

I have just introduced a second domain controller into
our network and given in a copy of the global catalogue.
When I take the first dc off he network users cannot authenticate onto the network.

What else do I need to do to get the second domain
controller to authenticate users when the first domain
controller is down ???
 
Yes, DNS is very important in this scenario.

Keep in mind the first DC in the domain during the DCPromo process you are
specifically asked if you want the DC to become a DNS Server. Subsequent
Domain Controllers we do not do this. Make sure that you have DNS
configured on the Second Domain Controller.

You may want to review the following information:

300202 How To Configure DNS for Internet Access in Windows 2000
http://support.microsoft.com/?id=300202

317590 HOW TO: Configure DNS Dynamic Update in Windows 2000
http://support.microsoft.com/?id=317590

255248 How To Create a Child Domain in Active Directory and Delegate the DNS
http://support.microsoft.com/?id=255248


Also. On the Second DC type the following Command: net share. Make sure
that there is a Netlogon and Sysvol Share listed there.

If not, then more then likely Sysvol has not finished replicating from the
first Domain controller. If this is the case, you may need to configure
under your Network card DNS configurations Primary DNS Server to point to
the First DC and Alternate DNS Server to Point itself.



Best regards:

(e-mail address removed)

This posting is provided "AS IS"
with no warranties, and confers no rights
 
Back
Top