No connection to TeamViewer server

I'm using Fedora Linux, and successfully installed teamviewer_11.0.67687.i686.rpm. But I'm getting a dialog "No connection to TeamViewer server. Please check your internet connection. Most likely you use a proxy server and you have to enter the proper information in the options dialog."

$ sudo systemctl status teamviewerd.service
[sudo] password for chris:
● teamviewerd.service - TeamViewer remote control daemon
Loaded: loaded (/etc/systemd/system/teamviewerd.service; enabled; vendor preset: disabled)
Active: active (running) since Sat 2016-11-12 13:08:18 PST; 18min ago
Main PID: 4751 (teamviewerd)
Tasks: 14 (limit: 4915)
CGroup: /system.slice/teamviewerd.service
└─4751 /opt/teamviewer/tv_bin/teamviewerd -d

Nov 12 13:08:18 f25h.localdomain systemd[1]: Starting TeamViewer remote control daemon...
Nov 12 13:08:18 f25h.localdomain systemd[1]: teamviewerd.service: PID file /var/run/teamviewerd.pid not readable (yet?) after start: No such
Nov 12 13:08:18 f25h.localdomain systemd[1]: Started TeamViewer remote control daemon.

I've also stopped firewalld just to test if it's the firewall. And there are no SELinux AVC messages. So I can't figure out why it can't connect to TeamViewer servers. On a Mac, on this same wireless network, I don't have this problem.

Find more posts tagged with

Accepted answers

Hi all,

I've the same issue.

I tried the tarball (for unsupported systems) and it is working.

Kind regards,

Soeren

All comments

Hi all,

I've the same issue.

I tried the tarball (for unsupported systems) and it is working.

Kind regards,

Soeren

PetkoDoichev

I found more info about the problem.

If you login with gnome Xorg, you can use teamviewer without problem, but if you use wayland, teamviewer cant connect to server.

oglop

restarting the daemon works magically

systemctl restart teamviewerd

service teamviewerd restart

keeeeeinplan

Hi Soeren,

thanks for the idea with the workarround installing the tarball, works with Fedora 25!

Kind regards,

Cornelius

chris_tv

If running on Linux, try restarting the TeamViewer daemon, e.g. 'service teamviewerd restart'. I can't remember where I saw this suggestion, but this works for me. The explanation was that it's caused by a race condition. Hope it helps someone.

dpayton

This worked for me on Zorin. Thanks!

vongts

It becauses of IP V6.

I got the same issue then I check this case, using mobile to test teamviewer I see it works but not work with my wifi. So I think this cause of my network. Called to network service they came and check and see that my network use both ip v4 & ip v6 (maybe switch sometime between v4 & v6). Then they set it use ip v4 only then Teamviewer works for me.

Hope that it help for someone got issue like me.

Regards,

ivanxx

Well, for those having problems even with the tarball, I just discovered that it wil not work if you install the tarball (tv-setup install), but it will if you run directly the teamviewer executable in the folder where you extract the tarball.

From what I can see, the difference is that a so-called "Network process" is not started when you run it from the installed version while it does start if you run teamviewer directly from the folder where you extract the tarball. More than a Wayland problem this seems like a permissions problem when you install under Wayland...

PetkoDoichev

Hi
1. I tried to install teamviewer through software center, but it said "File is not supported", so I try through terminal and I succeeded. But it can't connect.
2. I use gnome 3.22 and nautilus.

AmrAbdeen

su teamviewer

Fedora 25 wayland

Regards,

Amr

m4b0

I'm using wayland and I'm confirming that TeamViewer is working using the tar.xz file.

DamienCassou

> 1. How did you install TeamViewer on the system (softwarecenter or terminal?) and which version are you using?

dnf install -y https://download.teamviewer.com/download/teamviewer.i686.rpm

> 2. Which display manager is installed on the system?

The default one on Fedora 25: Gnome 3.22 + Wayland

Julia

Hi all,

we talked to our development regarding this.

It happens when you do an autoupdate form Fedora24 to Fedora25 - this is a bug in our current version. We are already working on it and I will inform you when we have fixed it.

We apologize for the inconvenience.

ReynierPM

I am using Fedora 25 as well and I am having the same issue. I am using the latest 12 release. Any updates on this?

JoaoMeisen

$ su teamviewer
su: user teamviewer does not exist

[root@localhost]# teamviewer

Init...
 *** TeamViewer can not be executed with sudo! ***
 Either use your normal user account without sudo
 or use a the real root account to log in to your desktop (not recommended!).

I'm sorry but I've failed to see how this resolves anything...

GeminiAlpha

some time ago I upgraded from v11 to v12, result:

No connection to TeamViewer server.

updating v12 to a newer version, result:

No connection to TeamViewer server.

hold your breath, they have problems, i think!

Henrywong

Now is good,they are data case is bad,tomorrow waste so many time:(

daxryan

same here... no connection to teamviewer server since April 9 upgrade

Telbiur

No TeamViewer Network Access (185.188.32.0/24)

We are an ISP. Our customers report that they can not use the program.

Below tracert to master1.teamviewer.com

C:\Documents and Settings\Administrator>tracert master1.teamviewer.com

Trasa śledzenia do master1.teamviewer.com [185.188.32.1]
przewyższa maksymalną liczbę przeskoków 30

  1     1 ms     1 ms     1 ms  mt-polna [10.140.4.1]
  2     1 ms     *        1 ms  10.0.140.1
  3     2 ms     2 ms     2 ms  78-131-235-6X.tktelekom.pl [78.131.235.6X]
  4     9 ms     7 ms     7 ms  83.238.248.228
  5     6 ms     6 ms     6 ms  te0-0-0-13.ccr21.waw01.atlas.cogentco.com [149.6.70.49]
  6    19 ms    18 ms    19 ms  be2253.ccr42.ham01.atlas.cogentco.com [154.54.61.1]
  7    27 ms    27 ms    27 ms  be2816.ccr42.ams03.atlas.cogentco.com [154.54.38.209]
  8    28 ms    28 ms    28 ms  be2440.agr21.ams03.atlas.cogentco.com [130.117.50.6]
  9    28 ms    28 ms    28 ms  ae-12.r02.amstnl02.nl.bb.gin.ntt.net [130.117.14.250]
 10    29 ms    28 ms    29 ms  ae-7.r25.amstnl02.nl.bb.gin.ntt.net [129.250.2.158]
 11    33 ms    36 ms    33 ms  ae-9.r20.frnkge04.de.bb.gin.ntt.net [129.250.3.76]
 12    33 ms    32 ms    33 ms  ae-1.r00.frnkge06.de.bb.gin.ntt.net [129.250.3.11]
 13    33 ms    33 ms    33 ms  83.231.214.146
 14     *        *        *     Upłynął limit czasu żądania.
 15     *        *        *     Upłynął limit czasu żądania.

Mersault

Same issue since I updated to version 12. I'm on Ubuntu Gnome 16.10 and installed through the debian package on the web.

Remote connection is working but I cannot login to my account

GeminiAlpha

some time ago I received a mail. TV crew answered, they are still working on it.
It looks to me it's difficult, because it already took some time...
Hold your breath...

regards, Geminialpha

zeljan

Fedora 25 without wayland (KDE Plasma), restarting teamviewerd service fixed my problem.

joannachua72

hi, i am also having this same problem with my team viewer as mentioned below.

may i know how i can have this solved?

joannachua72

hi, i am also having this same problem with my team viewer as mentioned below.

may i know how i can have this solved?

phpolo

I found only one way to clear this problem occured few days ago...

I have unistall Version 13 and reinstalled old version 11 now every thing work fine.

DO NOT UPDATE SOMETHING WOIRKING

oesponda

Thanks, that fixed my problem.

Nielsen_Knowhow

It sound reasonable - As far as I remember, the root cause at my system was that the program had not the right permissions to open a window in Wayland - Hence it was not allowed to start the session in a Wayland window. For the time beeing I only run TeamViewer from my workstation - It uses Xorg due to some Nvidia driver compatibility issues... My notebook however, still has the issue, just chose not to use it for TeamViewer...

ryant22

That did the trick for me Fedora 27 - Wayland

joshuakL

sudo does not work. but running from su does.

teamviewer

Im running arch wayland

joshuakL

you need to

teamviewer

sudo will not work.

Quick Links

All Categories
Recent Discussions
Activity
Unanswered
Groups
Help
Best Of