Knowledge Base

No Validation When Logging on Locally to a WINS Server

Article ID: 177256

Article Last Modified on 11/1/2006

APPLIES TO

This article was previously published under Q177256

SYMPTOMS

When you attempt to log on locally to your Windows NT Windows Internet Name Service (WINS) server, you may receive the following error:

No domain controller was available to validate your logon.

CAUSE

The Netlogon service may have started before the WINS service completely started.

RESOLUTION

After you start your WINS server, give the WINS service ample time to start before logging on locally.

NOTE: The amount of time will vary depending upon the hardware and software configuration of your WINS server.

MORE INFORMATION

A correctly configured WINS server should be set to register and resolve NetBIOS names only with itself (as both primary and secondary server). The local WINS configuration information can be viewed using either of the following:

  • The WINS tab of the TCP/IP Protocol properties within the Network applet of Control Panel

    -or-
  • Ipconfig.exe /all from a command prompt.
Although this is the correct configuration for a WINS server, it is possible for the Netlogon service to start before the WINS service. As a result, the Netlogon service will not be able to resolve the DOMAIN[1Ch] entry required for domain logon validation.

For more information regarding WINS server configuration, see the following article in the Microsoft Knowledge Base:

ARTICLE-ID: 150520
TITLE : WINS Server Sporadically Loses Name Resolution

ARTICLE-ID: 150737
TITLE : Setting Primary and Secondary WINS Server Options

Keywords: kberrmsg kbnetwork kbprb KB177256


Send feedback to Microsoft

© Microsoft Corporation. All rights reserved.