Cannot open Active Directory MMC on Win2000 Server

  • Thread starter Thread starter Gregg
  • Start date Start date
G

Gregg

Hello!

When I try to open AD Users/Computers, I get an error stating "Naming
information cannot be located because: Logon attempt failed. Contact your
system administrator to verify that your domain is properly configured and
is currently online."

Per article http://support.microsoft.com/default.aspx?scid=kb;en-us;329887,
I can "reset the Windows 2000 security configuration to the default values"
on the domain controller. My question, just what exactly does it reset? Does
it blow out the users and their passwords?

Thanks for helping!

Gregg Hill
 
It resets the security policy on the machine.

http://support.microsoft.com/default.aspx?scid=kb;EN-US;313222


--
--
Daniel Chang
Server Setup Team

Search our Knowledge Base at http://support.microsoft.com/directory
Visit the Windows 2000 Homepage at
http://www.microsoft.com/windows2000/default.asp
See the Windows NT Homepage at http://www.microsoft.com/ntserver/

NOTE: Please reply to the newsgroup and not directly to me. This allows
others to add to and benefit from these threads and also helps to ensure a
more timely response. Thank you!
This posting is provided "AS IS" without warranty either expressed or
implied, including, but not limited to, the implied warranties of
merchantability or fitness for a particular purpose.
The views and opinions expressed in this newsgroup posting do not
necessarily express or reflect the views and / or opinions of Microsoft.
 
Daniel,

Thanks for the response. Would you answer a few more questions, if you don't
mind, regarding the "Naming information cannot be located because: Logon
attempt failed" error.

1) What causes the failure related to this error? I am going on site
tomorrow morning, but I'd like to know the cause.
2) If I just reboot the server, will I be able to log in as the
administrator or does this error lock out the admin account? I initially got
on the system because the server was not locked.

Thanks again!

Gregg Hill
 
Gregg,

Please refer to:

257346 "Access This Computer from the Network" User Right Causes Tools Not
to
http://support.microsoft.com/?id=257346

Does this describe the situation you're in?

From the article:
The administrator who is logged on locally does not have the "Access this
computer from the network" user right. All of the tools listed in the
"Symptoms" section of this article use network API calls to operate; they do
not work because they try to access the computer from the network.

You should be able to log in locally as Administrator; it appears that the
Administratator may not have "Access the computer from the network" rights
necessary to use the AD Users/Computers tool.

HTH,

Daniel

--
--
Daniel Chang
Server Setup Team

Search our Knowledge Base at http://support.microsoft.com/directory
Visit the Windows 2000 Homepage at
http://www.microsoft.com/windows2000/default.asp
See the Windows NT Homepage at http://www.microsoft.com/ntserver/

NOTE: Please reply to the newsgroup and not directly to me. This allows
others to add to and benefit from these threads and also helps to ensure a
more timely response. Thank you!
This posting is provided "AS IS" without warranty either expressed or
implied, including, but not limited to, the implied warranties of
merchantability or fitness for a particular purpose.
The views and opinions expressed in this newsgroup posting do not
necessarily express or reflect the views and / or opinions of Microsoft.
 
Daniel,

I have the first symptom. When I went to the server, it was not locked, so I
was able to TRY to open AD Users/Computers, but received the "Naming
information cannot be located because..." error. I would like to just reboot
the server to see if anything clears up, but my fear is that if I reboot the
server, I will not be able to get back into it. We made no changes to the
server, so I cannot figure out WHY this happened in the first place.

So my question right now is, will this error prevent me from logging into
the server locally after rebooting it? I am not trying to log into via the
network, I need to make sure it will not lock me out locally upon reboot.

I am going to try the fixes in the articles...I'm just afraid of it locking
me out. I am trying to get my hands on ntrights.exe in case I do get locked
out.

Gregg Hill
 
This error shouldn't prevent you from logging into the server locally.
According to the article, the reason this occurs is because Network API
calls are made by the AD Users/Computers Tool (which appears to "access the
network" locally).

Daniel
--
Daniel Chang
Server Setup Team

Search our Knowledge Base at http://support.microsoft.com/directory
Visit the Windows 2000 Homepage at
http://www.microsoft.com/windows2000/default.asp
See the Windows NT Homepage at http://www.microsoft.com/ntserver/

NOTE: Please reply to the newsgroup and not directly to me. This allows
others to add to and benefit from these threads and also helps to ensure a
more timely response. Thank you!
This posting is provided "AS IS" without warranty either expressed or
implied, including, but not limited to, the implied warranties of
merchantability or fitness for a particular purpose.
The views and opinions expressed in this newsgroup posting are mine and do
not necessarily express or reflect the views and / or opinions of Microsoft.
 
Back
Top