Microsoft KB Archive/328570

= Existing computers are not updated to the DNS-style domain name after you upgrade the domain to Active Directory =

Article ID: 328570

Article Last Modified on 2/1/2007

-

APPLIES TO


 * Microsoft Windows XP Professional
 * Microsoft Windows 2000 Service Pack 1
 * Microsoft Windows 2000 Service Pack 2
 * Microsoft Windows 2000 Service Pack 3
 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows 2000 Service Pack 1
 * Microsoft Windows 2000 Service Pack 2
 * Microsoft Windows 2000 Service Pack 3

-



This article was previously published under Q328570



SYMPTOMS
After you upgrade the domain to Active Directory, existing Windows 2000-based computers and Windows XP-based computers may not be updated to the DNS-style domain name. As a result, the servers may not receive a Kerberos ticket. If you investigate the computer account attributes for the affected computers by using LDIFDE, the dNSHostName property and the servicePrincipalName property are left blank. If you turn on auditing for logon failures, a security event ID 675 message (&quot;Pre-authentication failed&quot;) is intermittently logged for the affected computers. Users may receive the following error message:

The system cannot log you on now because the domain  is not available.

If many domain members experience this problem, you may notice that your CPU usage approaches 90% to 100% when computers change their password. The computers then send Kerberos AS requests that fail with a &quot;Pre-authentication failed&quot; error. This problem drives up the CPU load on the domain controllers, especially the primary domain controller emulator, because by default, the domain controllers forward these requests to the primary domain controller.



Windows XP
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows XP service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question. The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

  Date         Time   Version          Size     File name    Platform 28-May-2003 21:46  5.1.2600.1227  1,046,016  Netlogon.dll   IA64 28-May-2003 21:39  5.1.2600.1227    387,584  Wnetlogon.dll  IA64 28-May-2003 21:46  5.1.2600.1227    387,584  Netlogon.dll   x86

Service Pack Information
To resolve this problem, obtain the latest service pack for Microsoft Windows 2000. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

260910 How to obtain the latest Windows 2000 service pack

Hotfix Information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows 2000 service pack that contains this hotfix.

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 about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

  Date         Time   Version            Size    File name --  30-Sep-2002  16:46  5.0.2195.6069     124,176  Adsldp.dll 30-Sep-2002 16:46  5.0.2195.5781     131,344  Adsldpc.dll 30-Sep-2002 16:46  5.0.2195.5781      62,736  Adsmsext.dll

30-Sep-2002 16:46  5.0.2195.6052     358,160  Advapi32.dll 30-Sep-2002 16:46  5.0.2195.6058      49,424  Browser.dll 30-Sep-2002 16:46  5.0.2195.6012     135,952  Dnsapi.dll 30-Sep-2002 16:46  5.0.2195.6012      96,016  Dnsrslvr.dll 30-Sep-2002 16:46  5.0.2195.5722      45,328  Eventlog.dll 30-Sep-2002 16:46  5.0.2195.6059     146,704  Kdcsvc.dll 05-Sep-2002 23:18  5.0.2195.6048     200,976  Kerberos.dll 21-Aug-2002 14:27  5.0.2195.6023      71,248  Ksecdd.sys 26-Sep-2002 00:01  5.0.2195.6072     507,664  Lsasrv.dll 26-Sep-2002 00:01  5.0.2195.6072      33,552  Lsass.exe 27-Aug-2002 20:53  5.0.2195.6034     108,816  Msv1_0.dll 30-Sep-2002 16:46  5.0.2195.5979     307,472  Netapi32.dll 30-Sep-2002 16:46  5.0.2195.6075     360,720  Netlogon.dll 30-Sep-2002 16:46  5.0.2195.6048     918,800  Ntdsa.dll 30-Sep-2002 16:46  5.0.2195.6025     389,392  Samsrv.dll 30-Sep-2002 16:46  5.0.2195.5951     129,296  Scecli.dll 30-Sep-2002 16:46  5.0.2195.5951     302,864  Scesrv.dll 30-Sep-2002 16:46  5.0.2195.5859      48,912  W32time.dll 04-Jun-2002 19:32  5.0.2195.5859      57,104  W32tm.exe 30-Sep-2002 16:46  5.0.2195.6052     126,224  Wldap32.dll 26-Sep-2002 00:01  5.0.2195.6072     507,664  Lsasrv.dll

Note Sometimes, if you install this hotfix after you perform the in-place upgrade, the problem is not resolved. You may have to perform a manual computer account password reset for the account. For domain controllers, use the netdom resetpwd command. For domain members, use the nltest /sc_change_pwd command. The automatic computer account password change that occurs every 30 days (the default interval) may also resolve this problem.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Windows 2000 Service Pack 4.



MORE INFORMATION
For more information about how to obtain a hotfix for Windows 2000 Datacenter Server, click the following article number to view the article in the Microsoft Knowledge Base:

265173 The Datacenter Program and Windows 2000 Datacenter Server product

Keywords: kbbug kbfix kbwin2000presp4fix kbqfe kbdirservices kbhotfixserver KB328570

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.