Article ID: 328283
Article Last Modified on 10/30/2006
APPLIES TO
- Microsoft Windows 2000 Service Pack 1
- Microsoft Windows 2000 Service Pack 2
- Microsoft Windows 2000 Service Pack 3
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows 2000 Advanced Server
This article was previously published under Q328283
SYMPTOMS
You may experience a problem when you are running the Active Directory Users&Computers snap-in on a computer that does not point to itself for DNS resolution. When you open user objects, queries are sent to the DNS computer with a name that is not valid. This occurs although you can see the DNS computer in a Network Monitor trace.
The name that is not valid is the FQDN of the domain controller that the snap-in is pointed at and that is used as a domain name. For example, your domain controller is named mcdc1.child.root.com. The DNS query is for the _ldap._tcp.dc._msdcs.mcdc1.child.root.com name.
CAUSE
The dialog box for the dial-up properties does not specify ADS_SERVER_BIND when it connects to domain controllers. For additional information about functions that generate incorrect DNS queries, click the article number below to view the article in the Microsoft Knowledge Base:
258507 ADsOpenObject(), ADsGetObject(), OpenDSObject() Functions May Generate Incorrect DNS Queries
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
Additional query words: dsa.msc
Keywords: kbwin2000presp4fix kbenv kbprb kbpending KB328283
