Unable to find domain controller. User will be logged using local credentials

[Clementius]

Hi,
We were running one Windows 2003 server (PDC emulator) and two NT 4.0 domain
controllers on our network. One of the NT 4.0 domain controller died over
the week-end. All users run a script from netlogon share. Since the NT 4.0
domain controller died we have had some users getting "Unable to find domain
controller. User will be logged using local credentials". This happens on
Windows NT 4.0 workstation only. When they get the message, they do not run
the login script and do not get access to share drive. Any thoughts on why
this is happening? Is there a way to disable login using local credentials
on the NT workstations? Thank you for your input. C

 

[Hope this helps!!]

Can the scripts go into a GPO or into the SYSVOL dir on
the W2K3 server?

 

[Clementius]

The scripts are into the sysvol of Win2K3 and also the netlogon share on NT
4.0. I think the machines do no even try to connect to the servers. They
cannot connect to the died server and use local credentials instead of
connecting to the live servers. C

 

[Round Two....]

Flush the DNS. Make the pc's go look for the server they
need.

 

[Bobby]

You've probably already tried this, but I'll just throw this out there
anyway. Remove all references to the crashed 4.0 server within AD. Remove
any references to it on the local workstation such as in the LMHOSTS file. I
know, LMHOSTS is WINS, but kill it anyway. Make sure you don't have it
listed in the DNS suffix list. Run the NETDOM utility on one of the domain
controllers to verify that the crashed DC isn't still being recognized as a
DC. It shouldn't matter, though. When a DC goes down the other DC's are
supposed to pick up the slack. Interesting error...

Regards,



BT