Agree...I posted a reply to @Natascha's comment, but somehow it didn't get through. You essencially sum it up, more often than not there's no-one at the other side, and many times restarting is not an option ( tasks are running and we need to see them through). Also, if it's a server, restarting handing out admin credentials to users ( not an option). Opening the logs you see stuff like: "CTcpConnectionBase[64]::HandleResolve(): Resolve failed, master4.teamviewer.com, Error: system:11001" and then you use an alternative software to connect remotely, ping master4.teamviewer.com, and it resolves. Error 11001 means nothing to us users, and during a 3AM call I don't want to google around for a possible solution. More meaningfull/usefull error would be nice. TV is a remote support tool, it must be resilient to computer issues ( to a point, obviously). In order to make TV more resilient to newtork errors,namely nameresolution, why not have a local copy of TV server's IP addresses? And if connecting to one server fail, why not "round robin" to another IP? If a certain host shows up ONLINE then it should be reachable remotely, because obviously it is communicating with TV somehow. I run a "one man show", providing IT support to nearly 40 clients, so I need a reliable IT support tool. Next week will begin testing an alternative solution, and not sure that I will upgrade to TV 14 ( I have used TV since version 11, and I am now on TV 13). Best regards from sunny Portugal, Cláudio João
... View more
