I have just installed TeamViewer12.0.75813 on Windows 7 64 Bit but when I run it, the following message shows up in the lower left corner:
Only LAN connections are possible.
I read that the reason is most-likely that I am not connected to the internet, but I am definitely (I am writing this post, so...).
Solved! Go to Solution.
General->Incoming LAN connections is set to "accept" (not "accept exclusively"!)
I see this answer all the time, but it is not the solution; TV still shows "Only LAN connections are possible"
For me this is an Ubuntu/Linux issue - other computers with TV installed on the same network do not have this problem
Version 12.0.76279 wine-1.6 (latest, Mar 24 2017 00:45:31)
This may be a DNS issue on the computer that is having the problem. You have internet connection, but you may not be resolving the address of the TeamViewer servers.
You should be able to ping master11.teamviewer.com - or similar - master3, master4,..
Compare the results against one of the computers on the LAN that is working.
Unfortunately not, all resolve correctly.
I have now also tried the Chrome TV extension on the same computer, which works, so it is likely not a networking issue. Also, there are no errors in the TV log relating to networking
The same problem with Windows 10, no proposed solution is working.
Have the same problem on 2 machines running Ubuntu 17.04
Both accept only LAN connections even both are able to use the internet connection.
Another issue is that both cannot Sign In at all.
Still cannot understand why is not working
I had a similar issue and we have a Corporate Edition of TeamViewer; multiple locations, different IP's etc. We had this issue randomly throughout our locations.
Turns out that it was DNS related. We have OpenDNS in our enviornment and they changed up the way TeamViewer was categorized so it kept blocking the connections. Here are two things you can do:
Option 1: I switched mine to Google for a sec (188.8.131.52 and 184.108.40.206) and the connections / computers became immediatley available. Switched back to OpenDNS and they were blocked again. So I had to manually whitelist them in OpenDNS. Make sure you flush your DNS cache on the target computer(s) and your router once you make these changes.
Option 2: I'll list the servers below so you can whitelist them in your firewall:
Hope it works for you all!
Haven't seen much thanks, but had same issue as others mentioned on Gentoo (soucecoded linux distro). I'm using TS13 and they messed around with the layout, but problem was the same. I think I had a TS11 running nicely, and 12 no problems. I am sure solution will work, so in advance thanks. ITGuyNumber47
solved! your suggestion of DNS was helpful. Our network must've done something with the DNS
in command prompt > ipconfig /flushdns
After a minute, if nothing happens either restart TV12 or go into advanced options, set the server to some value, hit ok and ok, then repeat and set to blank.
We have installed TeamViewer 14.2.2558 Corporate licence on Windows 10 64 Bit.
Five days ago suddenly, all TeamViewer machines became inaccessible even though they have a connection to the Internet - Only LAN connection are possible?!
At the same time TeamViewer download and update work - Help / Check for new version - update work!
Machines have a connection to the Internet, but only LAN is enabled.
What's the problem with this TeamViewer version?
We have a corporate license and we suffer great damage every day for this failure!
In my case, the Teamviewer 12 service (TeamViewer_service.exe) was hung and I couldn't restart it. I had to manually kill the service, then afterwards I could start it afresh, at which point I was able to access remote teamviewer PCs & laptops outside the local LAN.
I have no doubt that an alternate solution for me would have been to simply reboot the affected laptop but reboots take longer than killing, then restarting a service.
My problem started when I moved my laptop from a hard wire connection to wifi then back to hard wire - we do it all the time at work when taking our laptops to and from meetings.
This is the first and only time I've encountered this particular issue.