I believe that MS recommends disabling Win9x caching in an NT domain. Also delete any local cached password files. Also check to see that "logon to NT domain" is enabled in the network properties.

Sometimes users will modify these parameters so they can work easier in a standalone mode.

Password caching is controlled through a registry entry. When it is enabled it sort of creates a local user manager for Win9x & when enabled Win9x caches it local logon ID & password. If this local ID or password becomes out of sync with the central domain's cached ID & password you get a conflict. The result will look like a lockout but in actual fact it will be rejected because of an invalid password.

[ 08. August 2002, 16:52: Message edited by: Jack Lothian ]
_________________________
Jack