Down-Level Domain Users May Receive an Error Message When Starting MMC Snap-Ins

View products that this article applies to.

This article was previously published under Q247151

Expand all | Collapse all

SYMPTOMS

When a domain user of a trusted down-level domain starts a Microsoft Management Console (MMC) snap-in, the following error message may be generated in a message box titled Active Directory:

Naming information cannot be located because:
The specified domain either does not exist or could not be contacted. Contact your system administrator or verify that your domain is properly configured and is currently on-line.

This error message may be generated when the down-level domain user starts one of the following MMC snap-ins:

Active Directory Domains and Trusts
Active Directory Sites and Services
Active Directory Users and Computers
Group Policy Editor
Adsiedit
Domain Controller Security Policy
Domain Security Policy
Active Directory Schema

Back to the top

CAUSE

This issue occurs because MMC snap-ins are designed to connect to a domain controller for the logged on user, or if the Netlogon service is not started on the domain controller.

Back to the top

RESOLUTION

To work around this issue if the Netlogon service is not started on the domain controller, start it. Otherwise, use any of the following methods:

Use command-line options to specify the default domain controller to make a connection with.
Use the Runas.exe tool to configure the MMC snap-in to change the context of the user.
After you click OK following the error message, you may change the focus of the MMC snap-in to a Windows 2000-based domain controller.

NOTE: This must be done during initialization each time you start the MMC snap-in.

Back to the top