Windows Forum

Ask something
Discussion Locked

cannot find domain controller

0 helpful
14 replies

by bwalker

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have a windows 98 workstation that cannot find it's nt 4 domain controller for authentication...after being shot down at both client and microsoft family logon (pass by selecting "OK") the mapped dive connects to said domain controller. None of the other workstations (which use the same Logon/password, have this problem...this one didn't until last week...so far have...removed and reinstalled network settings...removed and reinstalled nic and network settings...replaced nic and reinstalled network settings...reloaded os. We use static addressing, no Wins, i have confirmed that the settings are identical to other stations. Can access all shares including domain controller. I'm at a loss, a little help??

14 replies

by stillatit

To ensure finding the Directory Controller:
Install NETBEUI if not already installed. Then add an entry to the LMHOSTS file pointing at the domain controller, and including the #PRE and #DOM: tags.

Various passwords:
In the network control panel, there is a selection for which login is the primary login for the machine (Microsoft client or Windows). This should be set to Microsoft Client. In the control panel, you should be able to change the user's password. Make sure the username and password are the same on the W98 box as on the Domain.

Reinstalling the OS should make no difference, since you did not kill or change the registry copy that the user keeps in his profile directory (or the windows directory if users are not differientiated). If each user has their own profile directory, save the user's files, then delete the user from the machine, and kill or rename their profile directory. The user profile will be created again when the user next logs in, and the user will re-create his password on that machine.

Good luck.

by shanghai sam

No go...had already considered these options...we run as little broadcast (netbeui) as possible, none running in that domain...had compared hosts files with other machines with no problems finding controller...have done everything conceivable tousername/password already...I did try suggestions anyway...thanks for the thoughts...again no problem finding box which houses domain controller, just doesn't recognize it as such for authentication purposes.

by bill_dixon39

Make sure the hosts file has entry for domain controller IP address(check out what is in workstations that are connecting) , you may also check that
you have permissions in that trusted domain

by bwalker

Already done...there are no listings other than local on boxes with successful authentication...this domain serves one purpose, running an application which allows up to six workstations share an application all with the same logon for the ease of user logon...the user can still run application from unauthenticated station, just receive warnings when trying to logon to domain.

by bwalker

This domain was created for the specific purpose of sharing an application between up to six workstations...single logon for all to simplify logon for users...checked hosts files on toher workstations...nothing listed with the exception of localhost. Thanks

by pcsamaritan

This sounds to easy to be the answer but you indicated the Domain is set up to only allow 6 users to log in all with same username. Any chance the domain controller thinks that 6 users are already logged in regardless of fact? Presume you have checked at the controller and don't need to kill any false connections. Is problem the drive letter mapping to the controller or logging into the domain, I am little confused. Killing a drive mapping and recreating it with an account that has rights to the "available" resource might fix a reconnect at login mapping problem.

by bwalker

25 users allowed...only 1 (and always the same one) of 6 set up thus far has this problem...this is a new problem, wasn't for 6 months of successful operation...no problem mapping, refuses to find domain controller for authentication purposes, but the share mapped to resides on the same box as the domain controller...there must be something very simple we're missing

by earthworm

When you re-installed the OS, did you install over the old copy? If so try killing it completely, Fdisk/Killmbr whatever, but start from complete scratch, and change NICs prior to install.

You said you use static addressing so it shouldn't be a DHCP problem, but it could be a Port problem, change the port that the Client plugs into on the Router/Switch/Hub.

If you are using a Switch/Router Re-initialize it after changing ports. Routers and smarter switches will keep track of which IP is in which Port, Re-Initialize it, or unplug it, and plug it back in.

I hope these help. If not let me know and i'll come up with something better.

-Earthworm

by bwalker

Well folks, the problem forced itself into resolution. The domain application suffered DB corruption and the shift manager took out the server before I could show up. Amusingly enough, the box in question started logging onto the controller again. I wasn't around to view the first logon attempt after server restart, but when the shift was over and I went to start dorking with it again, logon script is running!! Any reasonable excuse as to why the server rebooting changed anythng...remember, all boxes use same logon/password but only one always failed...gets the points.

by bohicam1

If it was only the one box in question, as opposed to the last one trying to access the share I would say the problem was with the logon box itself. Can you recall what the box looked like? Was there a line for username and password or were there lines for username, password AND domain? If domain is not an option, then the box just logs into itself, not to the controller.
Good luck!

Mike

by shanghai sam

I tried it both with the Windows Family Logon (which does in fact logon to the controller so long as you have also installed the following) as well as Client for Microsoft Networking (if you have have the former set as default, will not ask for domain but will logon to the domain configured for Client).
Thanks for the thoughts...I am suspecting that the box was logged on when some nearby equipment was moved and physically lost the connection briefly...since there is only one logon name andno password, somehow the server remembered connection by computer name and didn't want to establish a new connection that it thought was still connected...I have never heard of such a thing, but there it is.

by bwalker

Have tcpip running over netbios...have never used Wins...still don't and authenticates fine now...please see response to answer 4...Thanks for your response

This discussion is closed to new replies.