General discussion

  • Creator
    Topic
  • #2135245

    W2k password chg

    Locked

    by wj ·

    I have W2kPro clients in a NT4 network that have problems when they change their passwords. They recieve the notification that the password is about to expire and proceed to change it from that prompt. Their account seems to get locked when that happens but they are not locked out of their local machine only from network resources. Any ideas

All Comments

  • Author
    Replies
    • #3617347

      W2k password chg

      by caper ·

      In reply to W2k password chg

      I had a similar problem. They have no access to the network resource…sync the passwords and double check user has permission to change password. I have the “official” fix and can add it here when I get back to work on Tuesday.

    • #3617333

      W2k password chg

      by wj ·

      In reply to W2k password chg

      We do the domain sync and sprinkle in reboots of the machine. After a day or 2, the problem goes away…..until the next w2k user. Thanks, I’ll look forward to your reply Tues.

    • #3641925

      W2k password chg

      by maxwell edison ·

      In reply to W2k password chg

      If you create a new user account in Windows 2000, by default the password will expire in 42 days! This can be very disconcerting to the user if they’re not expecting it. If you create a new account for a user running Windows 2000, and you don’t wantthem to call you up very distressed six weeks later, you should go into:

      Control Panel,

      Select “Users and Passwords”

      Select “Advanced User Management”

      Find the newly created account

      Check the box “Password never expires”.

      Otherwise, the client will be in for a surprise in six weeks.

      Maxwell

    • #3639987

      W2k password chg

      by wj ·

      In reply to W2k password chg

      The account is created in a Windows NT domain and we want the passwords to expire periodically. The problem occurs when it does expire, if the user changes the password from a Win2K client. There is no problem if the pwd is changed from a NT4.0 client.

Viewing 3 reply threads