Error: You established and aborted connections too frequently?
I've been running Team Viewer 12 personal edition for a while with no problems on Windows 7 64-bit. Since this Tuesday, when I try to do a remote session with my other pc I cannot get to the password entry box when I click the 'Connect to partner' button. Out of frustration, I tried a rapid double-click which worked once but when I tried again, I receive this error & cannot try for a timeout period of about 15 mins: "You established and aborted connections too frequently". Is there a bug with this latest version?
Comments
-
Hi @deeve,
This is actually an important security feature in TeamViewer, which has existed for quite a long time. The feature exists as one of the methods we use to protect TeamViewer from brute-force attacks from botnets or would-be hackers.
If someone tries to make multiple connections to the same TeamViewer ID over a short period of time, they will automatically be blocked, for several minutes, from making further connections. This will happen if you click the "Connect to partner" button repeatedly.
You will need to wait for the indicated amount of time before being able to connect again.
Regards,
Jeremy
TeamViewer Quality Assurance Engineer1 -
Hi jeremy,
This is more acurately, a change of terms. I thought to see what would happen if I registered an account with Team Viewer & guess what? It now miraculously connects as it used to.FYI, waiting for the indicated time (there was never any specific time given) & trying again did not make any difference to this behaviour, or lack of, to be more acurate.
5 -
Hi @deeve,
Can you clarify what you mean by a change of terms? Which terms are you referring to?
The behaviour I described above - that you will be automatically blocked for several minutes if you click the "Connect to partner" button repeatedly - is not affected in any way at all by having a TeamViewer account. This security feature exists whether you are signed into an account or not.
However, once the blocked time has expired, you should be able to connect once again to the remote computer.
Regards,
Jeremy
TeamViewer Quality Assurance Engineer1 -
Sure Jeremy, I was being facetious. The timeout feature you mention did not permit me to log on after it had passed. I did not press the connect button repeatedly for the sake of it - I did so because I could not activate the connection password dialogue box as I was used to doing before. The double clicking was a frustrated attempt to beat the disconnect that was occuring - and this technique did actually work, once.
My English sense or irony was therefore implying that since I registered for a user account, as if by magic, the Connect button now mysteriously works, again.
4 -
Okay, gotcha - thanks for clarifying!
Regards,
Jeremy
TeamViewer Quality Assurance Engineer0 -
This should really be changed to only count failed logins.
This limit just hit me when connecting to a flaky machine, I've disconnected and reconnected about a dozen times in the last two minutes and now it's telling me I have to sit and wait.
Brute force protection is a good thing, but valid correctly-authenticating connections are not a brute force.
18 -
@Jeremy wrote:
> they will automatically be blocked, for several minutes
Can you offer any guidance on the definition of "several minutes"? My client's WiFi connection is demonstrably bad so I've been hit with this error message a few times. Since my client pays me for my time, it would be important to know how long I need to to wait.
6 -
Agreed, this is incredibly annoying and frustrating. We have a paid license for Teamviewer and trying to help a client out and I got locked out of hteir machine and I have no idea how long I need to wait before trying again. Terrible design. If you need to confirm I am not a bot, how about presenting a captcha? How about helping your customers instead of **bleep**ing them off.
12 -
I am in the same boat. Paid license and i cant conenct to a client becauseof this stupid feature. I had to restart the modem so was hitting connect a few times to see when it came back online. Now i am sitting here, not earning money ,waitingt for some undisclosed amount of time to pass. You must have a better way of doing this.
8 -
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.
3 -
"for a while" is NOT an indicated time. How long do I have to wait, a minute, a day or a year?
14 -
Hi all,
As mentioned in my previous post, you only need to wait for several minutes - approximately 10 to 15 minutes should be enough (it's not exact)..
Regards,
Jeremy
TeamViewer Quality Assurance Engineer2 -
Hello,
we are encountering the same problem here. This is NO indication of how long we have to wait. This is very frustrating. We need to help our customers and we cannot as we are locked out !
How can we remove this "superb" security feature ? We are not being paid here for being not able to help people. Do we need to go back in TeamViewer version ? This can't be serious.
Please provide a solution !
Kind regards,
Patrick
6 -
Right in the middle of a stressful network down situation i was hit with this stupid problem. [removed per Community Guidelines]
Please hear your customers feedback - this is dealbreaking problem that will make people switch to another solution.
14 -
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
6 -
Me too!
Please disable this "feature". We also have a corporate license for TV 12, and have lately big problems logging in to our customers.
9 -
Currently unable to connect to one of my client machines with this error, which means I have a retail terminal unable to trade, so this is actively costing my company money.
Note I have had multiple SUCCESSFUL connections, just a **bleep** connection at the client end neccessitating re-establishing connections. Happily we're in the process of renewing - I feel I'll be making recommendations for other solutions.
6 -
Same happening here too connecting to a very slow machine. Very frustrating
5 -
I just had this annoying problem as well. First I tried to connect and then I guess the client quite TeamViewer in the same moment. After that he opened it again and it didn't work anymore. It was always trying to connect. We both restartet our machines and it still didn't work. I wasted a lot of time and money. Additionally it made me look unprofessional.
This is very bad design!!!
6 -
it says ive tried and disconected too many times nbut this was due to you saying i had not enough connections so kept trying to see when one came free now one is free i cant connect what a S******D design this is/!!
4 -
This is the reason why you should not pay for this software.
4 -
I'm in agreement with everyone else, implement a captcha. Security is useless if the people that have access to a resource cannot due to security limitations.
8 -
At what point will Teamviewer support take notice? We have a paid license to use this software product, which we purchased based on recommendations of others... I wonder how long those recommendations will continue if Teamviewer support turns a deaf ear to this thread? We pay for the software, do not limit our use with this poor design.
5 -
how much time is the official time required to wait? we have an observatory at the top of a remote mountain with a very bad internet connection and it would be good to know how to keep from locking up like this.
Thanks
4 -
so it's a random amount of time between 10 and 15 minutes? It would be acceptable to state that.
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.
I'd prefer that the TV server (not the remote client which may be behind a flaky internet) give the option to authenticate or reauthenticate my connection to TV. I'm getting locked out after reattempting connections numerous times, but with 30 seconds between the attempts.
0 -
@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.
15 -
Might have to switch off this software because of this trash.
This should be able to be disabled.. Now I have a client that I cant help in a crunch because your software locked me out for an UNKNOWN TIME over multi clicks..
Byebye Teamviewer.. We gotta dump you.
9 -
Has anyone ever tried to call support for this issue?
I did today, and they pointed to the remote computer being the issue, but couldn't go any further obviously because I couldn't connect to it. Rebooting the machine resolved the issue, but didn't reveal the problem.
They instructed me to grab the log files from the remote computer (Extras >> Open Log Files), and open a support ticket (https://www.teamviewer.com/en/support/) so they can analyze it. They also have a data collector (http://download.teamviewer.com/support/TeamViewer_SupportCollector.exe) that can be used that seemingly creates log files in a more controlled manner, but ultimately provides the same information as the log files, according to the person I spoke with.
So, TeamViewer Staff: could you direct us in the right direction next time instead of just telling us the obvious? This thread is two pages at the time. There was no solution posted, and I have to say issues like this make products from other vendors much more appealing. We NEED support. It isn't a luxury with a paid product. Thanks for listening and improving.
-A Paying Customer
3 -
This is very annoying. Moreover there should be a more accurate system to prevent DDOS. A brute force attack implies thousands of connections / sec in order to be possible. Unless a user tried to connect with such frequency (tough for a human being isn't it ?), why blocking him for 2 or 3 failed attempt within the same minute ????
1 -
And if I don't wait enough and try again, do I get re-timed out for another 10-15 minutes ?
Thanks in advance for the answer.
And indeed this is really an inconvenient way to implement DOS/brute force protection.
I landed in this situation because of flaky connection on the remote I was trying to connect to and re-tried several times (at a human pace, waiting for a few seconds before retrying...)
5
