Active Directory problem

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

JoeC54 - 09 Mar 2006 14:08 GMT

I have taken over a client with SBS2000. The domain controller acts like it
doesn't know it's the domain controller. I can get AD running by using
recreatedefpol.exe tool, but then I have to reset all the service accounts
for them to run properly. 12 to 24 hours later it's back to not recognizing
itself as an AD controller. All the FSMO roles check out correct, DNS is
correct, the server points to itself as the primary DNS server, the service
records are in the zone. The error message when click on AD Users and
Computers is: Naming information cannot be located because: The logon attempt
failed.
Any help would be greatly appreciated.

Reply to this Message

Dave Nickason [SBS MVP] - 09 Mar 2006 15:23 GMT

Have you seen this article? This could be better written IMO, but it
describes a virus as the cause of this. I'm thinking that would be
consistent with the repair getting undone 12 to 24 hours later. In that
case, you'll have to get rid of the virus before the situation can be
permanently resolved. I would run a thorough scan with your AV software,
plus the malicious software removal tool from MU. Note anything found so
you can research it in case there are further steps necessary. If it's a
virus, you can probably get free support from MS at 1-866-PCSAFETY, or from
your AV vendor.

"Naming Information cannot be located" error message when you try to open
the Active Directory Users and Computers tool or the Active Directory Sites
and Services tool in Windows 2000 Server
http://support.microsoft.com/?kbid=887431

>I have taken over a client with SBS2000. The domain controller acts like it
> doesn't know it's the domain controller. I can get AD running by using
[quoted text clipped - 9 lines]
> failed.
> Any help would be greatly appreciated.

Reply to this Message

JoeC54 - 10 Mar 2006 14:43 GMT

Thanks for the info,ran a scan for virus's but the server is clean of any
virus's. Am lost at this point. Also ran the malicious tool removal, nothing
found.

> Have you seen this article? This could be better written IMO, but it
> describes a virus as the cause of this. I'm thinking that would be
[quoted text clipped - 24 lines]
> > failed.
> > Any help would be greatly appreciated.

Reply to this Message

Dave Nickason [SBS MVP] - 10 Mar 2006 16:48 GMT

Here's another one. If this doesn't help, try googling "Naming Information
cannot be located" - this is apparently not that uncommon a problem.

Windows 2000 domain controllers require SP3 or later when using Windows
Server 2003 administration tools
http://support.microsoft.com/default.aspx?scid=kb;%5BLN%5D;325465

> Thanks for the info,ran a scan for virus's but the server is clean of any
> virus's. Am lost at this point. Also ran the malicious tool removal,
[quoted text clipped - 34 lines]
>> > failed.
>> > Any help would be greatly appreciated.

Reply to this Message

Karan Rustagi - 29 Mar 2006 14:59 GMT

chk the polacdmn and poldrdmn key in the regsitry..

Reply to this Message