JSI Tip 3304. The specified domain either does not exist or could not be contacted?

When you attempt to join a Windows 2000 based computer to a domain, or use Dcpromo topromote a new domain controller, you receive:

The specified domain either does not exist or could not be contacted.

The System Event log may contain:

Event 7013 - Logon attempt with current password failed with the following error:
Logon failure: unknown user name or bad password.

When you run Dcdiag on the domain controller, you receive Sysvol errors. When you attempt to resolve any FSMO roles, you receive error 1355.

These problems can occur if the Sysvol folder is NOT shared on the domain controller.

NOTE: This behavior can occur if the DNS Server address points to your ISP's DNS server.

NOTE: Do NOT use Windows Explorer to share the Sysvol. See Knowledge Base article Q257338 - Troubleshooting Missing SYSVOL and NETLOGON Shares on Windows 2000 Domain Controllers.

If the Sysvol is not shared, use Regedt32 to navigate to:

HKEY_LOCAL_MACHINESystemCurrentControlSetServicesNetlogonParameters

Double-click the SysvolReady value, and change the data value from 0 to 1. Shutdown and restart the domain controller.

When the computer has restarted, open a CMD prompt and type:

nslookup and press Enter.

set q=srv and press ENTER.

_ldap._tcp. where is the domain controller'sFully Qualified Domain Name.

To verify that the Sysvol folder is shared, you can either open Windows Explorer, or type net share at a CMD prompt. By default, the Sysvol share is located in the %SystemRoot%SysvolSysvol folder. You should also check the File Replication Service event log. When replication has completed, on a domain with just one domain controller, Event 13516, The File Replication Service has stopped preventing the computer from becoming a domain controller, should be logged.