![]() There are links to download Ubuntu DEB files and Fedora RPM files. However, it does not explain why TM seems not to work properly on a 'random' basis. To install TeamViewer in Ubuntu and Fedora, fire up your browser and navigate to the TeamViewer Linux download page. Here is a workaround that allows TM to start viewing sessions and to connect to an account : sudo systemctl stop rvice sudo systemctl start rvice teamviewer & I am running Teamviewer 3 under Linux Mint Sarah. I have no idea whether this is related, but the misbehaving system has been part of a domain for a while, but I have since left that domain and cleaned up group policies as well as I could. If you use Manjaro, you can install TeamViewer from the Arch User Repository (AUR). (You basically connect by IP rather than by TeamViewer ID - which doesn't help me much when I am not in my LAN.)Īfter login of any user, the systems becomes and remains accessible (visible and connectable, with no interruption of existing connections) until reboot of the machine, even after this user (or all users) logs out - so it seems to be TeamViewer Service that, correctly in principle, handles this connection, but fails to connect to the TeamViewer server before I am logged in.Ī second system Windows 10 system of mine, on the same network, behaves normally, that is, accepts remote TeamViewer connections before user login. However, after reboot, that system does not appear in the list of my online computer and can only be connected to by LAN connection. Yee Haw… here we are again on that roller coaster of lifeīack on top of the lift hill, ready to roll down to the rest of the week.I have setup TeamViewer on my Windows 10 system to be accessible before user login: I have set it up to start with Windows, associated it to my TeamViewer account, granted easy access to myself, set a fixed password, and allowed incoming LAN connections.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |