Article ID: 258832 - Last Review: October 31, 2006 - Revision: 2.1 Cannot Join Windows 2000 Client to a Windows NT DomainThis article was previously published under Q258832 For a Microsoft Windows XP version of this article, see 314366
(http://support.microsoft.com/kb/314366/EN-US/
)
.
SYMPTOMS
A Windows 2000-based computer may be unable to join a Windows NT 4.0-based domain. When you attempt to change the domain membership for the Windows 2000-based computer in the Identification Changes dialog box, you receive the following error message:
Network Identification: The following error occurred validating the name "domain name". The specified domain either does not exist or could not be contacted.
System error 53 has occurred. The network path was not found. CAUSE
This problem can occur if both of the following conditions exist:
This problem can also occur if WINS is not enabled on the Windows 2000-based computer that you want to join the domain, and the Windows 2000-based computer is located in different TCP/IP subnet than the Windows NT 4.0 PDC. See the "More Information" section for details. RESOLUTION
Enable NetBIOS over TCP/IP on the workstation:
MORE INFORMATIONFor additional information about how to enable NetBIOS over TCP/IP with Windows 2000, click the article number below
to view the article in the Microsoft Knowledge Base:
204279
(http://support.microsoft.com/kb/204279/EN-US/
)
Direct Hosting of SMB Over TCP/IP
Some third-party DNS servers may cause this issue. For additional information, click the article number below
to view the article in the Microsoft Knowledge Base:
256083
(http://support.microsoft.com/kb/256083/EN-US/
)
Error Message: The Specified Domain Either Does Not Exist or Could Not Be Contacted
If WINS is not enabled on the Windows 2000-based computer that you want to join the domain and the computer is located in different TCP/IP subnet than the Windows NT 4.0 PDC, you can configure the computer to use the LMHOSTS file for NetBIOS name resolution. The computer that you want to join the domain must be able to find the PDC of that domain across subnets. To do so, it can look up the hexadecimal 1B registration for the domain name in its NetBIOS cache or on a WINS server to locate the IP address for the PDC. For additional information, click the article numbers below to view the articles in the Microsoft Knowledge Base: 180094
(http://support.microsoft.com/kb/180094/EN-US/
)
How to Write an LMHOSTS File for Domain Validation
140476
(http://support.microsoft.com/kb/140476/EN-US/
)
How to Install a BDC in a Routed TCP/IP Environment
To join a Windows 2000 Professional-based client to a domain:
| Article Translations
|
Back to the top
