Unable to Access Active Directory Users and Computers Snap-In

I'm having an issue where I am unable to access the ADUC console. When I try to bring up the ADUC I get the following error:

Naming information cannot be located because: The interface is unknown.
Contact your system administrator to verify that your domain is properly configured and is currently online.

Does anybody have any idea what might have caused this to occur?

Thanks in advance.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

If Active Directory is unavailable, the Active Directory management tools will fail when launched.

For example:


      When repadmin /showreps is run from the command prompt, it does not compelete or returns the "Cannot open LDAP connection to localhost" error.

      When Active Directory Sites and Services is started, it returns the following error:

      Naming information cannot be located because:

      The Network path was not found.

      Contact your system administrator to verify that your domain is properly

      Configured and is currently on line.

This problem can be related to incorrect TCP/IP configuration on the local domain controller, a network connection issue, a problem on the DNS server or because the NETLOGON service is not running locally.

In any of the above scenarios:

     Ensure that that the DNS server is unavailable.

     Try to ping the destination replication partner from the local domain controller.

     Use the Nslookup command to ensure that the DNS server is correctly configured on the local domain controller.
     If the problem is DNS related, flush the DNS cache on the local domain controller by using the ipconfig /flushdns   command, or stop and restart the DNS Client service. For more information about name resolution failures, see the "DNS Lookup Failure" section earlier in the chapter.

     Ensure that the NetLogon service is running properly in Administrative Tools, Services. Also check the System and Directory Service event logs in Event Viewer for events indicating errors for NetLogon.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Quick Note: schema modification issues are usually related to an account having enough rights against the DC holding the Schema Role Master (ADSRM) Role in a Forest. If you are the AD Admin you may temporarily transfer the ADSRM to a DC member of the child domain where you are trying to do the modification.

WARNING! this is a very sensitive operation and we had to perform it only under MS Tech Support shadowing and ONLY after all other paths failed (This was an EXCHANGE 2007 implementation having schema modifications issues during pre-installation AD preparation).
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.