17 replies
Use the start-find-files to find *.pwl and then erase these files. They are a local copy of your password and will be recreated at your next log-on. If the pwl file is out of sync with the domain password you will have the problem that you are describing. Also, make sure that in network properties that the log-in to NT domain box is checked.
Don
by dandb
by vue
First I would try log onto the server with this user and password from different work station and see it ok. In either way I would check the procedure below on a working pc.
1. Goto Network/Configuration.
2. On Primary Network Logon should have: "Client For Microsoft Network"
3. Double-Click on Client For Microsoft Network and:
4. Put a check on the box for: Log onto Windows NT Domain.
5. Windows NT Domain (line): should be your domain.
Good luck.
by dandb
by mattblakk
by dandb
by mpdcsup
by dandb
by mpdcsup
I only have a few other possibilities in mind without having the ability to tinker.
Case sensitivity: User ID's are case insensitive (as are passwords on Win95).
Two logon schemes:
The .pwl files are used if you're using the Windows Logon (the one with only two fields). The User ID and password entered here are used to unlock the .pwl file. The .pwl contains ID, password and domain for NT authentication and the User ID and password here may be different!
If you're using the MS Networking Logon, then Win95 has to have NetBIOS resolution. If the PDC is not on the local subnetwork, you have to have NetBIOS over IP enabled and you have to provide a way to do name resolution; either WINS or LMHOSTS (with valid #PRE and #DOM directives) should be configured. If it is on the local subnet, try installing NetBEUI.
Don't assume that since other computers connect okay that an identical configuration should work. NetBIOS name resolution is a living, breathing entity (a dynamicdatabase based mostly on self-discovery). You may need another mode of configuration before the NT domain sees the new machine.
Don't say none of this makes a difference because you use DNS -- DNS can't do NetBIOS name resolution (even though there are configuration dialogs that ask if you want to enable such a thing).
Look and see if your working Win95 machines have a file called c:\windows\LMHOSTS and if they do, copy it to the *failing* Win95 machine.
My gut tells me once you get the network to see the client, you'll be able to configure this machine exactly as the others -- but getting there may require a jump-start.
Win95/WinNT authentication is more complicated than pure WinNT authentication.
by mpdcsup
by mpdcsup
by mpdcsup
by mpdcsup
by dandb
by ezmoney
Have you tried deleting the computer account on the PDC and then recreating it? If not shut the offending system down then remove the computer account and then power up the offender. You must have administrator rights to do so.
Good luck
by dandb
by dandb
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending