Article ID: 260231
Article Last Modified on 2/20/2007
APPLIES TO
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows 2000 Professional Edition
This article was previously published under Q260231
SYMPTOMS
A computer that is running Windows 2000 Professional cannot join a Microsoft Windows NT 4.0-based domain using a third-party Domain Name System (DNS) server if the SRV resource records are not supported.
This is a new feature in Windows 2000 DNS server and in newer third-party servers that enables the ability to specify a server on a network that provides a particular service. In Windows 2000, SRV records are checked during logon for the location on the network of the Active Directory servers (the LDAP server).
CAUSE
If the SRV record is returned by the DNS server, Windows 2000-based logon clients attempt to log on to the Active Directory-based domain. If there is no DNS server specified for that computer, or if an SRV record for that service does not exist, Windows 2000 instead attempts to log on to a Windows NT-based network (this is performed by using a WINS lookup or a broadcast for a domain controller).
Windows NT 4.0 DNS servers return an error code that is explicitly checked and recognized by the Windows 2000 Logon service (Netlogon.dll) which instructs Netlogon to attempt to log on to a Windows NT-based domain. However, some third-party DNS servers may return a different error code when a request is made for a resource record that is not supported. In this case, "NOT IMPLEMENTED" is returned by the third-party DNS server, whereas the Windows 2000 Logon service checks for the "REFUSED" error code.
RFC 1035 provides the definition of the DNS message format. Response codes "NOT IMPLEMENTED" and "REFUSED" are defined as follows:
- Not Implemented - The name server does not support the requested kind of query.
- Refused - The name server refuses to perform the specified operation for policy reasons.
According to the RFC, returning "NOT IMPLEMENTED" is the correct response code when querying an unsupported type of resource record.
RESOLUTION
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Windows 2000 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this fix should have the following file attributes or later:
Date Time Version Size File name
--------------------------------------------------------
04/14/2000 02:11p 5.00.2195.2041 305,936 Netapi32.dll
04/14/2000 02:11p 5.00.2195.2041 345,872 Netlogon.dll
WORKAROUND
Use Windows NT 4.0 DNS, not specifying a DNS server on the client, or use Netdom.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
MORE INFORMATION
For additional information about how to install Windows 2000 and Windows 2000 hotfixes at the same time, click the article number below to view the article in the Microsoft Knowledge Base:
249149 Installing Microsoft Windows 2000 and Windows 2000 Hotfixes
Keywords: kbhotfixserver kbqfe kbbug kbfix kbqfe kbwin2000presp2fix KB260231
