Re: OFF TOPIC - remote PC & TeamViewer Home Use version - Times out & Disconnects

Joe Zeglinski

Finally RESOLVED – the Random TeamViewer (versions 8, 9, 10, 11) disconnections to on-site, LOCAL observatory.
    Just a few new findings I wanted to mention, for those using TeamViewer for a “local backyard observatory” link.
after months of testing, I finally found out what causes TeamViewer to “randomly” disconnect.
  1. If the user simply downloads TeamViewer  program, and doesn’t bother checking and changing the OPTIONS, (under Extras), TV is installed with “Incoming (local) LAN Connections” purposely DISABLED.
    So, even if you have two PC’s wirelessly linked on the same table, TV will actually go out on the web and according to the run log,  hook up with one of their 19 corporate servers, (on the planet), just to talk to your other nearby in-house PC.
    It also means that your AUTO-disconnect 3-hour timer (on the FREE, non-commercial user license) has started, since you really can’t expect them to allow us to tie up their corporate servers channels indefinitely.
    Another problem, is that you are ALSO wasting your ISP “monthly data limit” with all the TeamViewer screen exchanges, since it is an “external internet” data traffic connection, even though you may just be connecting the two wireless PC’s in-house.

    - So, Ray was quite right in his earlier reply (30/4/2016) !!!

    TV requires an internet link “by Default” – UNLESS ...  you change the “Options” to Allow Local LAN connection (i.e. backyard observatories). Neither the TeamViewer website, nor the installer mentions checking the Options window settings.  Odd that TeamViewer Corp.  “chooses” to default your connection to be over the internet.
    Unfortunately, those with off-site, truly remote, observatories have no choice and must use the internet, via the TV-11 servers farm, and tolerate any possible ISP performance and line issues, somewhere along the way.
  2. TeamViewer does NOT tolerate WEAK or sporadic in-house “wireless” LAN connections on the 2.4 GHZ band.
    Running a nearby kitchen microwave oven, makes it disconnect - (a well known comms. problem) - and to NEVER successfully reconnect  on its own. You have to close its TV window and re-login. 
    It doesn’t even wait a few minutes or seconds, for the router signal to improve (e.g. when the oven finally stops running).
    According to the TV run log, TeamViewer even “tries to RESET your Router”, thinking it is your router’s fault, and then just quits trying. That reset might even screw up others sharing the router.
    Meanwhile, the same harsh signal noise test done using “Microsoft Remote Desktop Program” (RDP) ... falters or pauses when using the PC’s  internal adapter wireless connection, but always recovers, without even disconnecting the user.
    TeamViewer just has no patience for less than perfect connections, elsewhere in the PC.
  3. TeamViewer disconnects even if it is using a totally different LAN wireless link, on a different wireless adapter.
    I found that if the laptop’s own built-in  standard  wireless adapter is NOT disabled (in Windows Control Panel Settings), then TV senses a ropey or missing wireless link on the laptop’s adapter channel – perhaps a Windows status test -   and disconnects from the “other, perfectly working, wireless adapter” network,  it is actually using. Weird, or what !
    When I tested using my ASUS USB-wireless adapter for the nearby observatory’s network link, TV-11 disconnected after a few seconds of the oven’s  2.4 GHZ radiation.
    After I DISABLED  my laptop’s (slower 150 Mbps) internal adapter, the ASUS AC56 wireless (external) adapter maintained its steady 300 Mbps 2.4 GHZ link, over more than 100 feet out to the backyard observatory – Windows never even paused on the Win-10  Date/Time display, used to show Windows performance status  -  no matter how long the microwave oven was running, or how far away the (local) target observatory PC was from the house.
    Obviously, TeamViewer does not like to see a poor wireless signal on some OTHER wireless network, in the same PC.
    Although my testing was between two local PC’s, the same TeamViewer-11 disconnections would happen with a long distance observatory internet connection, if there is any 2.4 GHZ interference, picked up by the PC’s internal wireless adapter pig-tail antenna ... either in-house, or at the remote site.
    In past years, I have lost connection, on the wireless 2.4 GHZ Router’s band,  even without operating the microwave oven – Perhaps it was due to nearby city Cell Tower noise, or aircraft based radar or communications interference  as they are flying at low approach altitudes, or just interference with a dozen neighbour routers. Hard to say which.
    Now, I simply disable the local PC’s wireless internal adapter (on BOTH PC’s), and use a good pair of  USB attached external desktop wireless network adapters. (a CDN $75 ... ASUS USB-AC56 in this case).
    So, if you are getting RANDOM disconnects – try my method, (assuming you have an alternate wireless adapter), rather than using the PC’s own.
    My TeamViewer now runs FAR smoother than RDP – never drops connection. Even the free non-commercial license no longer has that mandatory 3-hour use limit ... since it is NOT connected to the TeamViewer servers, when using the LOCAL LAN (option setting).
HTH – finally ... one very happy TeamViewer wireless user,
Joe Z.

Join { to automatically receive all group messages.