Discussion Locked

Win 95 won't authenticate on NT domain

0 helpful
17 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have a Windows 95 (Danish version) computer that cannot authenticate on our NT4.0 domain. This system has authenticated before, but has stopped. I can open a dos window and ping the PDC and BDC and all other systems on our network using either IP address, or system name. I can ping this system from other systems on the network. When I try to log onto the NT domain, I get an error back saying that (rough Danish translation) it cannot find a domain controller or the username password is incorrect. I have verified usernames and passwords used so I know they are correct.

17 replies

by don christner

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

The problem isn't with logging on locally. I am logging into a domain with a domain username and a domain password. Since I'm willing to try anything, I did delete the *.pwl files anyway, but it didn't help.

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

This stuff has all been checked, changed, re-checked, and compared to another 95 computer in our domain. It is all as it should be. Thanks for the try though.

by mattblakk

Just for kicks, right click on Network Neighborhood and choose properties. Check and make sure everything is OK. Often, I find it will then reinstall some drivers even though I haven't changed anything, and will then resume working.

by dandb

I have checked the settings here about 50 times. I have changed them several times. I have changed the IP address just to see if there may be another device on our network causing a conflict. I have removed the network card (both physically, and the drivers) and re-installed them. The network is working fine as far as I can tell, it's just the authentication that doesn't seem to be happening.

by mpdcsup

If none of the other users' suggestions have helped to this point, check the TCP/IP settings on the Win95 machine. If you are using DHCP to configure WINS, be sure the "Use DHCP" check box is selected at the bottom of the WINS tab on the TCP/IP Settings Dialog, otherwise, be sure the IP address of (at least) the Primary WINS Server points to a machine running WINS or forwarding WINS.

by dandb

I'm not using DHCP, nor WINS. I'm using DNS. I did set up the PDC to be a WINS server, and set it's address in the win95 computer. This did not help either. Thanks.

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

When I say above, "...the User ID and password here may be different!" I mean they are allowed to be different.

by mpdcsup

In addition to getting the network to see the client (above) the client has to rely on it for naming.

by mpdcsup

Windows 95 machines don't get computer accounts in an NT Domain. They are not allowed to participate in implementing domain security.

by mpdcsup

Make sure the Workgroup that the Win95 client belongs to is the same name as the WinNT domain.

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

This discussion is closed to new replies.