Discussion Locked

Custom Password Complexity in Win2k

0 helpful
12 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have a win2k domain controller with strong password requirements enabled (Enabled via doamin GPO). I have written a custom password filter (passfilt.dll customized code provided by MS Platform SDK) and wish to have my DC now use this new filter. How does one go about having win2k use the new filter instead of the default complexity filter.

12 replies

by joseph moore

TechNet Article ID: Q161990 tells you how to modify the Registry to use the password filter file (passfilt.dll):

"1. Install the latest Windows NT 4.0 service pack.

2. Copy Passfilt.dll to the %SYSTEMROOT%\SYSTEM32 folder.

3. Use Registry Editor (Regedt32.exe) to add the value "Notification Packages", of type REG_MULTI_SZ, under the LSA key.

NOTE: If this key already exists, go to Step 4.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa

4. Double-click the "Notification Packages" key and add the following value:

NOTE: If the value FPNWCLNT is already present, place the following entry beneath the FPNWCLNT entry:

PASSFILT

5. Click OK and then exit Registry Editor.

6. Quit and restart the computer running Windows NT Server"

Ok, after that, Article ID: Q225230 talks about the GPO change:

"1. Right-click the domain object in the Active Directory Users and Computers MMC snap-in, and then click Properties.

2. Click the Group Policy tab.

3. Click the Default Domain Policy GPO link, and then click Edit.

4.Navigate to the following node in the group policy object:

Group Policy Object Policy\Computer Configuration\Windows Settings\Security Settings\Account Policies\Password Policy

5. Double-click Passwords must meet complexity requirements of installed password filter to produce the application dialog box.

6. Change the template setting to Enabled to activate the strong password requirement.

As with all policy settings, the change is not applies until the next time group policy objects are applied to your domain controllers."

Hope this helps

by lfross

Thank you; I have tried this and since it is a WINDOWS NT fix and NOT Win2k I need not discuss the results, but I do appreciate your input (the fvmclient rule i did not try so we shall see

by sativocomputerservices

If you had Novell, you wouldn't ahve this problem.... just kidding.... What you may try is using regsvr32 /u to unregister the dll and then register yours in its place. Worth a shot anyway.

by lfross

Problem 1: What dll am I unregistering;
problem 2: If I knew the name of the dll I would delete it and replace it with mine.
Thank you for your response if you know the solutions to these problems the points are yours!!!
Thanks again
Larry

by sativocomputerservices

The dll you need to unregister and delete is the same name as the dll you created (passfilt.dll). Do not run any SP's because they will replace the dll you register

by 4u21der

The answer that joseph gave is correct. That same procedure will work under win2k. But just in case you don believe me here is the MSDN article:

==
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/security/pswd_about_9xm4.asp
==

If that still does not look ok to you then just do a seach on passfilt.dll in the search box and it will bring up several articles.

The 2 things that i think you are missing, is installing and registering the dll and the fact that the passfilt.dll may not already be installed.

Hope this works...

This discussion is closed to new replies.