Err Msg: There are Currently No Logon Servers Available...

This article was previously published under Q139410
In an environment that relies on Windows Internet Name Service (WINS) toresolve NetBIOS names, the error message "There are no logon serversavailable to service the logon request" appears if you are anadministrator and you do one or more of the following:
  • You attempt to remotely administer a trusted domain. For example, you use File Manager to assign share permissions to users from the trusted domain.
  • You attempt to select the trusted domain in User Manager for Domains.
The WINS database does not have the proper domain registrations for pass-through authentication. See the more information section below for moredetails.

This problem occurs most often in environments where the administrator hascreated a two-way trust between two previously independent domains. Mostoften, there are WINS servers in each domain and the WINS servers do notreplicate their databases to each other.
To resolve this problem:
  • Allow WINS dynamic registration.

    This ensures that Domain Controllers register their DOMAIN<1C> NetBIOS names with the WINS Server.
  • Make certain that WINS database replication is successful between WINS Servers. Missing database entries for domain names may indicate Problems with the WINS Servers and replication.
To work around this problem:
NOTE: Microsoft does not recommend using static mappings in the WINS database for WINS enabled computers.

  1. Run the WINS Administration Utility to add static mappings for the Domain<1C> registrations (of the trusted domain) that are not listed in the WINS database:
          Name:        Master DOMAIN Name      IP Address:  Address of the Primary Domain Controller (PDC) of the                    domain      Type:        Domain Name  						
If you are logged on as an administrator at a Domain Controller, remoteadministration works now successfully. If you are attempting to remotelyadminister the domain while logged on to a Server (not a domaincontroller) or Windows NT Workstation, you must add DOMAIN<1C> entries forboth the trusted and trusting domains.
To remotely administer a trusted domain, several pass-throughauthentication steps must take place. If the WINS database does not havethe proper domain registrations, the pass-through authentication fails.

For example, a trust is established between DOMAIN_A and DOMAIN_B. ServerPDC_A is in DOMAIN_A and PDC_B is in DOMAIN_B. DOMAIN_A is the trusted(master) domain, and DOMAIN_B is the resource (trusting) domain. Toestablish this trust relationship, the following NetBIOS names must beresolved to IP addresses, either through WINS or broadcast:

   NetBIOS Name      Description of Use of Name   ---------------------------------------------------------------------   DOMAIN_A<1B>      PDC_B uses this to query the PDC of DOMAIN_A   PDC_A<00>         PDC_B uses this to set up a session with the PDC of                     DOMAIN_A   DOMAIN_A<1C>      PDC_B uses this to get DC list of DOMAIN_A				

With these three names being registered, and if your account hasadministrator priviledges, the trust can be established and the message"The trust relationship was established successfully" appears. When youreboot the computer, or the first time you attempt remote administration,another NetBIOS name is needed:

   NetBIOS Name   Description of Use of Name   ---------------------------------------------------------------------   DOMAIN_A<1C>   Each Domain Controller in DOMAIN_B uses this name to                  establish a secure channel with a Domain Controller in                  the trusted domain.				

The Domain Controller (DC) in the trusting domain attempts to create asecure channel with any DC in the trusted domain by making a multicastlogon request to the NetBIOS name DOMAIN_A<1C>. This logon request is partof a process that creates a Secure Channel between the two DCs. The logonID in this logon request is the inter-domain trust account for thetrusting domain, DOMAIN_B$. If there is no registration for DOMAIN_A<1C>in the WINS database the error message STATUS_NO_LOGON_SERVERS is returnedto the call. The message "There are currently no logon servers available"is then returned to the user.

For additional information about special NetBIOS name registrations inWINS, please see the following article(s) in the Microsoft Knowledge Base:

ARTICLE-ID: 119495
TITLE : List of Names Registered with WINS Service
prodnt winfile netlogon trusts access denied

Αναγνωριστικό άρθρου: 139410 - Τελευταία αναθεώρηση: 11/01/2006 04:37:58 - Αναθεώρηση: 2.1

Microsoft Windows NT Workstation 3.5, Microsoft Windows NT Workstation 3.51, Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Server 3.5, Microsoft Windows NT Server 3.51, Microsoft Windows NT Server 4.0 Standard Edition

  • kbnetwork KB139410