Opened 13 years ago
Closed 6 years ago
#5393 closed Bug report (invalid)
Passwords/Accounts stop working or won't work
|Reported by:||Nathan Alterman||Owned by:|
|Keywords:||user auth password auth||Cc:||natealterman@…|
|Component version:||Operating system type:||Windows|
|Operating system version:||Windows 2008 Server SP2|
We have a Filezilla Server installation on Windows Server 2008 Data Center edition SP2.
We havea about 70 FTP users connecting using Chilkat clients.
We recented changed some security issues and modified each password and added an extension to it.
All of a sudden some accounts can't log in.
In most cases if I replace the password with a completely different password and then set it back to the expected password it will work.
In some cases the very account will not work. The folder name the account points to is not changed. If I create a new account with a different name and password and point it to access the folder for the account that fails, it works fine. If I rename the now working account to the same name as the previous account that failed, it will stop working also. This have been verified more than a few times.
I have tried to find some way of "forcing a re-initialization" of the account name/passwords but I am unable to find anything.
I have scoured the forum but didn't find anythink explaining my problem except one post that says "accounts just don't stop working". But in my case, I have about 10 accounts that have stopped working and I am in the process of having to reset up all the accounts with new names and passwords.
Change History (3)
comment:1 by , 13 years ago
comment:2 by , 6 years ago
comment:3 by , 6 years ago
|Keywords:||user auth password auth added; accounts fail unexpectedly. removed|
|Status:||new → closed|
This does not sound like a FileZilla bug. It can be summarized as "We changed 70 passwords and now some accounts can't log in." In addition, the user reports that the issue was resolved by re-typing the passwords. Finally, the issue is seven years old.
I suggest closing this bug.