I regret that you have not been more interested in this issue, despite this I looked on my side and found the solution.
I sniffed the communication of FAF and found that the connection protocol uses a UID to identify the connecting machine. As long as this UID is associated to an account, the server doesn't accept any other account with that same UID (=on the same machine).
The trick is to free the UID by associating the account to another UID, simply by logging into the account on another machine.
Account A log in on machine 1.
Another account cannot log in on Machine 1, because machine 1 is associated with account A.
Account A log in on machine 2 => machine 1 is not anymore associated with account A
Another account can log in on machine 1.
In my case:
- I logged in on my PC.
- I logged in on the PC of my girlfriend
- My brother could log in on my PC
- I could not log in on my PC
- I asked my brother to log in on his laptop
- I could log in on my PC
Finally, it is easy to solve the problem when the process used by FAF is known. Just connect to the last used account on your PC on another PC, then you can log in with any account on your PC again.
Hope this will help other people having the same problem.Statistics: Posted by KyrO — 18 Feb 2015, 02:15
]]>