This article was previously published under Q272686
This article has been archived. It is offered "as is" and will no longer be updated.
On a Windows 2000-based domain controller, when you open the Active Directory Users and Computers snap-in, you may receive the following error message:
Naming information cannot be located because the specified domain either does not exist or cannot be contacted. Contact your system administrator to verify that your domain is properly configured and is currently online
When you run the Domain Controller Diagnostics tool (Dcdiag.exe) on the domain controller, you may receive the following error message:
Starting test: Services
w32time Service is stopped on server
Starting test: FsmoCheck
Warning: DcGetDcName(TIME_SERVER) call failed, error 1355 A Time Server could not be located. The server holding the PDC role is down. Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error 1355 A Good Time Server could not be located. ......................... domain.com failed test FsmoCheck
This issue can occur because either:
The Windows Time service has stopped.
In the Windows Time service on the domain controller, Startup Type is set to Disabled.
To resolve this issue, follow these steps:
Click Start, point to Programs, point to Administrative Tools, and then click Services.