When you try to join a Windows Vista-based client computer to a top level domain (TLD) that has a purely numeric suffix, the Windows Vista-based client computer cannot join the domain. Additionally, you receive the following error message:
Computer Name/Domain Changes
An Active Directory Domain Controller for the domain <DNS domain name> could not be contacted. Ensure that the domain name is typed correctly. If the name is correct, click Details for troubleshooting information.
An example of a purely numeric suffix is "contoso.2003."
When you click Details
, you receive the following error message:
An error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller of the domain domain name.
The error was: "The filename, directory name, or volume label syntax is incorrect."
(error code 0x0000007B ERROR_INVALID_NAME)
The query was for the SRV record for _ldap._tcp.dc._msdcs.domain name.com
If you try to join the domain by using the NetBIOS name of the domain, you are prompted for domain credentials. In this case, the client computer still cannot join the domain. Additionally, you receive the following error message:
The following error occurred attempting to join the domain NetBIOS name of the domain Logon failure: unknown username or bad password.
This article helps you fix the problem. To have us fix this problem for you, go to the “Fix it for me
” section. If you would rather fix this problem yourself, go to the “Let me fix it myself
To fix this problem automatically, click the Fix this problem
link. Then click Run
in the File Download
dialog box, and follow the steps in this wizard.
This wizard may be in English only; however, the automatic fix also works for other language versions of Windows.Note
If you are not on the computer that has the problem, you can save the automatic fix to a flash drive or to a CD, and then you can run it on the computer that has the problem.
Now go to the "Did this fix the problem
This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
How to back up and restore the registry in Windows
To fix this problem, add the ScreenBadTlds registry entry. Adding this registry entry prevents the client computer from performing the test to determine whether the top level domain is supported.
To add this registry entry, follow these steps.
- Click Start
, type regedit in the Start Search box, and then press ENTER.
Collapse this imageExpand this image
Note If you are prompted for an administrator password or for confirmation, type the password or provide confirmation.
- Locate and then click the following registry subkey:
- On the Edit menu, point to New, and then click DWORD Value.
- Type ScreenBadTlds, and then press ENTER.
- Right-click ScreenBadTlds, and then click Modify.
- In the Value data box, type 0, and then click OK.
- Exit Registry Editor.
Now go to the "Did this fix the problem
Check whether the problem is fixed. If the problem is fixed, you are finished with this article. If the problem is not fixed, you can contact support
This behavior is by design.
This issue does not occur with domain names that have numbers and letters in the domain suffix. For example, this issue does not occur with domain names that resemble the following:
Also, this issue does not occur with domain names that have numbers in the domain prefix. For example, this issue does not occur with domain names that resemble the following
When this issue occurs, all Domain Name System (DNS) records are returned correctly when the computer is joining the domain. In a network trace, correct records are queried for and returned. Therefore, DNS is fully functional and is not part of this issue.