Account lockout problem! Help! (I don't think its Q262653 related)

Account lockout problem! Help! (I don't think its Q262653 related)

Post by Chri » Tue, 06 Jun 2000 04:00:00



Hi

We have a SMS2.0 SP1 site and are experiencing problems with the SMS account
locking itself out. This account is used by the SMS Executive and site
system communication. For some reason this account continues to lock itself
out. I have reset the password in UMFD and SMS. To try and avoid this
situation, I created more site system connection domain accounts for SMS to
use in case one is locked out. I don't really think this problem has
anything to so with Q232653 -
Its strange because the Administrator account for the domain continues to
lock itself out too!?

I am open to any suggestions and help -

Is it a rogue service causing this? Would a site reset help??!

TIA

Chris

 
 
 

Account lockout problem! Help! (I don't think its Q262653 related)

Post by Douglas Leon » Tue, 06 Jun 2000 04:00:00


I ran into this problem where I am. I traced it to 3 PC's witch were
using the account via the SMS client software.

Do not specify the SMS clients in any way to use the smsservice
accounts.
There are smsclitokn and smsclisvc accounts that the sms client will
use.

The way I found out what had happened is that the errors were logged in
the event viewer because we had AUDITING turned on for login failures.

I hope this helps.

 
 
 

Account lockout problem! Help! (I don't think its Q262653 related)

Post by Chri » Wed, 07 Jun 2000 04:00:00


the clients were not modified in any way beyond the default installation -
as far as I can tell they are using the SMSClitok and SMSClisvs as designed.

How could you tell which machines were failing authentication with the
suspect service account?


Quote:> I ran into this problem where I am. I traced it to 3 PC's witch were
> using the account via the SMS client software.

> Do not specify the SMS clients in any way to use the smsservice
> accounts.
> There are smsclitokn and smsclisvc accounts that the sms client will
> use.

> The way I found out what had happened is that the errors were logged in
> the event viewer because we had AUDITING turned on for login failures.

> I hope this helps.