Re: Account Lockout Question
- From: "gmc" <gcunning@xxxxxxxxxxx>
- Date: Sun, 13 Jul 2008 21:59:20 -0400
"Al Dunbar" <AlanDrub@xxxxxxxxxxxxxxxxxxx> wrote in message
news:O8UHLpD5IHA.1892@xxxxxxxxxxxxxxxxxxxxxxx
Thanks Al. The admin team is looking at the specific account and i'll pass
Do you have any idea what is actually causing this? Is there an issue with
the application itself, or do you suspect that some entity is doing this
to either hack or deny service?
If the latter, have you considered creating a new service account and
re-configuring the application to use it instead? If this works, then I'd
assume that the problem was not with the application, and the problem
would be, effectively, solved - at least until the "entity" discovered the
new account.
Also, I'm not a group policy expert, but I had thought that things like
account lockout were implemented that way. If so, perhaps an OU could be
created or found for which lockout was nor enforced, and the account moved
there for testing.
along the suggestion of setting up a new one to help resolve the matter.
in all the reading i could do it doesn't appear as though you can have
different GPO per OU when it comes to the account lockout settings, at least
in 2003. From what i can tell it will be different in 2008 but that doesn't
help us.
best regards
Gary
.
- References:
- Account Lockout Question
- From: Gary Cunninghame
- Re: Account Lockout Question
- From: Al Dunbar
- Account Lockout Question
- Prev by Date: Re: Account Lockout Question
- Next by Date: Re: Account Lockout Question
- Previous by thread: Re: Account Lockout Question
- Next by thread: Re: Account Lockout Question
- Index(es):
Relevant Pages
|