Active Directory wont open

[Ulster]

Hello,

I'm trying to open Active Directory on my Primary Domain Controller but I get the following error message:

Naming information cannot be loacted because:
The Logon attempt failed

Once I "ok" this error message, AD does open but I cant connect to the Domain (even tho when I click "browse" I can see it).
It hasnt seemed to effect anyone on the network yet but I'm worried it will...

I have also seen Event ID 1000 in the application log

Has anyone had this type of problem before? I would REALLY apprecitate any information ye can give me!

Cheers,
Leon

 

[Spirit]

Sounds like you either don't have permission to veiw AD or the GC can't be resolved.

Make sure that under your prefered DNS server in the network settings is the correct one and it can resolve to the PDC emulater server.

Iain

 

[Ulster]

Cheers for the reply Iain,

The network settings seem to be correct (I'm looking at the PDC network settings so it is essentially pointing at its own IP address).
How do I check if it can resolve to the PDC emulator server?

Cheers again,
Leon

 

[Ulster]

More information:

Running netdiag, I get the following results (problems/errors only):

DC list test . . . . . . . . . . . : Failed
[WARNING] Cannot call DsBind to bardpdc.EUROPE.local (192.168.168.200)
[ERROR_LOGON_FAILURE]

LDAP test. . . . . . . . . . . . . : Passed
[WARNING] Failed to query SPN registration on DC
'bardpdc.EUROPE.local'.
[FATAL] Cannot do NTLM authenticated ldap_bind to
'w2kserver.EUROPE.local': Invalid Credentials.
[FATAL] Cannot do Negotiate authenticated ldap_bind to
'w2kserver.EUROPE.local': Invalid Credentials.
[WARNING] Failed to query SPN registration on DC
'w2kserver.EUROPE.local'.

And I'm seeing this in the event viewer:
Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1000
Date: 24/04/2006
Time: 4:20:02 PM
User: NT AUTHORITY\SYSTEM
Computer: BARDPDC
Description:
Windows cannot determine the user or computer name. Return value (1326).

Any ideas?

 

[Spirit]

Try this;

You Cannot Interact with Active Directory MMC Snap-Ins Article ID : 329887

http://support.microsoft.com/kb/329887/en-us

Regards,
Iain

 

[Ulster]

Figured it out.
Seemingly someone had changed the administrator password (through an alternate route than AD) and when I went to log in to AD it was automatically checking the username and password I was logged on as.
I was logged on as the Administrator under the OLD password (as I had not logged out after the password had been changed).
Simple log off/log in procedure cleared it up.

Just in case anyone else has this problem, make sure no one in the IT team did the above!

Simple solution in hindsight but christ it freaked me!

Cheers for your help Iain