Scotty: "Brute force" is a term that refers to password cracking, not denial of service attacks. Are you saying that a human manually tapping the refresh button 10 times in 10 seconds is enough traffic to be classified as a denial of service attack by the teamviewer network? That requires a lot more explanation before it will be plausible. But if we assume that's true, that implies the teamviewer network is way too small to meet its demands due to being underfunded or poorly architected. But let's assume that this network problem is actually intrinsic to all remote desktop systems rather than just teamviewer and any higher performance on other services is a result of them temporarily operating at a loss in order to try to compete with teamviewer. In that case, the development team should take a long hard look at the use cases "flaky or intermittent connection", "old or overburdened pc", and "intermittent pc uptime". It should be designed so people can connect and stay connected in these cases without having to manually poke the button until they get connected or banned. Or they can just keep telling their PR people to spin it as a good thing.
... View more

MK2: Who are you trying to fool? This "brute force protection" is counting connection attempts that never even got to the password exchange phase and connection attempts to computers that are assigned to us with easy access.
... View more

@mogulskier wrote: For those of you complaining about this, it's not TVs fault that there are sick people out there who get satisfaction from just causing problems for others. Think of this as protection for DoS attacks. Brute force attacks are those where someone/something is iterating through credentials and possible passwords. TV is protecting from both. This is FAR below the level of DoS. Their stated reason for this error message is to prevent password brute force attacks. The bug is that they are counting connection attempts that never even got to the password exchange phase and they are even doing this for people that are logged into accounts trying to connect to computers that are assigned to them with easy access. The obvious reason they aren't fixing this bug is because this thread currently only has 11 "me too" votes. They don't mind shafting their users as long as it's only a minority.
... View more

Jeremy: That doesn't explain why this happens for errors like WaitForConnectFailed where the password exchange never even happened and it's your router that decided to end the connection attempt rather than wait longer like I want it to.
... View more