First, is there any Group Policy object that could be affecting the OU or Site this Win2K machine is in. A Site or OU GPO will override the domain and local policy. So, I would check higher up on the authority ladder first. Maybe another system admin imposed the password complexity.
In the meantime, here are the stats on Windows password complexity:
1. Passwords must be at least six (6) characters long.
2. Passwords must contain characters from at least three (3) of the following four (4) classes:
English upper case letters A, B, C, ... Z
English lower case letters a, b, c, ... z
Westernized Arabic numerals 0, 1, 2, ... 9
Non-alphanumeric ("special characters") such as punctuation symbols
3. Passwords may not contain your user name or any part of your full name.
Windows 2000 incorporated the NT4 password complexity filter (passfilt.dll) as a standard feature. In NT, it was optional (and did not even exist until NT SP2). The filter is very nice, once you train your users on its requirements.
Here is a TechNet article on the password complexity filter, with a note on Windows 2000:
http://support.microsoft.com/support/kb/articles/Q161/9/90.ASP
(please remove any spaces).
Now, IF there is no GPO farther up the chain in your network, then the last place I would check is to see if passfilt.dll was manually added to your Win2K box. As I understand it, it will work, but it might not show up under the local group policy objects. So, if no GPO, then go to the Registry location listed in the TechNet article and see what is there.
Hope this helps.