No Domain Server....

On a few of our Win 95 workstations, we get the following error when the user tries to log in : "Microsoft Networking : No domain server was available to validate your password. You may not be able to gain access to some network resources".  If we delete the TCP/IP protocol and then re-add it, identical to what is was, we can log in OK.  This only happens occasionally and only on a few workstations.
Who is Participating?
livniConnect With a Mentor Commented:

Last reviewed: October 17, 1997
Article ID: Q152791 The information in this article applies to:

•Microsoft Windows 95 •Microsoft Windows 95 OEM Service Release version 2


When you attempt to log on to a Microsoft Windows NT domain using only the TCP/IP protocol, the domain controller may not be found, generating the following error message:

   No domain server was available to validate your password.  You
   may not be able to gain access to some network resources.

After this occurs, you cannot log on to the domain until you restart your computer.


This problem can occur when the NetBIOS interface for TCP/IP (VNBT) is unable to allocate a buffer needed while you are logging on. This is more likely to occur in low-memory conditions.


Microsoft has confirmed this to be a problem in Microsoft Windows 95 and OEM Service Release 2 (OSR2). An update to address this problem is now available, but is not fully regression tested and should be applied only to computers experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft does not recommend implementing this update at this time. Contact Microsoft Technical Support for additional information about the availability of this update.
Is the traffic level of your network high, or your Domain Controller very busy when this happens?  It is possible that the workstation is timing out on its authentification request because the server or network is too busy to respond in time.  Are you running DHCP?  Does cold booting help after you get the error message?  It is also possible that TCP/IP stack is getting corrupted.  It could be a number of things.
Similar messages I have seen on NT m/cs with text as "Not able to login to domain will use  cached account information" and after this if we check it has logged into domain.Any comments about this.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.