SMS 2.0 Password Lockouts

[Trunk]

Anyone seen this.............<br><br>SMS 2.0, Single Site/Single Domain.&nbsp;&nbsp;On occasion a user may have to go use another PC to do his/her work.&nbsp;&nbsp;After a time, the users domain password expires and they change it.&nbsp;&nbsp;Now the other PC's he/she previously used bang away trying to attach to the CAP using to user's ID and old password, even if someone else has logged into that PC.&nbsp;&nbsp;This causes the user's domain account to become locked out.&nbsp;&nbsp;This only happens on occasion.&nbsp;&nbsp;Over a period of time, I have logged into numerous machines, with password changes in between, and have never experienced this problem.&nbsp;&nbsp;However, it does occur occasionally for other users. <p>Tom Thaden<br><a href=mailto:thadents@usano.ksc.nasa.gov>thadents@usano.ksc.nasa.gov</a><br><a href= > </a><br>

 

[SMS2]

Hi,<br><br>Maybe some idea:<br><br>The client software uses normally the SMSClient_&lt;sitecode&gt; account to contact the CAP. This account is maintained (password changed) by SMS. If the client temporarely has lost this password, it tries any account he knows.<br>Check the SMSCLient_&lt;sitecode&gt; account. This account should never be locked out.<br><br>To avoid connection accounts issues, create a second client connection account. Watch out, when you ccreate it in the SMS console, you still have to create it in NT manually.