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?

Find more posts tagged with

Comments

doesntreallymatter

In a time-critical scenario, my tv client should not block attempts to a machine that's shown as online while it isn't. Great Webview implementation you've got there. Maybe show machine as offline when it isn't online so I can't even go for connection attempts which block me later?

7.5 years later, you didn't even manage to change about 1 line of code to change the error message from waiting a short while to wait a specific time (if it is 10-15 minutes, just say 15 minutes).

And you really should forward this more than sufficient documented issue from this thread to the ideas hub on your own. Or maybe, you know, forward it internally because it is obviously a very poor attempt of a security implementation.

**bleep** in full swing, not just with Teamviewer. 🤣

PrimeGoat

https://community.teamviewer.com/English/discussion/comment/152836#Comment_152836

**bleep**, that's just nuts. Another ridiculous 'feature' is not being allowed to use my personal teamviewer at work in order to connect to my home machine while on break. They really need to stay in their lane and stop this **bleep**. using my home computer during my free time at work is NOT commercial use. And the fact that they snoop on your connections to determine if you're at work or not is a huge violation of so many principles. I've been using TeamViewer for many years and it's a great piece of software, except for these RIDICILOUS and UNACCEPTABLE problems that they INTENTIONALLY introduced. Seriously, what **bleep** is wrong with you guys? Are you friends with Putin?

PrimeGoat

This is absolutely ridiculous. Such a feature should be fully under the administrator's control, including whether it's enabled or not, the ability to reset it, and to configure its timeout, etc. This 'security' feature has caused a total disaster on more than one occasion. Imagine a production environment that MUST be accessed ASAP, with the client going absolutely belligerent because they need a setting updated that's affecting their entire business.. Locking an administrator out of their own server is also known as a denial of service attack. It's ironic that in an attempt to guard against DoS attacks, you decide to DoS attack your users. It is baffling that you think it is ok to infringe upon people's critical systems like that. It's as if a police officer were to break into my apartment in order to tell me that I've been flushing the toilet too much lately and am not allowed to use it for a while, right in the middle of an emergency.

Videoed_09

https://community.teamviewer.com/English/discussion/comment/152826#Comment_152826

Does anyone from Teamviewer actually read these posts? Adding to the above post, I have been using Teamviewer for years and NEVER had this problem until today. Years ago I complained to them about being locked out and somehow they set my account so I could use it but now it has reverted back to locking out or disconnecting within about 30 secs saying too many connect tries for a free account.

Videoed_09

I am not a corporate user but computer user who helps friends with their PC problems and also support several non profits with their computer issues. MUST be the **bleep** latest update that is causing the time out problem. Tried 3 times to log into a persons PC and got kicked out for XXXX minutes. It complained that the password was wrong. Typed it in at least 3 times without success. Trying to help elderly people there are going to be login / password issues but now with this going on it will make it nearly impossible to get connected. I have liked using the software as a free suer but I think I will have to start looking for something else as this **bleep**

ZLoG

This thread now 5-6 years old and still nothing.

In my situation, I use teamviewer for remote manage a long list of kiosk devices.

If some central error occurs, I may have to remote all the devices one-by-one and "refresh" them to get the going. Currently, in such a sensitive situation, I can't do this. I don't understand how connecting once - successfully - to a number of devices can be considered. I can understand if you try to connect and fail multiple times - but all my connections are successful. If this is to prevent "brute-force" attacks, then why count successful attempts in this? That makes no sense to me from a security perspective.

Right now, we have to live with some clients not being able to get back online before ew can remote connect to them again. I am in a bigger IT company and I will advise that we look for another piece of software do to this. That we cannot get our all our customers back online because of this flawed security setup is just not acceptable.

baltin

I need a solution for this.

How to disable this feature - we are using the commercial version!

rorick

https://community.teamviewer.com/English/discussion/comment/13627#Comment_13627

I dont know why are we paying for>?

user1152738

Same here - unacceptable for the customer, so some ask already to change to **Third Party Product**...

RDPearson

Seeing as I use this via LAN connections and the TV client is set to not connect via the TV servers how can this feature be for their server protection? I have this all the time on my LAN trying to assist my users. I will be hunting for a replacement product that works as this is not fit for purpose. I continuously get locked out when the stupid software disconnects me and I try connect again. I have no issues on my LAN so all thats left is this rubbish software.

HonokaOkumura121

Hi @Jeremy, I got the same issue as @deeve and I want to know how long will the "several minutes" last for before I can make another successful connection with my partner computer for a longer session. Right now it feels like forever.

Holly Z

https://community.teamviewer.com/English/discussion/comment/5727#Comment_5727

angryhobbiest

this has been an ongoing and unacceptable problem since teamviewer was invented

it counts every connection, even ones that fail out because they set the dam connection delay too low for non-cooperate internet ping(cable ping is just garbage) as "aborted" despite me wanting to shove down it's throat that: I NEVER ABORT CONNECTIONS

I think the people who code this software don't actually have any idea how RCON works, like not a single clue

see when real people using real RCON, you have to deal with MANY sub-optimal factors that can be cumulative

your connection can be slower than a real snail(not like that movie turbo), you can have multiple layers of modems that are still docsis3.0 ping, you can be dealing with a friend/travel that is over the atlantic pipeline increasing ping massively because of the speed of light, you can be dealing with wifi latency on one(or both) ends(and no"plug in ethernet" is just not always possible), and finally you could be dealing with device lag or even windows deciding it is somehow a good idea to page out teamviewer from memory despite never reaching the outdated 80% commit level or a software known to be on standby so not being actively used is not actually idle and therefore pageworthy

so basically this software is not worthy of a penny of your money ESPECIALLY for professional(commercial) use as real companies DO NOT HAVE TIME TO WASTE WAITING FOR A GOOD CONNECTION

I literally just tried to connect to BOTH my home file server AND my main gaming desktop, both idle without any known memory leak that would fill ram in under 10 days, and BOTH say "online" and BOTH actually auto-aborted without my consent to abort

in fact there is no setting for "bad ping tolerance" which you'd think an RCON software with anti-brute force routines would have a setting to avoid false brute force triggers from spotty wifi, but nope, you basically have to have fiber level ping and be within walking distance of the remote device which basically defeats the purpose of RCON

and windows vpn+RDP is just garbage as it is so stupid to set up and even then is supposed to be pro-only

people have reasons to rcon into a home server when visiting others, period

this means that this software would not be my paid professional choice ever until they get their act together and either allow "unsafe disabling of brute force lockouts" or just add a common sense delay to connection timeouts, heck what if I actually wanted to do some silly stuff for a youtube video and actually was able to visit the ISS and try to rcon into my home pc, in a purely individual content creator role, possibly even paying for pro, only to find my orbital ping is not at all possible to be low enough to RCON

the ISS can have fairly stable video, even acceptable video calling, but I can't RCON my home media server in orbit to listen to one of my audiobooks despite having enough speed and stability to do a video call to my spouse?

honestly RCON is terribly misunderstood and misclassified as something only IT guys and companies use, if I am a gamer(like MANY PEOPLE ARE) I might decide (as I did)to host a game world "dedicated server". my friends can easily connect on my sh**ty internet and play well, but then I visit my parents for a week(as I do) and expect my server to remain powered(like it is on it's massive UPS) but we all know game servers are never 100% stable and need moderation and rebooting sometimes

so what do I do when teh server is down, I have absolutely no way outside of a "pro-only" activity to using in my decidedly non-pro setup? I run RCON with a hacked license(as there is no way to operate it in "personal mode") or I use TeamViewer personal edition

but that implies that the software is actually capable of tolerating the real-world connection woes of the only setups that exist, imperfect ones

this software, like far too many these days, is configured based on optimal test cases that seldom if ever exist in normal environments, liely assuming the latest gen of cable modem or even full fiber internet service(very very rare) on both ends, and including full lan connection from device to internet to device(rarely ever the normal case) and a router that has absolutely no lag from NAT(most are worthless garbage or were actually quality and expensive bot with fatal design flaws) so compounding the issue of overly sensitive brute-force lockouts classing any connection that never gets a response(basically not factually classable as "aborted") as "connected and aborted" and then the fact that it expects a reply in 1/4 of the worst ping time most people tend to deal with regularly you get a ton of failed, not aborted, connections that are classed as "attacks" and not what they are, a frustrated user desperate to download a file they forgot from a home server, clicking "try again" until it treats them like an attacker for not having good ping

bizarrepanic

I came here hoping to find a work around just to find other paying customers like me get ignored and shrugged off.

I've been a paying customer since teamviewer 9

after this year is up I'm on the hunt for something else!

bizarrepanic

Way to go TV! love to see such an annoying use of a "lazy fix". this happened twice in the last week with crews in the field that had poor connections. Had an entire operation on standby for "a while".

[removed per Community Guidelines]

SAMEER_99

https://community.teamviewer.com/English/discussion/5562/error-you-established-and-aborted-connections-too-frequently

Best way is to stop using Teamviewer. There are many other cool Remote Access applications out there. Try them instead

OngoPH

This is not good its really humper the whole operation of specific users.

How to bypass this **bleep** feature

frankrosenberg

let me reiterate what everyone else has confirmed. there are mulitple ways to identify that this is not a brute force attack. it is incredibly frustrating when dealing with a buggy computer and accessing through easy access channel.

is there anyone at teamviewer listening to all the comments going back 6 years?

SteveJS

https://community.teamviewer.com/English/discussion/comment/124497#Comment_124497

Why do you keep referring to a post that doesn't anwer people's questions? EVERYONE understands it's a security measure, but the fact that it's a security measure doesn't mean that it's an acceptable one. People have provided you with tons of solutions on how to improve this security measure but you keep ignoring it and just keep parroting the same dumb reply.

Instead of acting like a [Removed as per Community Guidelines], explain to people why TeamViewer refuse to improve this clearly lacking security measure that only causes problems for your paying users. You should personally feel ashamed for playing along in your employers dumb charade and if you personally are seriously believing y'all are handling this issue well... Well then I agree with the earlier poster who asked you all to go somethingsomething yourselves.

LubomirStuller

First time this happened to me. Can't believe my eyes this is not a bug, but a feature. You don't even let me know how long I'm supposed to wait before I can try again? I'm really furious now.

hatim

So this is DDOS prevention by denying us service? If I'm not able to connect to a computer with connection issues, how can I help them? If at least connecting for few minutes and disconnect, I can still help them, until I get this DDOS feature designed to block me from accessing, although I already have MFA enabled and always login from the same company static IP address. This feature need to be redesigned like some suggested long time ago, using Caption or if MFA is enabled request another token, but blocking and denying service is not a security solution, it is crippling function of the application. Or at least, make it so the customer can disable the feature, and accept the risk.

BuscusDude

The excuse that this is to protect from DDOSing or whatever they find is absolute NFT (Another word for shenanigan). I sit across my work partner and I wanted to connect to his PC. His TeamViewer was open, and he was waiting for me to connect, however I get the stupid "Connection could not be established make sure you are connected to the Internet or restart your TeamViewer" or something along those lines. So, we both restarted our TeamViewers and still couldn't connect. Out of frustration, I spammed the connect button and got the timeout. This is bizarre, because not only are we connected to the same Internet, HAVE THE SAME IP, same every network configuration you can think of, because we are both on the same Terminal Server. So, please, explain to me how and why is this possible?

unknown

This content has been removed.

Johancgfh

I can not believe that this is a feature of TeamViewer, it's beyond insane. Infuriating and insulting.

I need to connect to my mothers computer, to assist her in ordering her food for the next week.

I was waiting for her to start her TeamViewer, meanwhile I was trying to connect on my side, pressing Connect again and again, waiting for it to work. And then I got hit with this **bleep**. I NEED TO HELP MY MOTHER ORDER HER FOOD!

You have ONE JOB, TeamViewer. And you are preventing me from doing mine. Who is in control of these computers, and this software? I AM! **bleep** ME! Don't tell me I can not do what I want to do, ON MY OWN **bleep** COMPUTER!

My patience is REALLY wearing thin with you guys.

And no I don't want to raise a support request or whatever **bleep** it is that needs to be done. YOU DO IT. Fix your **bleep**. This is UNACCEPTABLE.

Andy_W

https://community.teamviewer.com/English/discussion/comment/13633#Comment_13633

The real question is why the number is not exact, surely the timeout restriction has a particular value when, there's no way it can be a range, or if it is, that's quite possibly the worst implementation i've ever seen.

@AlenaC That post was lacking as I've mentioned above. It seems even you guys don't know what the correct timeout value is, so who does? Can we have some input from one of the actual engineers? Somebody did post a solution, if the device doing the connecting is a trusted device, then it should not trigger the lockout, since it's a trusted source. I can understand if you're being hit by thousands of different ip addresses, then yes, it makes sense to prevent them from brute forcing; but what's the point in having a trusted device if the system treats it as hostile anyway?

AlenaC

Thank you all for your posts,

please keep in mind that as @Jeremy explained on the first page this is a security measure.

If you have an idea to change it or feature request, I would recommend putting it on our ideas hub. As soon as any of you publish it, others will be able to upvote it. Our developers check this section regularly looking for the most voted.

Thanks in advance

Best, Alena

didikunz

HELLO SUPPORT!!!

This tread is 4 (in words FOUR) years old and the problem persistes. Is anybody at TeamViewer interested in keeping their customers? Can we get rid of that **bleep**? Or at least get an option to disable that for a given account? It is a EXTREMLY ANOYING THING. If security keeps you from supporting your clients it is a bad thing, that destroys the reputation of TeamViewer and of the one trying to give support to a client (me).

Does anybody care? Interessiert das bei Euch jemand?

joefox97

Going to ring in and agree with everyone else. TeamViewer's defensive posture about this poorly designed and implemented feature is inexcusable. You wrote **bleep** poor software; that's fine -- just go back and do a better job and implement the feature a different way. The current solution is embarrassingly bad -- and sufficient to cause us to go find alternative solutions if you refuse to change it.

Corona312

We are having this issue as well "you established and aborted connections too frequently. Please wait for a while before the next connection.

What is the amount of time to be able to reconnect?

Like others requested please use a different approach to blocking connections such as CAPTCHA, we are a new paid customer and already having this issue.

We never had this issue with "Third Party Product", but can see us having this issue more frequently with more use.

JonnyGators

This "feature" put me into a difficult situation where I had an end user on the phone I couldn't help due to you blocking my attempts to connect. The frequent aborted connections? Your **bleep** service failing to connect in the first place. Then I finally get in, get back to helping - another drop - and you block me.

Absolutely unacceptable for your "features" to block me from doing my job!

Security efforts like these only impair the legit end users - you make things so secure, only a hacker can actually do anything!

pocwiard

I am using TeamViewer for professional support to the customers. Often they have intermittent internet connection. I have to click many times to connect and often get disconnected.

The nonsense message "you established connection too frequently" when working with intermittent connection is such a pain and really limits the use of TeamViewer for me. One of the worst things you could do, to stop your customers from being able to connect.

Such a design flaw.