Account gets locked out
Results 1 to 4 of 4

Thread: Account gets locked out

  1. #1
    Registered User
    Join Date
    Feb 2000
    Location
    Tolland, Ct.
    Posts
    60

    Post Account gets locked out

    We have a classroom with 24 PCs logging on to the server with the same username and password. They are all set to autologon, not allowed to log off, and no password required when waking. The account constantly gets locked out, often when we are right in the classroom checking out the machines. All the machines can be up and running, and when we reboot one, the account is locked.

    McAffee is using the logged on account for updates. No services are running which should submit a password. The event logs show nothing indicating a logon problem. How would we set up a log to monitor any attempts to log onto this account from anywhere in the school? Any suggestions would be appreciated.

  2. #2
    Registered User HIESLanMan's Avatar
    Join Date
    Feb 2001
    Location
    Atlanta, GA
    Posts
    154

    Post

    If you enable logging on the server, you should be able to pick up any unsuccessful attempts to log on. Unfortunately, this still doen't give you much information. In the meantime, you might up the number of unsuccessful attempts before lockout (if this doesn't too greatly affect the other accounts on your network). You an also make a policy to prohibit that account fromm logging on from other computers, I think. I'm not positive that this would prevent the account from locking, but it might.
    a LARTing we will go
    a LARTing we will go
    hi-ho the derrio
    a LARTing we will go

  3. #3
    Banned Ya_know's Avatar
    Join Date
    Jun 2001
    Posts
    10,692

    Post

    Which version of NT controls your domain?

    If win 2k:
    To limit that stations the user can login from, it is done in AD users and computers. For the user, under the Account tab, the Log on To button, you can specify the systems in the classroom only.
    You could also put this user in a different container, copy an inherited Group policy, giving it a new name. Then take out the account lockout policy function, or change the duration amounts as suggested (good for troubleshooting). Don’t forget to “block policy inheritance” for this containers group policy to make it stick for the users within. Doing it this way will keep you from changing these settings for the entire domain, and may get you by...

    This is not what you are asking for, It is more of a work around. Good luck finding the problem…

  4. #4
    Registered User
    Join Date
    Jan 2001
    Location
    Scotland
    Posts
    468

    Post

    Have you got sufficient licences on your server for the amount of machines you've got?

    Good luck!

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •