Error Message: Waitforconnectfailed
Comments
-
This might be the best solution.
I have had this issue on too much a variety os systems to pinpoint another source other than a TV issue.Rebooting, with no config change sorts it ALWAYS.
As I see it, if a computer shows up as online, then some sort of comunication channetl is available to TV server (ie, not blocked in any way)
I am sure that, through code, this channel could be used for a remote session (even if slower, or limited).
I have TV 13 license, and was thinking about upgrading my account (I need mobile support more frequently), but now I think I'll invest my money on a alternative solution to install alongside TV, or eventually replace it.0 -
This is real problem. I have two machines (out of 30-40) with this issue. I was able to connect this morning and I know that they are on line. Asking customer to reset is embarrassing. Installed version is version 13 HOST. Must be TeamViewer bug of some sort.
0 -
Any solution for this error yet?
0 -
Ok.
That was it for me. I first noted this issue last year and it happened every now and then. Now, it occurs almost every day, on a variety of sistems. I am fed up with the ignorance of TeamViewer staff and whole the money I have payed for a connection sistem that is not worth it.
I am sorry but I cannot continue like this. I am a support business and in my TV console I have almost 100 computers. This issue affects almost 10% of my remote managed computers, on a daily basis, with any configuration, any type of connection so is nobodys fault except Teamviewers.
I am pretty sure that it is something that can be easely fixed by a software update, but Teamviewer does not care.
All they care is charging a lot of money.
I am switching to **Third Party Product** as we speak.
0 -
this is hilarious, the forum automatic moderator replaced **Third Party Product** in my previous post, but if you look above a few posts, someone else clearly states that name and it was not replaced.
this is weird conspirational behavior from TV.
i am switching right away ...
0 -
Dear
Mr./Madam TeamViewer
I had problem like Re: Error Message: Waitforconnectfailed, I was looking for resolve from forum teamviewer, but I didn't found conclusion for over come this problem.
please from your employee team for resolve my problem
Best Regrads
MRP24
0 -
Dear @MRP24,
Thanks for your post.
Is it possible, that you restart the service of the TeamViewer software for both sides?
If you restart the services, the connection should be possible afterwards.
Looking forward to your answer.
Best,
NataschaGerman Community moderator 💙 Moderatorin der deutschsprachigen Community
1 -
How does one restart the services on the remote side, remotely? Your suggested solution assumes that somebody on the other side is available to restart it. That may be the case in some situations, but there are also many situations where the remote machine needs to be accessed right now, and there is nobody there, or nobody that has the technical knowledge to restart the service. So your proposed solution really isn't a real solution. If we didn't need reliable remote access, we wouldn't need TeamViewer. Please escalate this issue up the chain so it can get a true fix.3
-
Agree...I posted a reply to @Natascha's comment, but somehow it didn't get through.
You essencially sum it up, more often than not there's no-one at the other side, and many times restarting is not an option ( tasks are running and we need to see them through).
Also, if it's a server, restarting handing out admin credentials to users ( not an option).Opening the logs you see stuff like:
"CTcpConnectionBase[64]::HandleResolve(): Resolve failed, master4.teamviewer.com, Error: system:11001"
and then you use an alternative software to connect remotely, ping master4.teamviewer.com, and it resolves.
Error 11001 means nothing to us users, and during a 3AM call I don't want to google around for a possible solution. More meaningfull/usefull error would be nice.
TV is a remote support tool, it must be resilient to computer issues ( to a point, obviously).
In order to make TV more resilient to newtork errors,namely nameresolution, why not have a local copy of TV server's IP addresses?
And if connecting to one server fail, why not "round robin" to another IP?
If a certain host shows up ONLINE then it should be reachable remotely, because obviously it is communicating with TV somehow.
I run a "one man show", providing IT support to nearly 40 clients, so I need a reliable IT support tool.
Next week will begin testing an alternative solution, and not sure that I will upgrade to TV 14 ( I have used TV since version 11, and I am now on TV 13).
Best regards from sunny Portugal,
Cláudio João3 -
On the same page with ClaudioJoao In his post just replace 40 with 70, and Teamviwer 11 with 9, and you got my case, so a little worse.
0 -
Hi,
I am trying to use TeamViewer to connect to my home computer (a Windows 10 PC) from another computer (a Windows 7 PC). I have installed the software on both machines and have checked that it is indeed running, but every time I try to connect I get the following error
"No connection to partner! Partner did not connect to router. Error code: WaitforConnectFailed"
Your resource centre is not particularly helpful with this, because the advice is just to reinstall the software on both machines and/or shutdown and restart the software. I have done both of these things several times, but same error. Having read all of the other posts about this, it would seem that lots of people are having the same problem but nobody seems to have an answer (other than use other software).
Please advise.
Charlie
3 -
Hi,
Can you give me informations about this "Third Party Product"? What is this and where can I find it?
I have the same problem as you sinds years and years and TemvViewer staff never made anything for that.
Problem is that I have nobody on site to "restart" my compuyters, miles and miles from home...
Vincent.
0 -
He means like **Third Party Product** - I do the same as no one product is fully reliable when you have nobody on site. **bleep**, but a fact of life.
0 -
Specicying the DNS Server Addresses for the Windows Network Adapter resolved the issue for me, or I should say avoided having it again. TV resetting on both sides needed to take place first. Tracking the Event Viewer I came across the unresponsive DNS warning for teamviewer server request and that's why I went ahead and specified the DNS. Firewall issues can also cause it as one of the posts suggests. Have you resolved yours ?
1 -
Has anyone found a solution other than rebooting? I have this problem with one of my remote systems. Usually if I keep trying to connect eventually it will go through, but recently it has been taking around 10 tries which is frustrating and time consuming. Restarting does seem to help for a short period of time, but after 1 or 2 days the WaitForConnectFailed error comes back.
0 -
Already uninstall and install host TeamViewer, the client TeamViewer is online but cannot connect.
0 -
I setup a Raspberry Pi4 for use at a remote site - it was on my LAN (via a powerline adaptor) and HDMI to my bedroom TV. Setup Teamviewer Server as well as "Third Party Product" (as a backup) - I could get in as well as a friend outside of my network.
I then moved the Pi4 to another location - still on LAN via a powerline adaptor. I get the same "WaitForConnectFail" error with Teamviewer and even "Third Party Product" fails despite IP scanner seeing the Pi4 and "Third Party Product" on my laptop picking it up (but won't connect).
Very annoying as this was meant to be placed at a remote commercial site so we can control some equipment.
0 -
Found the solution on a post regarding "Third Party Product" - it solves the TeamViewer issue as well.
This issue does not affect TeamViewer and "Third Party Product" on a Raspberry Pi3B+ possibly due to a different graphics setup.
* * * * * * * * * *
I assume "Third Party Product" relies on the being a GUI/desktop to access just like VNC does,
but when the pi4 is booted without a screen connected then there is no GUI/desktop started, so you probably need to do the same as you would if you were using VNC and set a default screen resolution which forces the pi to run the GUI/desktop even though there is no screen connected.
you need to run
sudo raspi-config
go to Advanced options > Resolution (I found that it should be the graphics option menu not the advance option menu)
and set a default resolution that is not the same resolution as the screen you plug to the pi.
0 -
Hi,
I have latest version of TV and I am connected to Internet, I can see on my TV Ready to connect but I am not able to connect to my ID as well as no outbound. Steps I have performed
- Un-install TV and re-install
- Un-install Anti-Virus
- Windows Firewall disabled (Public, Private & Domain)
While connecting from outside to my laptop getting following error
When I connect to from Laptop to outside getting error
Could not connect to Partner
If I am posting on wrong forum do guide me correct one.
Thanks
Rajesh
1 -
This is still happening four years later and still no solution?
2 -
I recently ran into this. After looking into it for a long time, I found out that you need to have a monitor connected to the device that you installed TeamViewer on when trying to connect to it remotely.
My coworker found some old instructions stating that you had to edit a text file line (on the Pi OS that we are using), in order to bypass the monitor requirement. I'm not sure what the equivalent file is on Windows or Mac. But here is what I found for it on Raspberry Pi:
- Enable booting without HDMI
- sudo nano /boot/config.txt
- Remove # from hdmi_force_hotplug=1
- If it is still not working disable GL drivers
- sudo raspi-config
- Advanced Options
- GL Drivers
- Legacy
- sudo raspi-config
I highlighted the fix for Pi. All I did was delete the # from that line, hit Ctrl+O and Enter. It saved the edit after that.
I'm guessing you would see something similar in Windows but you would see a 0 instead of a 1, so you would just change the 0 to a 1 and save the file. That should force the graphics card online even though a monitor is not connected to it. Mac might be similar to Pi. I didn't have to use line c, but included it just in case.
I hope this helps, or at least gets you going in the right direction. It's been a huge headache for me these last couple of weeks.
0 - Enable booting without HDMI
-
We're using Intel NUCs running Ubuntu OS and I'm getting this error as well: WaitforConnectFailed
I am able to connect if I use the Remote Control option and input the ID and password (of course, I have to have someone on site to provide it). I've tried relaunching TV and restarting the NUC, but still getting the same error when trying to connect from the "Computers and Contacts" part of the Mac app. This is only happening for some of our computers. I'm unable to identify a common denominator for the ones experiencing this issue.
What am I missing?
0 -
Hello, did you manage to find a solution?
This is the teamviewer error that really upsets me with teamviewer, get it all the time, and unable to find a common reason.
Some people say restart service, restricted remote users can't do that, and many time restarting router / computer will not solve the issue.
It seems that TV works fine if everything is working perfectly. Sadly, and I think I'm talking for most of us, we need to connect mostly when something is not working perfectly. My best solution to this has been to install a second remote acess on the computers.
If I could I would switch to another remote access solution, but at this moment it's not feasable, so I'm stuck with this.
0 -
Just a quick update on this, I have some success if i disable IPv6 on the network cards.
On windows, you can try and set TCP / IP to prefer V4 over V6, or disable V6 entirely.
Check here: https://docs.microsoft.com/en-us/troubleshoot/windows-server/networking/configure-ipv6-in-windows
Saddly, all this has to be done before you actually need to use TV remotely.
Hope it helps.
0 -
I am having the same problem. What is the solution?
0 -
What is the solution?
0 -
Try flush DNS cache, it works for me
1 -
Can confirm that running ipconfig /flushdns and then ipconfig /registerdns on the remote client machine fixes this. Troubleshot the network side WAY too long to then end up frustrated and looking through these online solutions. Glad I found kobean's post!
0 -
[Removed per Community Guidelines]
0
