Discussion Locked

Secondary domain controller fails fault tolorance.

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi Techies

Here's the problem. I have a solid Windows 2000 network infrastructure, as far as replication, Group Policies,scopes,and everything else windows has to offer works fine. However when I decided to test shut down the Primary Server, my secondary server failed faul tolorance. Meaning I wasn't able to browse the internet or Active Directory.

Is there any one out there that can tell me where I went I wrong and how can I fix this issue. I believe it may have something to do with reverse DNS. Please help! Thank you all in advance.

9 replies

by dafe2

Your right it's likely an issue with DNS. I'd look at how your zone transfers are configured (or) even re-configure them as AD integrated zones. (Pure 2K Option Only)

Your DNS eventlogs should indicate the issue you had on this one.

Just a thought.

by sysadmintech

Hey thanks for your responce but Im going to need a little more info. I tip my admin hat to you. So far you have been the only person that attempted to answer my question.

I noticed that most of the techs on here answer the most common easy questions. Hmmmmmmmm... Hey Im not a rocket but I do enjoy a challeging question. I think thats one of my weekness in the IT world...

by dafe2

Take a look at the event logs on the primary server. They'll likely tell you where your configuration needs tweaking. ( Seems your Zone transfers aren't updating in this case )

Also, I found this article that (may) help you double check your configuration:

http://www.xenocafe.com/tutorials/windows/dns/install_configure_windows_2000_dns_server-part1.php

In addition, if your running pure 2K (I) don't see any reason why you couldn't go AD integrated DNS. Microsoft has a whitepaper that can give you all the details on implementation issues.

Good luck & let me know how you make out.

by sysadmintech

Awsome ! I think this artical is going to help me out a lot I will keep you posted.

Oh and just for the record I did check my DNS event log and its free and clear from errors.

Thanks again

by bfilmfan

On the domain controller experiencing the issue, is it configured to see use itself in the event the primary fails?

And can you ping to the default gateway from the DC experiencing issues?

The primary DC isn't routing is it?

Are all the FSMO roles on the primary DC?

In addition, is the second DC a Global Catalog?

Just some thoughts I had when I saw this thread this morning.

by nirmal_bhonsle

Try these steps.primary dns server of the primary dc pointing to itself
primary dns of the backup dc = ip of the primary dc
secondary dns of the backup dc = ip of itself.

clients having primary and secondary dns as ip of the primary dc and backup dc respectivly.

try this out and I hope you will have the network running inspite of the primary dc failing.

by jhansen

if you cant browse the network while on the fault tolerant role, do this simple test.

start->run->cmd(press ok)
ping www.yahoo.com

If FAILS

ipconfig /all

ping

If FAILS

I suspect that you don't have DHCP being controlled by the server. You most likely have it controlled by the router with a special DNS entry on the computers.

IF TRUE

Enable DHCP to be controlled by the server, disable it on the router.

Set the backup server to act as a DHCP server in the event of the other being down, or if you don't want to mess with it, just turn it on when you need it.

------------------------------------------
Computer Techs, provide your customers with easy online backup system. Become an affiliate and start your online backup business today. http://www.zray.net/AffiliateProgram.html

by maniacman

Since AD is dependent on DNS and won't work without it, I have reason to believe that your DNS isn't setup properly. Ideally, you should setup every DC to be a DNS server and host AD integrated zones. That way, every zone is primary and there are no such things as zone transfers as the DNS zones are replicated with AD during the normal replication cycle. What you want to do is specify the primary and secondary DNS servers on the DCs' to first point to themselves and then to the other DC. That way, it can use itself to resolve DNS or its peer DC if its own DNS service fails for any reason.

This discussion is closed to new replies.