Microsoft KB Archive/247975

From BetaArchive Wiki
Knowledge Base


Strong Passwords May Contain Parts of the Full Name

Article ID: 247975

Article Last Modified on 11/1/2006



APPLIES TO

  • Microsoft Windows NT Server 4.0 Standard Edition
  • Microsoft Windows NT Server 4.0 Enterprise Edition



This article was previously published under Q247975

SYMPTOMS

Windows NT 4.0 Service Pack 2 includes a new feature that forces users to use strong passwords. For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

161990 How to Enable Strong Password Functionality in Windows NT


The strong password policy states that the password may not contain your user name or any part of your full name; however, this does not hold true. For example, a user who is named "Userfirstname Userlastname" can successfully create the password "xxx*Userlastname123."

RESOLUTION

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem.

To resolve this problem, 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:

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-language version of this fix should have the following file attributes or later:

   Date         Time     Size     File name      Platform
   ------------------------------------------------------
   12/06/1999   02:35p    7,952   Passfilt.dll   x86
   12/06/1999   02:34p   13,072   Passfilt.dll   Alpha
                



STATUS

Microsoft has confirmed that this is a problem in Windows NT 4.0.

Keywords: kbhotfixserver kbqfe kbbug kbfix KB247975