Hello Scotty, I can understand the need for brute force attack protection, however when this happend to me it was when I had remotely rebooted the remote client, I clicked on connect before it had fully restarted and got the message "Team Viewer is not running ont the client" (or somethign like that), so tried again, same message, tried again and got locked out. So it was not as if I had tried quickly in sucession with incorrect credentials, it was just that the first few times TV was not fully running and able to accept connections, so really think there is a flaw in the logic somewhere. At the very least a message should be displayed on the remote client stating what has happened and allowing the user on the remote client to over rule the system and allow the connection. Also a bit disapointing it has taken so long for someone at TV to reply to this thread.
... View more
I have just had trhis problem when being impatient waiting for a machine to reboot, so not entirely sure how that is a security feature when it was not instigated by the remote machine but TV running on my laptop, just because it could not connect to the remote machine about 4 times in a row with a message similar to "Team viewer is not running on the remote computer"! This is really rubbish, please remove this "feature" (bug) or get it to work properly
... View more