Teamviewer 8 and Fedora 18

Do you have a problem getting TeamViewer 8 to start at boot time in Fedora 18 and Fedora 17?

The issue comes from TeamViewer improperly placing the necessary SystemD component to have systemd start the service at boot.  Its a simple fix! Just follow the commands below to correct!

 

sudo cp -r /opt/teamviewer8/tv_bin/script/teamviewerd.service /lib/systemd/system/

sudo service teamviewerd start

sudo systemctl enable teamviewerd.service

12 Comments

  • Bruce says:

    Thanks, this really helped! Although, I had to change your first command to:
    sudo cp -r /opt/teamviewer8/tv_bin/script/teamviewerd.service /lib/systemd/system/

    Not sure why my installation was different, but something to watch out for.

    • CubedRoot says:

      Bruce,
      Thanks for the note! It looks like I made a typo on the first command, and included an improper path. I have corrected the post with the type removed.

      Glad it helped you out!

  • Martin says:

    Hi,
    TeamViewer unnattended access on my Fedora 18 box worked once, when I installed it, since then,
    whenever I try to "remote control" the box, it just goes "Connecting" but never comes back.
    I entered your cmds above, systemd is running but nothing happens.
    I'm using TeamViewer 8 with a TeamViewerID and I am able to connect without any problems to many PCs (Win Vista, Win7 & Win2000).
    The only one that I cannot connect to is my Fedora 18 box.
    How can I troubleshoot the connection on Fedora 18 ?
    Many thanks.
    Martin

    • CubedRoot says:

      Martin,
      On your Fedora 18 box, you will need to verify the TeamViewer daemon is running. It is called teamviewerd.

      Run this command to see if it is running:

      ps aux | grep -i teamviewerd

      It should return something like this:
      root 1282 0.0 0.1 42572 8896 ? Sl 08:56 0:02 /opt/teamviewer8/tv_bin/teamviewerd -d

      • Martin says:

        Hi,

        Thanks for the quick follow-up.
        Yes the deamon is running. I checked right it right after cut/pasting your commands before.
        I tried connecting with TeamViewer, didn't work.
        Rebooted, rechecked, teamviewerd was running, TeamViewer connection wasn't happening.

        I can't paste the "ps" output since I don't have access to the machine right now ;-(
        I have access to other computers on my network but I just installed Fedora and it seems that telnetd isn't running by default ;-(

        Thanks again
        mp

        • CubedRoot says:

          Martin,
          I wonder if it would be iptables blocking the ports that TeamViewer daemon is using? Are you running iptables (firewalld) on the Fedora machine?

          • Martin says:

            I will have to check but one sure thing: I did not install this on purpose.
            But I suspect more something with TeamViewer because now it is also happening with my Win2k server.
            I was connected via TeamViewer and got disconnected, and now I cannot reconnect ;-(
            tx
            mp

          • Martin says:

            Ok, more testing showed that process is running
            root 1291 0.1 0.0 134528 24096 ? Sl 19:50 0:01 /opt/teamviewer8/tv_bin/teamviewerd -d

            And whenever I reboot TeamViewer successfully connects to the Internet TeamViewer server with my account. I can see my fedora box "online" from my other computers.
            -I click "remote control" it does nothing on both screens.
            -I "send message", it does nothing on both screens.
            -I go fedora->Internet->TeamViewer8
            -TeamViewer front-end comes up and shows my message
            -But still no remote-control from other PC
            -On fedora I go "ps -ef" and I have strange processes

            mapicard 2334 1 2 20:12 ? 00:00:00 c:\TeamViewer\TeamViewer.exe
            mapicard 2357 1 0 20:12 ? 00:00:00 /opt/teamviewer8/tv_bin/wine/bin/wineserver
            mapicard 2363 1 0 20:12 ? 00:00:00 C:\windows\system32\services.exe

            Why the C:\stuff on a fedora box ???
            I'm lost.
            tx for any input
            mp

  • Martin says:

    Also, it looks like there's a different behavior if I login as "root" instead of my regular ID.
    Logged-in as root with GNOME-Desktop environment, wine application started automatically so when I tried "remote control" from another PC, it worked immediately.
    Logout and login as root with XFCE,
    -remote control did not work
    -started TeamViewer8 manually
    -remote control came up immediately
    Logout/login with regular ID with XFCE
    -remote control did not work
    -had to started TeamViewer8 manually
    -remote control still did not work

  • Vonedaddy says:

    @Martin

    I have the same issue, seems like selinux is blocking the connection although I can not test right now.

    Try running the following command:

    setenforce 0

    That will put selinux in permissive mode. Then try the connection again.

  • Eugene says:

    You can also try free remote desktop software Ammyy Admin
    http://www.ammyy.com/en/index.html

    One of the easiest and the most fast software for desktop sharing and techsupport. No monthly fees, free for non commercial use.

    It might be a good alternative though! Hope you'll like it!

  • Its good that TeamViewer version 8 supports Linux. But I prefer using RHUB`s remote support solution as it supports Windows, Linux, Unix, MAC, Ubuntu etc.

Leave a Reply

XHTML: You can use these tags:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>

%d bloggers like this: