Not ready. Please check your connection after upgrade to v12

Confucian

I get "Not ready. Please check your connection" after upgrade to v12

was working fine before upgrade.

Internet connection ok as it let me download the upgrade.

It keeps banging on about "proxy servers" which i have set to none as i dont have or use one

Find more posts tagged with

Comments

Ray666

Same problem, caused by Avast web shield

getinto-pc

thanks for ur info.

download here the required software at getinto-pc

edstrait

This is the one that worked for me. Stopped teamview, renamed the /etc/teamviewer/globla.conf to .old restarted Teamviewer and all was golden.

matsimo

This workaround works for me, for other people with the same issue before try to restart your teamviewerd service before modify the /etc/systemd/system/teamviewerd.service. If after the service restar teamviewer is online go a head to modify the config file. @Bloodhound Thanks for the solution.

Rps

Thanks it worked.

GlenB

My router does not support IPv6 so I never enabled it. Unless TV messes with my net config (which it should not without letting me know) then there is some other reason for the problem.

Seems that it eventually goes away all on its own ... further evidence that the problem is not my configuration. Of course if it can go away, then it can come back.

We really need a better explanation and not something that is assumed because they seemed to happen at the same time.

mcochi

The issue was IPv6. I disabled it and it worked fine.

Running Win 10 Home OS

aquintanar

Hi,

I get the same message. I was working pretty nice for several months. I upgraded some times and increase the version without any problem. But since some days ago, I get the message "Not ready. Please check your connection".

I upgraded to the version 13 Beta and until now everything works great for me.

Kind regards.

GlenB

Same error message. Have been running TV12 on Win10 for weeks with no troubles. Then this started. I have not knowingly changed any of my network configuration.But I checked.

1 - Windows Firewall is on and there are rules to let TV and TV-service run over TCP and UDP.

2 - My adapter has IPv6 off and has ALWAYS had it off.

3 - I used Task Mgr to get rid of any and all instances of TV andthen restarted the program.

4 - "Check for updates" says that I am already up to date.

None of those made the slightest difference. So I downloaded the install package and ran it again and now it all seems fine.

Not helpful to have NO IDEA what got messed up or how it happened. The error message is particularly uninformative, making a suggestion about Proxies which I don't use but have always had set as self-discover.

R0YMU5TANG

I've had to kill the background process for teamviewer and start it up again. Generally I get this when I lose internet and get it back again.

As a workaround, I wrote a .bat file that essentially kills Teamviewer and all of it's background processes, then start it up again and it works.

taskkill /f /im teamviewer.exe
taskkill /f /im tv_x64.exe
taskkill /f /im tv_w32.exe

BehradKazemi

Fixed after starting VPN

phoenix49

Thanks!!

MarinaTajPalace

No, Its not working did that.

dnemcanin

HI!

On Windows 10 I had same problem.

I stopped teamviewer services. On Teamview option I disable start with system.
After reboot teamviewer worked fine.

TuyenBui

After reading lots of comments and try many recommendations, I was successed when disable "Internet protocol Version 6(IPv6)", disable IPv6 at Lan/Wifi properties(not at router), just uncheck this option, I work like a boss. Please view the link below to detail

Fix teamviewer v12 connection on window 10

Nice day!

TDawg

Thanks! This worked for me also.

Elder-Geek

This did the trick for me. I tried stopping the Teamviewer service and it didn't stop. I then used Task Manager to stop the service. The service was still marked at stopping. I then tried to stop it again and it was finally marked as stopped. I then started the service and all is now working perfectly.

Vallefor

Omg! Thank you! You save me!

SashaS

@oiram wrote:
I have resolved on Ubuntu 17.04 executing in a terminal the following command:
sudo apt install libnss-resolve:i386

Excellent! The only real thing which worked for me (ubuntu 16.10).

johnBasinger

sudo service teamviewerd restart

This works for me. Thank u very much

subho

I was facing the same problem with v12 on Windows 10.....and it is solved after the Microsoft .NET Framework 4.7 for Windows 10 Version 1607 and Windows Server 2016 for x64 (KB3186568) update. So I believe the problem was in Windows 10 and not in Teamviwer.

I hope this will help.

oiram

I suspected it was a problem with Wine and the network, and because all worked fine until I have installed Ubuntu 17.04 I have take a look to the release notes discovering Canonical changed the support for DNS, so I googled looking for people having a similar problem with Wine and network comunication after the update to Ubuntu 17.04 and I found the solution

Ales

oiram wrote:

sudo apt install libnss-resolve:i386

That finally helped! I wonder how did you figure it out but thanks a lot.

oiram

I have resolved on Ubuntu 17.04 executing in a terminal the following command:

sudo apt install libnss-resolve:i386

LadyTramp

@MSunThis worked for me... Thank you

smart2017

I have the same problem and i have reebooth and upgrade but its still not working

ahasbini

Exit Teamviewer, open task manager and go to Services tab, find Teamviewer serivce, right click and stop. Wait until it's Status changes to stop. Then open Teamviewer again and now it connects.

TcoUpLoad

i know this is a reply to an old question but next time search in filehipo.com and for your search has this link filehippo.com teamviewer v11 and others

Phlyer

i had the same issue after upgrading my desktop and Lappy from 11 to 12 about a month ago.

I ended up uninstalling and reinstalling 12, doing a registry wipe using ccleaner, rebooting and then reinstalling 12 which made zero difference. I repeated this and reinstalled 11. still zero difference I dont have installation files for 9 or 10 so ive regressed back to 8 on both machines. Desktop is on XP, Lappy is on win 7.

If i try to setup unattended access i get the same no connection message.

Both machines exhibit LAN only connection messages, but if i use my partner ID list I can connect, even over hotel wifi from 100 miles away, but....

The link is fragile and if it drops out or gets closed in error, I cannot reestablish a connection with the remote PC unless I call home and get someone to reboot it.

before an ID was displayed, now all i have is a local IP address (on both machines).

Also cannot sign in to account (computers & contacts option).from either machine except my phone. The GUI refuses to respond to mouse clicks.

If the link drops out, i usually get "Teamviewer not running on partner computer" when I try to reconnect.

My phone has TV installed on it which has NOT been upgraded and that works fine with both machines. The thing works, just but im no nearer finding out why or what I can do to resolve the issue, which is a real pain when im away and i get a support call from one of my aged relatives!

MSun

I just simply opened the Task Manager and killed the TeamViewer processes. It started working. Possibly I am just lucky this time. Hopefully it will continue to work from now on.