Discussion Locked

Cannot log in on the NT domain server

0 helpful
4 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I want to add a new user to the domain, I successfully added it but the client computer or prompts that the password is not correct. I check it many times to be exact 12 times and still same prompt. Old accounts are perfectly working, how is that so?
Is there a way an Administrator to lock the newly added user? (yes, new user account can be seen but password is blocked) if there is, I ask for the solution to UNLOCK it.
Note: Administrator left the scenario to me - i am now the new admin.

4 replies

by aclopez5

Strange problem. One thing comes to mind: are the workstation Windows 2000? If they are, then I would check the event log and make sure your old accounts are REALLY authenticating properly. Windows 2000 professional will NOT report a "Domain Controller Not Found" error message if the user has logged in before. It will simply log them in using cached information. I saw this happen once when a workstation was a member of a domain that was retired (the workstation was never moved to the new domain). The user had no problem until they changed their password. The workstation continued to recognize the old password, but not the new one. By looking at the event viewer, I realized that the workstation had not been authenticating to the domain for months, but was still accessing other network resources using it's cached profile.

by jbjerome

I have a computer running WinXP Pro that is replacing an NT4 unit. However, the network domain is an NT4 server, running SP6. I have been very unsuccessful thus far getting the machine to connect to the server and thus be able to access various netwrok resources.

I have tried specifying logging on to the correct domain name in network properties and supplying the username and password; the only message I get is that access is denied.

Any ideas?

by ctooze

From your question it's not clear if you've actually joined the workstation to the domain properly ie System props -> Computer Name -> Rename Computer or join a domain. You will need the correct level of rights in order to do this though.

by arthurp

Assuming that your profile is not held upon the computer ...

I've one question ... Can you log into the system ?

If the answer is yes, then you have conducted the acid test & everything is working ... except the user's account is diabled.

I've occassionally seen this problem, where for some reason the system has not been able to log onto the domain.

The resolution that I use is ...

* Place the computer into a workgroup, and reboot
* you will then need to log into the system with
as the local administrator
* rename the computer, in accordance with your policy and reboot
* re-introduce the computer to the domain,
ensuring that you create the account upon the
domain .. ensuring that you have the correct
admin rights
* again reboot the computer

** Upto this point you will need to log into the
system as the local administrator

* once the system has booted correctly & you have
confirmed that you are connected to the network
reboot the system
* log in using your personal profile - this will
ensure that the system is connected to the
network
* reboot and ask the user to log in ...

If this fails take a look at the network adapter properties, and the bonding (right click network neighbourhood & select properties, ensuring that the network card is both enabled and the uppermost item on the list, (with the exception of remote services)

The most likely reason that the older profiles are working, is because of the information storage, (remembering the user's password ect - for local use).

Hopefully this will work for you

Arthur

This discussion is closed to new replies.