Guest_imported
New member
- Jan 1, 1970
- 0
I am running my company's server on Win 2000 Server edition, and I recently reset the Administrator password using Active Directory Users and Computers (the server was already logged in as Administrator but I needed to the password to run a scheduled task). So I changed it to something I knew, but did not ever log off the server. The scheduled task works with the new password, and I can use the new administrator password to connect to the server from other (NT) machines. But now, even though I am still logged on as Administrator on the server, I can no longer access the important functions (Active Directory) under administrative tools to look at users or anything. Here is the main question: If I log the server off and back on with the new password, will this solve my problem and will I have access to these features again? The reason I have not yet done this is that I am afraidthat there Is some higher level Administrator password that I do not know and I won't be able to get the server back up at all. Incidentally, at least one other machine that is also logged in as Administrator and has not been logged off since the change cannot connect to the server (if I try administrator, it says "incorrect password or unknown user name", and if I try another known user just on this same machine I get a credentials conflict. I think maybe the change has not been recognized by these machines but I won't log off unless I am confident I can get back on.
Other questions: Is this typical of Administrator passwords, i.e. they do not take full effect until the Administrator logs off and back on (even on the server)? Like I said, I can use the password on (operator level user) machines that have logged on/off since I did this. Also, why is it that other things like scheduled task (run from the server!) work with this password, but critical AD functions give me a login error when I try to access them? If I log off and cannot log back on as Administrator, what can I do to recover Administrative control over the server?
I would greatly appreciate any of your help. Thank you.
Other questions: Is this typical of Administrator passwords, i.e. they do not take full effect until the Administrator logs off and back on (even on the server)? Like I said, I can use the password on (operator level user) machines that have logged on/off since I did this. Also, why is it that other things like scheduled task (run from the server!) work with this password, but critical AD functions give me a login error when I try to access them? If I log off and cannot log back on as Administrator, what can I do to recover Administrative control over the server?
I would greatly appreciate any of your help. Thank you.