Issue with NT Domain Controllers

[Guest]

Archived from groups: microsoft.public.windowsnt.domain (More info?)

We have two NT domain controllers in our network. My
understanding is that either one should be able to
authenticate user logins. The issue is that only one of
the two actually seems to be authenticating user logins at
any given time. More significantly is that if the one
that is currently authenticating user logins goes down the
other domain controller does not detect this and start
allowing user accounts to login through it. As a result
users can't login to the NT domain.

If I reboot the other domain controller it will seemily
notice that the other controller is down when it boots up
and then start authenticating user logins itself but it
does not seem to me that I should have to do this.

Any thoughts on what might cause this behaivor? Both
domain controller are on the same network (ie: no routers)

Thanks in advance...

PW

 

[Guest]

Archived from groups: microsoft.public.windowsnt.domain (More info?)

In an NT 4.0 domain all DCs register a special netbios name
domain name 1c group name which contains the tcp/ip address
of the PDC and all BDCs on the domain, this name must be
resolved to find a DC for authentication. There is a known
problem when the name goes into conflict and prevents machines
from finding a DC, if you open a dos prompt on the BDC and
run nbtstat -n you can view the local name table and see if the
name is in conflict a reboot usually clears the conflict but if it
reoccuring there might be another reason this happening and
there is a hotfix for it.:

The "domain<1c>" Name Is Occasionally in Conflict
http://support.microsoft.com/default.aspx?scid=kb;en-us;314696

"pwallace" <pwallace@rmh.org> wrote in message news:
> We have two NT domain controllers in our network. My
> understanding is that either one should be able to
> authenticate user logins. The issue is that only one of
> the two actually seems to be authenticating user logins at
> any given time. More significantly is that if the one
> that is currently authenticating user logins goes down the
> other domain controller does not detect this and start
> allowing user accounts to login through it. As a result
> users can't login to the NT domain.
>
> If I reboot the other domain controller it will seemily
> notice that the other controller is down when it boots up
> and then start authenticating user logins itself but it
> does not seem to me that I should have to do this.
>
> Any thoughts on what might cause this behaivor? Both
> domain controller are on the same network (ie: no routers)
>
> Thanks in advance...
>
> PW
>
>