This article was previously published under Q253096
This article has been archived. It is offered "as is" and will no longer be updated.
When you use the Windows 2000 support tool Nltest.exe to try to find the global catalog for a domain by specifying a NetBIOS name instead of the DNS name, Nltest.exe may generate the following error message:
DsGetDcName failed: Status = 1355 0x54b ERROR_NO_SUCH_DOMAIN
For example, this may occur if you use the NLTEST /dsgetdc:NetBIOS domain name /gc command.Nltest.exe may also generate this error message if the wrong domain is referenced in the Nltest.exe command.
You have two or more domains, Example.com and Child.Example.com. If you run the NLTEST /dsgetdc:child.domain.com /gc command, you receive the error message that is described in this article. This is because the global catalog records only exist or only are registered in the Parent\Root Domain in DNS.
To work around this problem, use the DNS domain name instead of the NetBIOS domain name or use the correct domain name in the Nltest.exe command. The NLTEST /dsgetdc:example.com /gc command returns the correct response.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
The NetBIOS name can be used to query for a primary domain controller (PDC) and Kerberos Key Distribution Center (KDC).