Cross Platform
by

Idle Time to Think

Dave is good. Maybe even one of the best. As a supporter his Kung foo is powerful. Inside the Windows registry, it’s like he’s in the Matrix. Where others just see random numbers or unintelligible words, it’s as if he can see the truth of what’s really going on behind the scenes.

When customers contact his IT services company with computer problems, they’re in good hands, no matter what the problem. He works quickly and efficiently, but he takes his time when necessary to answer questions or offer explanations. He knows IT inside and out. It’s his realm. Most of all though, he just really enjoys helping people.

However, like everyone else, Dave has a lot going on in his life. He just got engaged to an amazing woman. The band he plays in on the weekends just lined up its first real gig, and he’s even winning his office’s fantasy football league. Life is pretty good sometimes. It doesn’t mean that it’s not without stress though.

Fight or flight

Christmas is getting closer with every passing day, and he hasn’t even thought about what gifts he’s going get his family and loved ones. Actually, as he sits at his desk thinking about it and watching the snow slowly descending through the glow of the soft yellow lights outside, he can already feel his heart starting to pound.

He shakes his head and can only sigh as he recalls an article he read the other day about how the huge crowds shopping during the Christmas season can be the cause of so much stress that it can stimulate primal “fight or flight” feelings in people.

In fact, one study even showed that some male shoppers at Christmas frequently experienced stress similar to that of soldiers in combat. They would rather get shot at than have to go into the perfume section of the department store at Christmas time.

That doesn’t even begin to cover the feelings of guilt or inadequacy associated with choosing the wrong gifts. What do you even buy for the perfect woman?

Just then, a flashing notification on his monitor startles Dave back to consciousness. Better so, he thinks to himself as he opens the session.

“Hi, this is David, what can I help you with?”

Ten minutes later, the problem is solved and Dave has again saved the day and relieved a lot stress on the other end of the connection.

Idle session timeout

“Oh man, look at the time. I gotta get going, but what the heck am I even gonna buy? Uugh.” Dave throws on his coat, grabs his keys and dashes out of the office. There’s just one problem. That last session is still running.

The guy on the other end of the line was in a bit of hurry himself. So is that session going to stay open all weekend? Not with TeamViewer. Thirty minutes later the idle session shuts down automatically.

With TeamViewer 10, idle session timeout is a user-definable option that can be set from 30 minutes to up to eight hours. Supporters and their clients never have to worry about idle sessions remaining open. To have this peace of mind, just download TeamViewer 10.

Download TeamViewer 10

Want More Like This?

Get the latest tips on productivity, technology and personal growth to succeed with coworkers and customers around the world, straight to your inbox.

75 replies
  1. Norma
    Norma says:

    Happy New Year Michael
    just had this ‘aha’ moment a way to help my 56y old daughter with her computer problems.
    Although she knows it all calls the computer stupid and wants to just go buy a new one
    rather then to battle the problems.
    Simple tasks as cleaning unnecessary files , updating etc, I will suggest to download the TV
    that I may show her a few basic tasks.
    Wish me success. LOL
    norma

    Reply
    • Michael Thomas Albert
      Michael Thomas Albert says:

      Hello Norma,
      A very happy New Year to you as well.
      I enjoy those “aha” moments. I’m very glad that our blog could serve as a little bit of inspiration. Your daughter is also fortunate to have such a helpful and technologically savvy mother. Good luck!

  2. Bernd
    Bernd says:

    “With TeamViewer 10, idle session timeout is a user-definable option that can be set from 30 minutes to up to eight hours.”
    I landed here looking for a way to stop this. I’m tried of idle timeouts ;-). So I hunted around the options and found a candidate under Extras, Options, Advanced, Advanced settings for connections to other computers and find a slider for Timeout inactive session. But it’s set to off already. I does go up to 8 hours as mentioned in your article, but I have it off, and for good measure I checked both ends of the connection and they both have it off. So is there any way I can deactivate this idle session timeout?

    Reply
    • Juulia Ruha
      Juulia Ruha says:

      Hello Bernd,
      Thank you for your message. When “Timing out inactive session” is set to off it is so to say deactivated. Have you experienced issues with the feature or do you just want to have the feature deactivated?

    • JeffD
      JeffD says:

      I have started having problems with TeamViewer11 timing me out even though I have the setting at “off” and even though the idle time has not been particularly long (sometimes 15 minutes). It’s as if it suddenly just decides I’ve been on long enough. FWIW, I am using the Linux version to connect to Windows PCs.

    • Doug McKerson
      Doug McKerson says:

      Hi Jeff,
      Thanks for your comment. There can be different reasons causing the issue. We’d be very happy to take a closer look to find out the reason for this and help you further. Please open a support ticket including your TeamViewer log files here: http://bit.ly/1DZjHiq

  3. Jaco
    Jaco says:

    How do you set the time-out period? I can’t find it anywere but since the introduction of teamviewer 11 it’s annoying short.

    Reply
    • Juulia Ruha
      Juulia Ruha says:

      Hello Jaco,
      Thanks for the message. You can set this in TeamViewer under Extras | Options | Advanced | Advanced setting for connections to other computers | Timing out inactive session. If you have any further questions, please feel free to contact us again.

    • Juulia Ruha
      Juulia Ruha says:

      Hello Beck,
      Thanks for the message. You will find this option in the advanced settings. In TeamViewer go to Extras | Options | Advanced | Advanced setting for connections to other computers | Timing out inactive session. I hope this helps. If you have any additional questions, please feel free to contact us again.

  4. Scott
    Scott says:

    This timeing out option has off up to 8 hours. Does off mean never disconnect buecause it does disconnect much more frequently since I updated. Is 8 hours the best I can do?

    Reply
    • Juulia Ruha
      Juulia Ruha says:

      Hi Scott,
      Thanks for the comment. When a TeamViewer session is inactive 8 hours it will be timed out. However, if TeamViewer disconnects often I’d recommend you to contact our support team: http://bit.ly/1DZjHiq Please provide our support team with your log files so that they investigate the issue.

  5. Jaco
    Jaco says:

    Thanks for your response Juulia,

    It doesn’t work though, both the pc I use as the remote controlled pc have ‘Timing out inactive session’ turned to ‘off’. However, the connection still times out with the “Your Teamviewer session has timed out and will be closed.”

    This problem emerged after updating to Teamviewer 11. I could have Teamviewer 10 running all day without time outs.

    Reply
  6. Tom S.
    Tom S. says:

    I have both the local and remote TeamViewer (version 11.0.53245) timeouts set to “off” (it’s default value). However, the session still times out, not sure how long the inactivity period actually is as I haven’t measured it, but it is certainly seems less than 30 minutes and the timeout period does not seem to be consistent. However, as I said, it should not time out as it’s set to “off”. Any suggestions as to why it’s not working?

    Reply
    • Juulia Ruha
      Juulia Ruha says:

      Hello Tom,
      Thanks for your message. There can be different reasons causing this issue. We’d be happy to look into it and help you further. Could you please open a support ticket including your TeamViewer log files: http://bit.ly/1DZjHiq Thanks in advance!

  7. marios
    marios says:

    teamviewer 11 every 1 hour disconnect even if the timing out inactive session is off.
    thinking to go back to teamviewer 10 wich has no such problem. connected all day without to disconnect.

    Reply
    • Juulia Ruha
      Juulia Ruha says:

      Hello Marios,
      Thank you for the feedback. If TeamViewer disconnects that often we’d need to take a look at your TeamViewer in order to find out what is causing the issue. Can you please contact our Support Department and provide them with your TeamViewer log files: http://bit.ly/1DZjHiq Thanks in advance!

  8. Chris
    Chris says:

    I have set the “Timing out inactive session” option to “Off” on both the client and host computers and it still times out and disconnects after a certain amount of time, even if there is no inactivity. I’m using TeamViewer 11. Any ideas?

    Reply
    • Juulia Ruha
      Juulia Ruha says:

      Hello Chris,
      Thank you for the message. We’d need to take a closer look at your TeamViewer to find out what exactly is causing this. Could you be so kind as to submit a support ticket including your TeamViewer log files? You’ll find the log files under Extras -> Open log files -> TeamViewerX_Logfile. Thanks in advance!

  9. Steve B
    Steve B says:

    computers on both sides of connection are set to OFF, yet connection keeps getting closed for timeout after 3 or 4 hours, which also apparently aborts in progress file transfer.

    Reply
    • Juulia Ruha
      Juulia Ruha says:

      Hi Steve,
      Thanks for your message. Could you please contact our Support Department and provide them with your TeamViewer log files? Our support team will analyze the log files and help you further.

  10. Rich
    Rich says:

    Same issue. Both computers timeout set to off. Times out after some hours have gone by. Ver. 11.0.53254
    Rather than multiple persons sending tickets off, can someone from support indicate if this is a known problem that is being fixed?

    Reply
    • Juulia Ruha
      Juulia Ruha says:

      Hello Rich,
      Thanks for your comment. When a connection with a free version of TeamViewer is established and the connection is a TCP connection the session will be disconnected after three hours. Please note you can always establish a new connection again immediately afterwards. However, each case can be different and there can be other reasons causing the time out. For example, some connections are UDP connections instead of TCP connections. Sometimes the issue can be caused by the internet connection. In such cases we’re not able to tell what is causing the issue without taking a look at the TeamViewer log files of the respective device. As we don’t want to give inadequate solutions we ask our users to submit a support ticket so that we can investigate what is causing the issue. I hope this answers your question. If you have any additional questions, please feel free to contact us again.

  11. Jaco
    Jaco says:

    Could you post back here as soon as there is a solution? I have the same problem and would like to found out how to fix it. This problem started occurring after the update to teamviewer 11.

    Reply
    • Juulia Ruha
      Juulia Ruha says:

      Hello Jaco,
      Thank you for your message. There can be different reasons causing the issue. We’d be happy to take a closer look at your TeamViewer to find out the reason for this and help you further. Please open a support ticket including your TeamViewer log files here: http://bit.ly/1DZjHiq

  12. Boris Noneya
    Boris Noneya says:

    As with many other people, “Timing out inactive session” is turned off on both computers and still happens. Would be real nice if you could give some feed back besides asking people to private chat your tech support. It’s obviously not an isolated issue so how about a fix?

    Reply
    • Juulia Ruha
      Juulia Ruha says:

      Hi Boris,
      Thank you for your message. When there’s a TCP connection established with TeamViewer the session will be disconnected after three hours. However, you can reconnect immediately. Please note that not all TeamViewer connections are TCP connections. Some of them are UDP connections. With a UDP connection the remote session should not time out. Also, sometimes there might be another reason causing the issue. The only way for us to find out why you are experiencing the issue is to have a look at your log files. That is why I need to ask every user facing this kind of issue to submit a support ticket. I hope you understand.

  13. Tom
    Tom says:

    Juulia,

    This 3-hour timeout was introduced in TeamViewer 11, and re-establishing the session is not a good option at all. It will timeout as I’m typing. Sometimes I have a time-sensitive need, and the few minutes it takes to reconnect is more than just an inconvenience. I understand that you want this timeout in the free version. Can you at least reset the 3-hour timer from the last time I used the remote session? That way at least it won’t timeout as I’m typing into it.

    Regards,
    Tom

    Regarde

    Reply
    • Juulia Ruha
      Juulia Ruha says:

      Hi Tom,
      Thank you for your feedback. I understand timing out a remote connection can cause troubles when you have a time sensitive need. I will therefore forward you feedback internally.
      Regarding the timer, it is reset after the connection has timed out. If this is not the case and you get disconnected after short time please contact our support team and they will look into it: http://bit.ly/1DZjHiq

  14. Jaco
    Jaco says:

    Hi Juulia,

    You indicate: ‘When a connection with a free version of TeamViewer is established and the connection is a TCP connection the session will be disconnected after three hours. ‘

    Will downgrading to teamviewer version 10 fix the problem?

    Reply
    • Juulia Ruha
      Juulia Ruha says:

      Hi Jaco,
      You’re welcome to try if the connection lasts longer with version 10. Please note that with version 10 applies the same policy. However, most of the feedback we’ve received is about version 11.

  15. jeff
    jeff says:

    This problem is not being addressed and is an obvious issue for most teamviewer 11 users. The question is WHY it’s not being dealt with?
    This was not a common problem in previous versions…so why now? And why state that there can be many different causes when this wasn’t an issue before 11?
    Please stop beating around the bush on this and either take responsibility for the problem and either let us know (as users) what we can do, or when a fix is coming.

    Reply
    • Doug McKerson
      Doug McKerson says:

      Hi Jeff,
      Thank you for your comment. We’d be happy to take a closer look at your TeamViewer to find out the reason for this and help you further. Please open a support ticket including your TeamViewer log files and a description of the issue you’re experiencing here: http://bit.ly/1DZjHiq

  16. Alfred Dixon
    Alfred Dixon says:

    Obviously the timeout is causing a lot of people to become frustrated. Me included.
    “Off” should mean “Off” not the program’s built in, far to short, default.
    That said it is a great program.

    Reply
    • Doug McKerson
      Doug McKerson says:

      Hi Alfred – I’m sorry to hear you’re experiencing frustration because of this issue. Please do reach out to our support team so that they can look into this: http://bit.ly/1DZjHiq Also, please include your log files.

  17. John Doe
    John Doe says:

    What a way to mess up a good product TeamViewer 11. Clearly the answer hear is pay for the pro version and hope it gets fixed. Or go back to TeamViewer 10 which didn’t have the timeout problem. It is rather insulting to tech savvy people for you to keep saying to everyone to send in their log files as if this is not a Teamviewer version 11 issue. It would be more logical to keep saying we’re working on it when you obviously are not.

    Reply
    • Doug McKerson
      Doug McKerson says:

      Hi there – I’m very sorry you feel that way. At this point we need to look into the log file in each case in order to find out what is causing the issue since there can be various reasons. It is true that we’ve received quite a lot feedback on this issue. Nevertheless, we need to investigate each case individually. I hope you understand.

  18. Michael
    Michael says:

    I’m also having a problem with the 3-hour timeout. It makes this program almost unusable. Having it dump you out of a connection while you are in the middle of doing something is just bad form.

    So in reading this page, I noticed that it was stated that the free version has this limitation but the paid do not. So I thought to myself, “Oh heck, I use this to manage my home media server remotely… I can probably throw some money into it.” But then I find out that the MINIMUM price is 800ish dollars!?
    You state it is “Free for personal use” on your website and then make it more of a pain to use than it should be.
    You should either remove the disconnection(it’s one thing if it disconnects while idle.. entirely another when it disconnects during active use…) or at least add a cheaper version for personal use!

    Reply
    • Doug McKerson
      Doug McKerson says:

      Hi Michael – Thank you for your comment – I’ve forwarded your suggestion internally. I’d recommend you get in touch with our support team and include your log files so they can look into the issue you’re experiencing: http://bit.ly/1DZjHiq. Just a reminder that TeamViewer licenses are for commercial use – personal use is free.

  19. Philip Albert
    Philip Albert says:

    I think it would be in TeamViewer’s best interest to kill the time-out. I will have to move to a different solution, if this continues. I’m remotely running thousands of dollars of astronomy equipment. When your new 3 hour time-out ‘feature’ disconnects me…. it kills all programs running, on the remote computer! And, when I have a telescope tracking, while taking long exposures….. should I just say, That’s a serious issue! Kill the 3 hour time-out!

    Reply
    • Doug McKerson
      Doug McKerson says:

      Hi Philip – I’m sorry to hear you’re experiencing frustration because of this issue. Please get in contact with our support team so that they can look into this: http://bit.ly/1DZjHiq Also, please include your log files.

  20. Brad
    Brad says:

    If I understand correctly, if I am uploading/downloading files using the free version of TeamViewer 11’s file transfer, the 3-hour time limit can possibly terminate the connection, thus terminating the file transfer? Surely, you can see how this would be very problematic on a slow connection during the transfer of a large file, or if a file transfer was started toward the end of the three-hour window. Reconnecting may not solve this – it seems like a poorly thought out limitation. Is there any discussion internally about removing it?

    Also, Juulia Ruha mentions this 3-hour time limit will not occur on the free version of TeamViewer 11 when UDP is used instead of TCP. Is there any way to force UDP? Why is there a decision to disable the 3-hour “feature” on TCP, but allow it on UDP?

    Thanks!

    Reply
    • Brad
      Brad says:

      To revise the last sentence in my previous post, it should say, “Why is there a decision to disable the 3-hour timeout “feature” on UDP, but allow it on TCP?”

      Any reason why there is no response to my questions? I noticed every other person received attention within a couple days at most, yet eight days later, no response. There is another user, Danny, who posted on Feb. 9 that also brings up the file transfer point.

    • Doug McKerson
      Doug McKerson says:

      Hi Brad – thank you for your message. The three hour time out for TCP connections is part of the free version. However, not all connections are TCP connections. The three hour time out should not happen when the connection is a UDP connection. If the file transfer connection is a UDP connection it shouldn’t time out. Can you please try if changing the TeamViewer network settings helps? Go to Extras -> Options -> Advanced -> Advanced network settings -> check “Use UDP” on both computers in the connection (the local one and remote computer). If you still experience issues after changing the settings, please submit a support ticket so that we can look into it: http://bit.ly/1DZjHiq

  21. Jeff
    Jeff says:

    I’m so glad to see that others are having this problem as well. I use TeamViewer 11 all day, and it’s timing out in the same way everyone else is posting about. Would love to go back to TeamViewer 10, as 11 is simply unusable with the 3 hour timeouts. I may have to go to Remote Desktop Connection, but would prefer the issue fixed in TeamViewer.. Please fix this. TeamViewer 10 never did this.
    Thanks!

    Reply
    • Doug McKerson
      Doug McKerson says:

      Hi Jeff – I’m sorry to hear you’re experiencing frustration because of this issue. Please get in touch with our support team so that they can look into this issue: http://bit.ly/1DZjHiq Also, please include your log files.

  22. Yupper
    Yupper says:

    What’s the status of this? I have the same issue as everyone else: setting the idle timeout option to “off” does nothing… TeamViewer 11 still disconnects automatically on what seems like a timer, no matter if you’re even in the middle of doing something (i.e. not idle). This did not happen with TeamViewer 10.

    Please let us know when this will be fixed. It is obviously not an isolated incident. Please don’t ask for my log files, with this many people having problems you should easily be able to track down and fix the issue.

    Reply
    • Doug McKerson
      Doug McKerson says:

      Hi Yupper – thank you for your message. The only way for us to find out why you are experiencing the issue is to have a look at your log files. That is why we need to ask every user facing this kind of issue to submit a support ticket here: http://bit.ly/1DZjHiq I hope you understand.

    • De-M-oN
      De-M-oN says:

      It is obvious why. Its your mentioned limit. Remove it.

      No one is willing to pay you that amount of money.

      Offer at least a way to remove that annoying limit.

  23. Danny
    Danny says:

    I have been experiencing the same issue since Teamviewer 11. My timeout option is also set to OFF. It happens even on my home computers connected to the exact same network. This never happened in prior versions. I have been using the free version for several years. Something has changed with Teamviewer 11. It would also be beneficial to tell us where and what the log files are you want attached and which computers.

    Reply
    • Doug McKerson
      Doug McKerson says:

      Hi Danny – thank you for your message. There can be different reasons causing the issue, which is why we need to ask each person to contact our support team so they can take a closer look to find out the reason for this and help you further. Please open a support ticket including your TeamViewer log files here: http://bit.ly/1DZjHiq You’ll find the log files under Extras -> Open log files -> TeamViewerX_Logfile.

  24. Jason
    Jason says:

    I have the same issue – I spent the weekend trying to copy a massive .pst file to my fathers new pc, and it kept failing. The estimated copy time was 5 hours – now I know why it kept failing!!
    This is worryingly beginning to sound like LogMeIn’s ‘bait & switch’ business model. They where fairly priced, but kept removing things from the Pro package and TeamViewer is too expensive for me to pay for.
    Time to look for a third party option 🙁

    Reply
    • Doug McKerson
      Doug McKerson says:

      Hi Jason – thank you for your message. There can be different reasons causing the issue. Please contact our support team so they can take a closer look to find out the reason for this and help you further. Please open a support ticket including your TeamViewer log files here: http://bit.ly/1DZjHiq

  25. Danny
    Danny says:

    The timeout happens in 3 hours regardless of activity. I can be in the middle of a session working and BAM timeout and disconnect. This is very aggravating. It has also happened in the middle of a FTP session and it kills the transfers.

    Reply
  26. Maxim
    Maxim says:

    Hello
    Why in the paid version, you cannot to do just auto disconnecting a connection from provisos computer if you connect on another one?
    I have to wait the auto disconnecting time-out!
    For multiple connection I have to pay you a tons of money! And we dont need it!

    Reply
  27. StanleyC
    StanleyC says:

    I have both side PC set using UDP connection.
    However, I find the option does not force all connections use UDP but some process still using TCP from the log. The TCP conenction finally closed by idle time too long. The idle time setting does not take effective at all, even set it to off or 8 hours does not help 🙁

    Reply
  28. Tim
    Tim says:

    The solution seems pretty clear – release a revision to version 11 without the 3 hour “inactivity” timeout. Why is this so hard to understand?

    Reply
  29. Antti
    Antti says:

    Hi!
    TeamViewer WAS the best of any kind of remote control software but because of this limit it is now almost useless. I often transfer rather big files from a computer with slow connection so 3 hours is not even close to enough.
    You just keep asking for logs when you know that will not help in 99% of cases because it is intentional, VERY annoying ‘nag’ for free version.
    You should at VERY least warn about this when file transfer or session is closing to limit but of course the only good solution is to remove that limit completely.
    Or if you want people to buy this, then for heaven’s sake make the price at least somewhat reasonable for personal users.
    For this hidden ‘feature’ I am VERY disappointed in TeamViewer which is sad because I thought you cared about customers and not just money.

    Reply
  30. Antti
    Antti says:

    The worst in this is that file transfer creates the full-size file immediately and names it as requested so there is even no way to tell if some file is incomplete or not. And that file is still in use by TeamViewer even after the timeout!
    Actually it seems TeamViewer wants to make free usage as difficult as possible.
    After this I am even more disappointed, I really thought this company wanted to make good software without greediness but this sadly shows otherwise.

    Reply
  31. Martin
    Martin says:

    The problem is still there, even with freshly downloaded Teamviewer 11. The timeout slider is not a bad idea, but it doesn’t work properly. This ‘feature’ is a bug and needs a fix. I’m going back to version 10 or maybe 8 and looking for an alternative solution for remote software. I used to be a big fan of Teamviewer, but Version 11 is a big step backwards in functionality.

    Reply
  32. Joe Z.
    Joe Z. says:

    I too have been suffering from the dreaded TV “time out” problem. We have now established that it was “intentional” in the free version as a form of persuasion to spend the big bucks for the commercial version.

    However, I tried going back to the previous TV-10 as a test of two laptops 2 feet apart right next to the router, and it still times out – even in TV-10. One of the laptops was even directly cabled into the router – no difference. This is under Win-10 Pro.
    The timeout isn’t exactly 3 hours – it is completely RANDOM. I have had TV run for upto 3.5 hours, if I didn’t touch the keyboard too often. Another time, it timed out in a few seconds, and I had to reconnect about a dozen times in 10 minutes!
    I do NOT think it really is a “timer” problem – far too random. When I had a “pair of host laptops” (sessions) connected tonight, from one directly cabled client, all three Win-10 PRO PC’s ran for about 3.5 hours before drop out. I managed to “beak them” by doing some internet searches on the client, which added extra Ethernet traffic on the home configuration, and both hosts dropped out in a short while.
    I very STRONGLY suspect it is a case of TV-10 and TV-11 not being able to handle the communications load. Or, it is checking for TCP/UDP loss and giving up too quickly. Check your logs around your TV’s crash time and you will see several checks without answers in just a few seconds, and TV shuts down the session. Maybe if it waited 10 seconds the load might subside enough to not shutdown.
    Haven’t tried yet, but another fix might be to TURN OFF all three LOG boxes in the EXTRA setups. TV sends a lot of traffic to the log files. Might run longer without logging.
    … My log shows several lines like the following, at the timeout point:

    CarrierReconnectLogic[80]::StartReconnectAsClientInternal: TCP connect successful
    (then a split second later…)
    CTcpConnection[181]::KeepAliveBeepTimerHandler(): No KeepAliveBeepAnswer was sent. Stopping connection.

    It seems that this “KEEP ALIVE” checking is done for too short a period, before TV initiates a graceful shutdown of the session.
    I think I will try to go back further – maybe TV version 9 or even ver. 8 might wok better ???
    TeamViewer is a “wonderful app” and I appreciate having it for my astronomy hobby – Too bad this timeout or communications (WiFi or direct connect) load sensitive abort is ruining its otherwise excellent reputation, at the moment.

    HTH,
    Joe

    Reply
    • Joe Z.
      Joe Z. says:

      As a follow up, the problem continues – “Totally Random” TeamViewer disconnections in far less than the “undisclosed” … 3-hour timeout limit for the Home , non-commercial use license.

      Is anyone using the Commercial Version, and is NOT having this “random” timeout issue? If even that version has this bug, it would seriously impact acceptance and sales of TeamViewer. Then again, if it works with a Commercial license, then why punish Home users, who are in effect the Beta testers of the Commercial version.

      Been chasing and testing possible work-arounds for many man-weeks, under Win-10 Pro, and none of these work:

      (1) Tried complete uninstall and then re-install of TeamViewer versions (9, 10, and 11) – all have the random timeout, far shorter than the undisclosed 3-hour limit. Could QA have missed it all these months and years?
      (2) Used 3 different, recent vintage Intel i7 PC’s, lots of RAM didn’t solve the bug – and one of the PC’s even boots from a high speed SSD solid state drive, for all that heavy TV Logging. Not a hardware issue.
      (3) Exchanged PC roles, Host vs Client on TeamViewer – still get random cutouts. Not a client-side only bug.
      (4) Positioned laptops beside each other right next to the Router, all within 3 foot distance to source – didn’t help
      (5) Tried both “Wireless and Direct cable” to router – not a signal quality issue
      (6) In all tests, Windows Power Option set to “High Performance Mode” – never Sleep or Hibernate, so the OS doesn’t stop communications
      (7) Likewise, setting to Accept only Local LAN connection to avoid internet problems – didn’t fix it
      (8) Turning OFF all TeamViewer “LOG Functions” to minimize the constant disk I/O – ditto
      (9) Setting up the test PC’s with no apps running, no keyboarding, no mouse movement, and walking away from the “idling” session – still times out long before the allowed 3 hour limit. This happens whether or not the session is busy with operator activity, or not.

      It would be nice if, in addition to solving this nuisance Random timeout bug, the company would:
      (a) Disclose in the webpage, and in the Installer, as well as the TV Setup, that the Home License has an actual built-in 3-hour timeout limit
      (b) That a “count down timer” be displayed showing how much time we have remaining to finish our transactions
      (c) The Timeout Bar in Advanced Settings be disabled or left FIXED in position at 3 hours for Home installs, rather than the OFF and 8-hour Option which is strictly available to the Commercial users … who can easily “write-off” that other very expensive version
      (d) Change the wording in the message from “Attempting to Reconnect” … which implies it will come right back, so we should wait – Instead, just say it is being shut down and ask the user to log back in.
      That warning would be more less deceptive.

      This random timeout bug is widely discussed on the web – couldn’t be inspiring confidence in even the Commercial product. It is time for the QA staff to actually test the product before release, rather than relying on us Home use as Beta testers.

      TeamViewer is a well designed, well thought-out product. It is a shame … to quote .. Shakespeare that … “for want of a nail, this horse is lost”.
      Fix the random timeout bug – we can live with the “undisclosed” but imposed 3-hour limit, if we must.

      Joe

  33. Ron Marz
    Ron Marz says:

    If this cursed new three-hour timeout can’t be eliminated, perhaps you’d be so kind as to implement a message box or timer warning us when we’re within five or 10 minutes of being abruptly disconnected. Thank you.

    Reply
  34. Steve
    Steve says:

    The support sounds like a broken vinyl – repeating all the same useless mantra “show us the log files” which obviously makes no sense. What a stupid business model, as was said – logmein style – bite and switch. 🙁

    Reply
  35. Mahir
    Mahir says:

    Wow. Way to kill an otherwise useful product! The timeout message may as well say “Pay us $800 or install something else”.

    Reply
  36. Tony Bell
    Tony Bell says:

    Instead of this waste of time quasi-fiction, how about you tell us how to stop automatic timeout in Preferences in the free version, or tell us that it is not possible to do so, so we can find another piece of software that does not have this EXTREMELY ANNOYING ANTI-FEATURE.

    Reply

Leave a Reply

Want to join the discussion?
Feel free to contribute!

Leave a Reply

Your email address will not be published. Required fields are marked *