Teamviewer 8 - Not connecting

[KWilliamson]

Hi, As a long time user of teamviewer I am not happy with the latest version.

I have had no problems since I started using teamviewer....... until I installed Version 8. I am consistently unable to connect.

This morning the PC had rebooted for Windows updates, so I logged in and went to work. When I got to work and tried to connect I got a message something like "remote pc failed to connect to router", But showing online in my partner list. Finally gave up and got m,y wife to re-installed version 7. No problem. Connects immediately.

I am running Windows 7 64bit home with Vipre antivirus.

Please get this fixed as soon as possible. Luckily I have found the "turn off automatic updates" in the advanced options.

[matt]

What version are you running at work.

You can't connect to a ver 8 from a ver 7

[KWilliamson]

Was running a non-installed version 8 at work. When I downgraded home, I switched back to version 7.

[KWilliamson]

Further update. Despite selecting do not upate in the settings, I somehow now have 2 versions on teamviewer installed. And since I'm at work there is nothing I can do about it AAAAAAAAAAAAAAAARRRRRRRRRRRGGGGGGGGGGGGGGGHHHHHHHHHHHHHHH!

[KWilliamson]

Got home from work and sure enough I have teamviewer 7 and 8 installed. I have uninstalled version 8 and I can connect again from my ipad.

[OlafE]

I experience the same with TeamViewer 8, connecting to a Windows 8 x64 machine from home to work.
Was running well for a while, but suddenly I lost the session screen. (Had the same during the beta, as my frontend machine updated itself to RTM and non corporate. But now both machines are installed with corporate license.)
Status shown is unknown (was that way before), and ready to connect. If I click Connect, connecting is shown forever in the lower left bottom.
There is no way to reconnect again, and of course, since office is 100km away and it's weekend, nobody can reboot that workstation until Monday.
Currently too unreliable for business use!
Best greetings from Germany
Olaf

[Demosthenes]

I have a similar issue, but not yet sure if it is the same. Was working fine with Teamviewer V7 on Windows 7 64 bit, now that I've put TV8 on the home computer and tried to remote in from work (using 8 setup.exe portable) it doesn't connect with the v8 but will connect with another v7. Same internal network, no different settings from when it worked except the version number. I did notice something in my log:

Code: [Select]

CConnectionThread::CmdEndSession(): Received CMD_ENDSESSION with reason: 3

So it's connecting and then disconnecting without any notification on my end other than going from connecting to waiting to connect. No error pops up, no reason why it won't show me a window, not even a glimpse of the remote screen, nothing.

Will go back to tv7 on home and work comp. Hopefully they never stop supporting 7 or they fix 8.

Anyone have a definition of what the reasons mean?

[KWilliamson]

Log files submitted to development for investigation. Hopefully a fix will be on its way soon.

[Sants]

rebump.

I am still facing this issue with v8, latest update in both clients.

Please update.

Thanks,

S

[matt]

This is a fan run site, this is not official support from TeamViewer.

Personally I find that if I have latest of ver 6,7 or 8 at both ends (just the latest of a version, not necessarily the same version) then I can connect across version.

[garyfritz]

Has anyone made any progress with this issue?  I never used TeamViewer all that often, but I have not been able to use it at all since the TV 8 release.  In 7 it used a "connection ID" on the target system, and that worked, but as soon as they switched to IPs it broke my setup.

I just tried it again.  I'm trying to connect from an iPad (version 8.0.10338 CL) to Windows 7 (version 8.0.20935).  I've verified that I can ping the Windows system IP from the iPad.  My Windows Firewall has 4 rules that allow the correct v8 executable.  (Not sure why there are 4 rules -- the TV installer created them.  There are two TCP rules and two UDP rules but otherwise they appear to be identical.)

But TV says "A connection could not be established.  Reason unknown."

Help!?

[Admin]

has anyone with this issue send a report to teamviewer through the official channel?
As Matt pointed out, this is a user based support forum, but there another resources available , the more that send a request to teamviewer the more likely we are to get a response from Teamviewer
use the link in my signature

[garyfritz]

I hadn't, hoping that somebody here had the answer.  Since I haven't gotten any results here, I went ahead and submitted a ticket.  I'll let you know if they resolve my problem.

[garyfritz]

I submitted a ticket, and they were useless.  "We don't see anything wrong with your logfile."

But I figured it out for myself.  The ID for the controlled computer showed as an IP address (actually several IP addresses).  In the lower left it said "Only LAN connections are possible."  Which was what I wanted -- I just want to control my system locally, and not have it respond to any external requests.

But then I went into Extras -> Options  -> General, and changed Incoming LAN connections from "accept exclusively" to "deactivated."  This was necessary to connect to a TV meeting I was invited to.  But I noticed it also changed the TV ID to a 9-digit number, like it used to be.  I tried that, and shazam!  Connection.

So local IP connections don't work for some reason.

[RandomTechPerson]

....
I am running Windows 7 64bit home with Vipre antivirus.
....

I noticed you said you have Vipre antivirus... At my company, we use TV8, and have experienced multiple issues with vipre updating TV8. We have some clients that have the vipre software and when we restart their PC, (despite turning off automatic updates  in TV settings) it still would update TV regardless. Once we removed vipre from the equation, we no longer had issues with TV automatically updating (or being updated by vipre) to the later versions. (in our situation, it was updating to TV10). Try removing vipre and restarting a few times to see if it updates automatically