Discussion Locked

No domain controller

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have 5 NT wrkstns. and 5 Win9.x systems. All log into an NT 4.0 PDC. No one has a problem logging in. The NT 4.0 wrkstns. get a message, "Can't find Domain Controller, using cached copy of profile". All are able to use domain resources. Varied NT wrkstns. are unable to login, "Can't find domain controller" from time to time. When running "NBTSTAT -a name of server" it shows a conflict at "Name of Domain <1C> GROUP Registered". How do I get rid of the conflict? Is this the problem thatis causing the inability to login directly to the domain controller and using a cached copy of the users profile?

6 replies

by sfo farmer

Are you running WINS? If so tombstone any corrupt or bad WINS entries. The other question is the PDC multihomed (with 2 NIC's)? And is this also the WINS server?

Check your event viewers for browser elections. For NT in the resorce kit is a utility called browstat to find who your master browser is. Take a look at NLstat too.
You may have a Win 9x system that could be the master browser in conflict with one of your NT machines.

Hope this helps ya! SFO

by dlfman

Gave good advice. However, multi-homing is an excuse for poor routing. You shouldn't have to multi-home.

by frobo

Hi,

yes there is a problem with Servers who are runin and runing... The Server normaly doesn?t shut down and up, so he is not registering his name on the Network. Since SP4 for NT 4.0 MS has solved this Problem with a new Command for nbtstat.exe.U can use nbtstat -RR to reregister the Name ( of cource the the Domain-name too)on the Network ! Try this and all?s Ok !
For the Wks who got the Cache is lokal newer Problem click in Usermanager on Slow-Wan Link. ( REad Technet for this isue)Hope it helps

Frobo

This discussion is closed to new replies.