Re: urgent: Second win2003 domain controller doesn't process login requests


<StanislavO@xxxxxx> wrote in message
news:1170597369.032576.210590@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On 4 æÅ×., 15:34, "Herb Martin" <n...@xxxxxxxxxxxxxx> wrote:
<Stanisl...@xxxxxx> wrote in message

news:1170590806.854831.71010@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Hello,
I have two Win2003 domain controllers in the organization, both
migrated from WinNT 4.0 -> Windows 2000 -> Windows 2003. One of them,
who used to be PDC previously, has motherboard malfanction which
causes it to halt unexpectedly. Unfortunately when it halts all
network resources immediately become inaccessible, user cannot login,
etc! The second DC seems to be simply ignored.

Is the second DC a DNS server AND a GC?

Do the other machines ALL know that the second DC is a DNS
server, i.e, have it in NIC->IP ->DNS Server properties as alternate.


Yes the second DC is a DNS server as is known as DNS server across
other computers. According to dcdiag, it is a GC; however I don't know
how to control it explicitly.

AD Sites and Services (MMC) enables a GC on a DC.


Meantime I promoted another Win2003 server to DC and transferred all 5
known domain controller roles to it.

Why? You already had this on the current DC, OR it was not fully replicated
which would not provide it to the "new DC".


It won't help either, though
eventlog shows no errors and several warnings, clients ignore new DC
and won't login. It's known as DNS server across organizations.
Eventlog on an old "primary" DC shows error in FRS replicating syslog
on physical level, blaming NTFS journal.

Sounds like you had replication errors to begin -- before all this happened.

You might take the current DC (and new DC) offline temporarily and try
returning the new repaired original (better to just try ONE client on a
private net with that old DC). If this works then DCPromo cycle the
OTHER DCs and keep the old one.

--
Herb Martin, MCSE, MVP
http://www.LearnQuick.Com
(phone on web site)


.

Relevant Pages

  • Re: DNS dfs issue
    ... You say that some clients are OK. ... The domain controllers for SiteA are named: ... No matter which dns server I use on clientB1 its %logonserver% is always ...
    (microsoft.public.windows.server.dns)
  • Re: Domain Controller Advice
    ... Clients use DNS to located domain controllers, ... only have one DNS server or if your clients has only one DNS server set for ... > DC1 was the first one to be installed and has all the five FSMO roles ...
    (microsoft.public.win2000.general)
  • Re: Domain Controller Advice
    ... Clients use DNS to located domain controllers, ... only have one DNS server or if your clients has only one DNS server set for ... > DC1 was the first one to be installed and has all the five FSMO roles ...
    (microsoft.public.windows.server.general)
  • Re: Domain Controller Advice
    ... Clients use DNS to located domain controllers, ... only have one DNS server or if your clients has only one DNS server set for ... > DC1 was the first one to be installed and has all the five FSMO roles ...
    (microsoft.public.windows.server.networking)
  • Re: Domain workstation cannot see the domain for adding user permi
    ... approach but to instead use ONLY your domain controllers and configure them ... does not go to the other one if the DNS server returns a "not found" ... Now I have internet access via the dsl ... The network has a dsl router which only some machines are allowed to ...
    (microsoft.public.windowsxp.security_admin)