Active Directory failover not working as intended

Hello,

We have a relatively small domain - 7 servers total with about 200 users...  All of our servers are running MS Windows Server 2003...  for lack of a better term our PDC (which I know doesn't exist anymore) is called MSDSB04.  It handles DNS as well as Active Directory and DHCP on the local LAN segment.

I have added two other Active Directory servers over the last year or so - the intent being that if something happened to MSDSB04 they would handle DNS and authentication requests seamlessly without any interruption of service to the LAN users... this has not worked...  When MSDSB04 goes offline - it kills the LAN.

What do I need to do to get these other servers to pick up the slack on demand?
iain_stephenIT ManagerAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
Chris DentConnect With a Mentor PowerShell DeveloperCommented:

Hey,

You need a few things.

You mentioned it, but didn't say whether or not the other servers were running the DNS Service? And if so, are they mentioned in your clients TCP/IP config?

One of the other most important things is that you set your servers to be Global Catalog, this is done through AD Sites and Services, then under your Site, Servers, your Server and the properties for NTDS Settings you should see a little tick box. There are no problems with you making all your Domain Controllers Global Catalog.

Chris
0
 
iain_stephenIT ManagerAuthor Commented:
Just a note - thank you for keeping it simple and not referring me to endless Microsoft KB articles... the key was the global catalog - it was only checked for the 'PDC' - not the other two servers...

I have done that now and will try it out tonight...

One other question - if you have the time - The original 'PDC' is also running DHCP for the local LAN segment...  should I be setting up any kind of failover for that?  Perhaps it would be best to move the DHCP function to the main router (default gateway)?
0
 
Chris DentPowerShell DeveloperCommented:

Possibly the best way to deal with DHCP is to split the scope up into two, then have one DHCP Server hand out the first half and another the second.

Works pretty well really.

Chris
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.