Question : Workstations are getting exception errors or are locking up while connected to server

This is happening amoung both NT 4.0 and XP professional workstations while working on files located on the file server.  The users are using Quickbooks and a server application for tax processing.  I suspect it is the tax program that is causing the problem, but can't find anything on the server event viewer that helps.  

Sometimes the NT workstation gets a warning that an exception error has occurred and that they should close all programs and reboot.  Other times it just locks the workstation.  ON the XP workstations, the application just closes.  

The only thing I see in the event viewer is this "The session setup from the computer LWB failed to authenticate. The name of the account referenced in the security database is LWB$.  The following error occurred:
Access is denied."  The event ID is 5722 the source is NETLOGON.  

What to try next?

Answer : Workstations are getting exception errors or are locking up while connected to server

Knowledge Base  

Netlogon Event ID 5770 and 5722 on Primary Domain ControllerPSS ID Number: 180114

Article Last Modified on 5/14/2003


--------------------------------------------------------------------------------
The information in this article applies to:


Microsoft Windows NT Server 3.1
Microsoft Windows NT Workstation 3.1
Microsoft Windows NT Advanced Server 3.1
Microsoft Windows NT Workstation 3.5
Microsoft Windows NT Workstation 3.51
Microsoft Windows NT Workstation 4.0
Microsoft Windows NT Server 3.5
Microsoft Windows NT Server 3.51
Microsoft Windows NT Server 4.0

--------------------------------------------------------------------------------

This article was previously published under Q180114
SYMPTOMS
The following errors may occur in Windows NT when connecting to a Windows NT Workstation or a member Windows NT Server computer with User Manager or Server Manager:


The trust relationship between this workstation and the domain failed.

Additionally, the following 5770 and 5722 errors may occur in the event log on a primary domain controller:

Netlogon Event ID 5722:


The session setup from the computer CSWINS failed to authenticate. The
name of the account referenced in the security database is CSWINS$. The
following error occurred:

Access is denied.

Netlogon Event ID 5770:


The session setup to the Windows NT Domain Controller <\\server> from
computer CSWINS using account CSWINS$ failed. CSWINS2 is declared to be
a BDC in domain . However, CSWINS2 tried to connect as
either a DC in a trusted domain, a member workstation in domain
, or as a server in domain . Use the Server
Manager to remove the BDC account for CSWINS.


And the following errors will occur on the target workstation or member server:

Netlogon Event ID 5719:


No Windows NT Domain Controller is available for domain .
The following error occurred:

There are currently no logon servers available to service the logon
request.

NOTE: This event is expected and can be ignored when booting with the No Net Hardware Profile.

Netlogon Event ID 3210:


Failed to authenticate with <\\server>, a Windows NT domain controller
for domain .
CAUSE
Workstation and stand-alone server computer accounts are mistakenly treated as LanMan backup domain controllers (BDC) by the primary domain controller (PDC). LanMan BDCs are declared as such in a Windows NT domain by creating a special Windows NT global group called servers, creating user accounts that correspond to the computer names of the LanMan BDCs, and placing those user accounts in the servers group.

Authentication with the PDC fails when the accounts in the servers group are actually Windows NT workstations and servers. This is because Windows NT will use the secure channel account password against to authenticate with the PDC. The PDC finds a matching user account in the servers group for the Windows NT system and treats it as a LanMan BDC. During challenge/response authentication, the PDC uses the user account password instead of the secure channel password to authenticate the Windows NT system. This causes the errors noted in the summary.
RESOLUTION
If no LanMan BDCs exist, then remove the servers group and restart the Netlogon service on the PDC.

If LanMan BDCs exist, then remove the user accounts for the Windows NT systems experiencing this problem from the servers group. Restart the Netlogon service on the PDC.
Keywords: kbprb KB180114
Technology: kbWinNT310Search kbWinNT350search kbWinNT351search kbWinNT400search kbWinNTAdvSerSearch kbWinNTAdvServ310 kbWinNTS310 kbWinNTS310search kbWinNTS350 kbWinNTS350search kbWinNTS351 kbWinNTS351search kbWinNTS400 kbWinNTS400search kbWinNTsearch kbWinNTSsearch kbWinNTW310 kbWinNTW310Search kbWinNTW350 kbWinNTW350search kbWinNTW351 kbWinNTW351search kbWinNTW400 kbWinNTW400search kbWinNTWsearch



--------------------------------------------------------------------------------

Send feedback to Microsoft

© 2003 Microsoft Corporation. All rights reserved.