Article ID: 283133 - View products that this article applies to.
This article was previously published under Q283133
NoticeThis article applies to Windows 2000. Support for Windows 2000 ends on July 13, 2010. The Windows 2000 End-of-Support Solution Center
(http://support.microsoft.com/?scid=http%3a%2f%2fsupport.microsoft.com%2fwin2000)is a starting point for planning your migration strategy from Windows 2000. For more information see the Microsoft Support Lifecycle Policy
When you attempt to run the Active Directory Installation wizard (Dcpromo.exe) for a new domain controller or you attempt to join a computer that is running Windows 2000 Server or Windows 2000 Professional to a domain, you may receive the following error message:
The system log may report the following information:
The specified domain either does not exist or could not be contacted
If you run the Dcdiag tool on the domain controller, you may also receive Sysvol errors, and you may not be able to resolve any operation manager roles. When you attempt to resolve these roles, you receive an "error 1355" message.
Event 7013 - Logon attempt with current password failed with the following error:
Logon failure: unknown user name or bad password.
This issue can occur because the Sysvol directory is not shared out on the domain controller.
To resolve this issue, share out the Sysvol directory. However, it is recommended that you enable the system to share this directory. It is not recommended that you share out this directory by using Windows Explorer.
For additional information about enabling the system to share this directory out on its own, click the article number below to view the article in the Microsoft Knowledge Base:
257338To verify that the Sysvol directory is shared out, you can either open Windows Explorer, or type net share at a command prompt to see if the Sysvol share is showing. By default, the Sysvol share is located in the following folder: %SystemRoot%\Sysvol\Sysvol.
(http://support.microsoft.com/kb/257338/EN-US/ )Troubleshooting Missing Sysvol and Netlogon Shares
It is also recommended that you check the File Replication Service log. When replication has completed (with a domain with just one domain controller) the File Replication Service log reports the following event:
The system volume can take some time to initialize depending on the network.
Event 13516: The File Replication Service has stopped preventing the computer from becoming a domain controller.
This issue may still occur even though the following tests are successful: