We have had a very strange issues related to the most recent Serv-U update in June (18.104.22.1686) which started yesterday 26th September out of nowhere, no changes were made..
See this thread for the details relating to the password encryption method change in the update from 22.214.171.1246, we've had this update in place for months with no issues but now...
Accounts using Public Key authentication to connect to Serv-U suddently were not able to connect AND their accounts were becoming disabled. Users do not have automatic disabling set on their account, Serv-U is doing this all by itself.
After lots of testing, it appears that when an account has been connecting using a key, Serv-U still has the old password format/encryption method associated with that user's account (in the user's Archive file), even though they are not using a password to connect. Something in the Serv-U code seems to have enforced that accounts with this get DISABLED when they try to connect, even with a key (specifically on 26th September). The administrator when has to manually reactivate the account but as soon as they try to login again, it gets disabled. We also saw one instance where the GROUP that the user belonged to also go disabled, which disables all other users in that group.
The only way to fix this is to set a new password on the account but I have hundreds of accounts this could have happened to and it is near impossible to work out which accounts are affected.
Please can you let us know if there is something in Serv-U for this specific date and how we can fix this issue, is there a patch?
Thank you for your help.
chrisrowYou may get this issue too based on our previous discussions on the other thread linked above.