1 of 2 domain controllers down and users cannot login to the domain


we have 2 windows 2003 domain controllers here in our domain.
recently dc2 rebooted patch in middle of night
and had keyboard error (you know 1 need press f1 to
continue). easy fix disturbed me while server
was "down" none of users able login domain. if they
weren't looking the other server for authentication, dns, dhcp etc.

is client-side dns setting or time out value can changed?
is there way ensure if goes down again, users redirected
to other dc quickly?

please help!

"also, know xp once get's hold of domain controller won't change it."

this i'm talking about. seems crazy won't new dc when realize can't 1 that's down.
i read can modify dns cache settings in registry lower value don't have reboot or run ipconfig /flushdns on everyone's pc.
well we're upgrading windows 7 in next couple months maybe fix things.

thanks,
scott

sorry, not looking make things more complicated want clear up.  xp another dc if it's original server becomes unavailable - 2000, 2003, vista, 2008, win7, , 2008 r2.  if you'd like, i'd happy send network trace showing behavior clearly.  or wouldn't mind sending video capture of failover behavior.  huge part of purpose of multihomed directory service.

that said, not sure caused issue.  there have been lot of suggestions far (particularly the gc suggestion because msft client oses fail netbios find a dc if needed).  truthfully, without having trace of event it's going tough say.  best clue @ point event logs from a workstation failed logon during time period.  if have event logs , upload them review, please zip them up, upload them skydrive, , send link zip. 

again, apologize muddying water again.  wanted make clear redundant behavior of directory service , clients.

thx

/rich
http://cbfive.com


Windows Server  >  Directory Services



Comments

Popular posts from this blog

some help on Event 540

WMI Repository 4GB limit - Win 2003 Ent Question

Event ID 1302 (error 1307) DFS replication service encountered an error while writing to the debug log file