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.

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. 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.

Not anymore and what I do not understand is why as this is a key feature of TeamViewer and we need it back. Continued with configuring the device, then reboot - no connection. TeamViewer would run on the guest machine at system startup and we would be able to log into the guest machine. I installed TV Linux Host (latest version from TV website) and connected it to my account. By default, TeamViewer connects on port 5938 but can also use ports 80 and 443 if not opened (so it will work natively most of the time). In TeamViewer 12 and all version I have used below we were able to issue a simple reboot. What if your PC is not wired and the WIFI card does not support WOL services You can use a Raspberry PI as a WOL (Wake on LAN) server.

This has been a problem since the half baked TeamViewer 13 and it has been passed on in TeamViewer 14.

Raspberry pi teamviewer not ready