Log On Attempt Does Not Work on Computers with Windows NT Newly Installed

ID: Q223997

The information in this article applies to:

Microsoft Windows NT Workstation version 4.0
Microsoft Windows NT Server version 4.0
Microsoft Windows NT Server, Enterprise Edition version 4.0

SYMPTOMS

When you attempt to log on to a computer that has just had Windows NT installed, the following error message may be displayed:

The system cannot log you on because the system's computer account in it's primary domain is missing or the password on that account is incorrect.

CAUSE

This problem occurs when the user is automatically required to log on to the computer immediately after the computer account has been added to the domain.

When a Windows NT-based computer joins a domain during Windows NT installation, a computer account is created on the Primary Domain Controller (PDC) computer. If the PDC is running Windows NT 4.0 Service Pack 4, the new account is not sent to each Backup Domain Controller (BDC) computer until the next scheduled replication, which has a default setting of five minutes. Prior to Service Pack 4, the PDC would replicate all machine account updates immediately.

RESOLUTION

This problem normally only occurs during the first logon after the installation of a new computer in an existing domain. This hotfix must be installed on the new computer as part of the service pack update as documented in the following article in the Microsoft Knowledge Base:

Q166839 How to Apply Windows NT Hotfixes Along w/ WinNT Service Packs

A supported fix that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next Windows NT 4.0 service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://www.microsoft.com/support/supportnet/overview/overview.asp

The English version of this fix should have the following file attributes or later:


   Date      Time     Size      File name      Platform
   --------------------------------------------------
   04/28/99  05:41p   188,176   Netlogon.dll   x86
   04/27/99  05:38p   310,544   Netlogon.dll   Alpha

NOTE: If this product was already installed on your computer when you purchased it from the Original Equipment Manufacturer (OEM) and you need this fix, please call the Pay Per Incident number listed on the above Web site. If you contact Microsoft to obtain this fix, and if it is determined that you only require the fix you requested, no fee will be charged. However, if you request additional technical support, and if your no-charge technical support period has expired, or if you are not eligible for standard no-charge technical support, you may be charged a non-refundable fee.

For more information about eligibility for no-charge technical support, see the following article in the Microsoft Knowledge Base:

Q154871 Determining If You Are Eligible for No-Charge Technical Support

WORKAROUND

To work around this problem, perform one of the following:

Add all computer accounts prior to installing Windows NT on the computers.

Use an LMHOST file that has a #PRE #DOM entry with the PDC's IP address specified.

Promote a BDC that is running Windows NT 4.0, Service Pack 3 to the PDC until all computers being added to the domain have had Windows NT installed. You can then demote the PDC to a BDC and promote the PDC with Service Pack 4 installed, or you can install Service Pack 4 on the current PDC.

STATUS

Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article.

Additional query words:


Keywords          : kbbug4.00 kbfix4.00 
Version           : winnt:4.0
Platform          : winnt 
Issue type        : kbbug

Last Reviewed: July 20, 1999