Badges

Before you run TeamViewer run Terminal and elevate to Root User with the following command.. sudo teamviewer daemon restart [enter] and when complete type exit [enter] and then exit [enter] again. Then run TeamViewer as you would normally and it should caputre the Internet. Things in Camp TeamViewer for Linux are not so good anymore and the developers do not care about us linux users.
... View more

Date: 20190228 / 28-Feb-2019 So it seems the rot with TeamViewer continues! I launch TeamViewer 14 tonight to find all by client contacts on TeamViewer 14 are now listed as black with the following after all of them (unknown). Worse I have arranged to work on a clients laptop tonight and 90% of the time when I add the clients TeamViewer ID they do not come up as an available and online system to connect to but they are classified as "(unknown)" and I am unable to connect to my client. When my clients remote laptop (Windows-10) has been online I have been able to connect until the remote connection fails and when attempting to reconnect I am presented with "waitforconnectfailed" and all the rot there. At the end of the day you take our money and when your product is incomplete or fails it is not you who is on the ground who looks bad because of your failures it is us. I have spend over a year having to downgrade back to TeamViewer 12 for stable remote support services and a service I have paid for now for 2 years running that is incomplete or makes me look bad. I deserve better from a business who charges me so much per year for their product and a Premium licence. I have in the past deleted a number of contacts (my clients) from which I earn a living and provide remote support services and tonight I can not enter a clients TeamViewer ID and provide an Alias for them as for the majority of the time they are classified as "unknown" and I am unable to connect. I do not know what is going on at TeamViewer but this rot of developing a product around your paying clients and providing incomplete products masquerading as complete when key features are missing (ability to automatically reconnect to a remote windows OS after a remote reboot) and worse removing TeamViewer 12 and adding a set of custom repositories to ensure and force users to use TeamViewer 14 even though key features are still missing is plain outright disrespectful. You do not care that the remaining business and private clients I had saved in my list of contacts is now classified as “unknown” and that I have let another client down with your failing and faulty service tonight because you have already been paid for another year. If you did care then why is this the state of TeamViewer in 2019 on 28-Feb? I am the one who will have to explain to my client why I was unable to complete the work I promised them I would do which, makes me look bad when you should own this sh*t and not leave it on our shoulders!!! After the disaster of tonight I guess there is no point in saving clients information and TeamViewer Contact Details. TeamViewer use to have respect, honour, commitment and passion for their software and us as their clients but for over a year now I have seen none of it, replaced with pure greed at the cost of us, your paying Linux Users & Clients! I could not be more disappointed and let down by TeamViewer as a Premium and paying client and worse it carries on directly to my clients!
... View more

I have checked TeamViewer 14.1.9025 on 23-Feb-2019 and there is still the ability to conduct a "Remote Reboot" but the necessary feature to be automatically reconnected to the Remote Windows Computer after the reboot is missing. Back to the feature rich TeamViewer 12 until the clowns get TeamViewer 14 completed! How do the developers of TeamViewer expect us to reconnect to a Remote Windows Machine after a Remote Reboot when TeamViewer generates a new random password and the feature to automatically be reconnected is missing? Not all my clients want me to use a static password and to have TeamViewer running on System Boot into Windows. Why have the option for a Remote Reboot if you are not going to have the feature to automatically reconnect after the Remote Reboot has occured?
... View more

Dear Dom, Thank you very much for sending us these Feature Requests. I will forward your suggestion to our product management. Such ideas are always welcome, although I cannot promise when or if this Feature will be implemented, as the decision is based on public demand. Nevertheless, your feedback is very important to us as we want to continue to develop TeamViewer based on our user's needs and demands. We will be happy to inform you about realisation of this feature. If you have any further questions on our product, please feel free to contact us. Best Regards, Support Engineer
*********************************************************************************
I am not asking for a NEW FEATURE to be added to TeamViewer 13 and 14!!! I am asking for the same features and functions to be available in TeamViewer 13 and 14 that were in TeamViewer 8, 9 10, 11 and 12. Why have the possibility to conduct a Remote Reboot on a Windows Operating System without the potential to automatically reconnect to the remote Windows Operating System to continue our Remote Session? We could just click on the Start menu and conduct a normal Reboot on the remote Windows Operating System. This is a blatant incomplete feature the developers hoped we would not notice was missing and I am fed up with incomplete versions and features missing in TeamViewer 13 that has been passed onto TeamViewer 14.
Have some respect for us Linux Users who you have forced to wait for over a year to provide us with a bare basic working native version of TeamViewer for Linux. Any of us serious users who provide Remote Support are having to hang onto the last version of TeamViewer that came out with all the necessary features and services which was TeamViewer 12.
Stop disrespecting us Linux Users and in doing so disrespecting our businesses and at least finish a full & feature rich version of TeamViewer 14 that has all the features of TeamViewer 8, 9, 10, 11 and finally the last decent version of TeamViewer being version 12.
You are a better business than this and it is time to start behaving the way you used to before the development of TeamViewer 13 and the total **bleep** that it has been for over an entire year where the incompleteness has been inherited by TeamViewer 14. Are your Linux Developers so overwhelmed that they can not finish what they started or have your development team been so focused on the Windows Version you just do not care about us Linux Users?
... View more

*** Instructions for Debian / Ubuntu Based Operating Systems *** If this happens to you then please launch Terminal (Ctrl + Alt + T) Elevate to Root User in Terminal with sudo su - Type in your password (NOTE: You will not see your password) and then press Enter / Return => The Username should now be root@your-system-id:~# Enter the following command (as root user) sudo teamviewer daemon restart => This will force the TeamViewer Daemon to restart and "capture" the Internet Connection => Now TeamViewer will work until you restart your computer or shut it down and you will need to do this again. => If you set TeamViewer to run on system startup then TeamViewer will "capture" the Internet Connection and you will not need to do this every time.
... View more

TeamViewer 12 now requires the following terminal commant to be entered into Terminal to work on up-to-date Linux (Debian based) Operating System as Root User... sudo teamviewer daemon restart otherwise it will not be able to connect to the TeamViewer Servers as TeamViewer 12 can not "grab" the Internet Connection. TeamViewer 12 is no longer in development and so this will not be fixed. TeamViewer 13 and now 14 are still incomplete and for over a year I have paid for a Professional Licence so I can use TeamViewer 13 and 14. What is missing is the feature available in TeamViewer 8, 9, 10, 11 and 12 where when we issue a Remote Reboot on a Remote Windows Operating System and we are prompted to automatically reconnect to that Remote Machine after the reboot. As a IT Technician I rely on this feature to do my job and always have! How long must we constantly wait for a full and feature rich version of TeamViewer 13 or 14 to be released that is simply able to perform the same tasks as their predecessors? This is interfering with my business and my ability to provide stable Remote Support Services. Others, including myself have paid for something we have been unable to use and still can not fully use. You have no issue in demanding we pay the invoices you send us to use this service and yet this service has not been ready and is still not fully ready after 13 months. You used to have pride in your software and over the last 13 months you have demanded we pay, which we have and you have built the software around us and it is still incomplete. It is time to stop dissappointing us Linux Users and just provide us with a fully feature rich product that is able to equal its predecessors and then you can start to focus on new features and enhancements. We have paid so it is well overdue you do your part and give us what we have paid for!!!
... View more

This has been a problem since the half baked TeamViewer 13 and it has been passed on in TeamViewer 14. In TeamViewer 12 and all version I have used below we were able to issue a simple reboot. TeamViewer would run on the guest machine at system startup and we would be able to log into the guest machine. Not anymore and what I do not understand is why as this is a key feature of TeamViewer and we need it back. TeamViewer should never have released TeamViewer 13 in the "Preview" nonsense it was and a native linux version should have been built in the background rather than giving us a broken and incomplete product. I am absolutely dissapointed this has not been fixed in TeamViewer 14 and that means that it looks like for another year I will be forced to use and deploy TeamViewer 12 because the developers are not focused on giving all the features we use to have to the native linux version. It is reaching the point I might need to look at other Remote Support Providers who care about their clients and develop fully working products.
... View more

TeamViewer 13 has been the biggest disappointment I have ever experienced with TeamViewer. I have paid to use TeamViewer 13 as a full and proper version with all the features and abilities of TeamViewer 12 and it is now August of 2018 and I am still to have a full and ready to use version of TeamViewer 13 I can use on my Linux Business Computers. I tried the other day to use the updated TeamViewer 13 for Linux and I had to apologise to my client and downgrade back to TeamViewer 12 so I could provide proper, reliable remote support. I honestly believe 2018 will pass and TeamViewer 14 will be released before we are given a full, reliable and feature rich version of TeamViewer 13 which can operate and function the same as TeamViewer 12 does. Until a full and matching version of TeamViewer 13 is released there should be a clone of TeamViewer 12 with a upgraded Version being “13” so we can do the work we paid so much to be able to do, not this preview garbage that has been incomplete since it was released and is an embarrassment when I look incapable when it is the “preview version of 13” not having all the features TeamViewer 12 has.
... View more