My "Wake-up" command no longer works. (Free version) Is it something I did?
I now have to physically turn on my desktop computer.
Very sad, but at least it is now clear what the issue is mentioned - although the error in the TeamViewer Client is not helpful that a not sufficient license was the root cause. Maybe that could be improved, e.g. by blocking the setup of the wake on LAN settings when not having a sufficient license. Then it is more clear that it won't work.
Moreover I think the note "This article applies to Remote Access, Business, Premium, Corporate and Tensor customers." in the Knowledge Base article can be easily overseen and I think it is not 100 % clear that the Wake-on-LAN feature is not available in the free license. @JeanK Maybe could you add a similar statement like in the forum "The Wake-On-LAN (WOL) functionality is not available to free users".
Additionally, I would appreciate if there would be a table overview which feature is contained in the free license and which not so it can be compared to the different paid licenses: https://service.teamviewer.com/en-de/overview
That is an appalling example of the contempt with which TeamViewer decision makers view both their users and the front-line staff who have to deal with contributors to this forum, who were clearly kept in ignorance of the changes made to the functionality of the product. Caveat emptor. TeamViewer, you have successfully driven me away from being a promoter of your product; I will now permanently stop using your product and adopt the alternative that you drove me to find.
I thought I was the only one. My "Wake up" command stopped working last Sunday, December 4th. I thought maybe it was something they had done like disabling it for the "Free" version, so I signed up for the single user version today and it still does not work. Let me know if you find a solution.
PS: I have found a windows program and iPhone App that do work so I am pretty sure it is not something on my end.
I posted my problem description above, just wanted to add after seeing this that also I have been using NoIP provided DynDNS. So maybe something broke in the way Teamviewer handles DynDNS (NoIP specific or not?).
A fix or a functioning workaround would be greatly appreciated!
@mikulik86, thanks a lot for clarifying. This is indeed a very valuable piece of information.
I just informed our responsible team about it and will ping you as soon as I have something to share.
/JeanK
Hi all,
I spoke with our responsible team, confirming it's a known issue.
Our team is working on it to bring the functionality back at the earliest convenience.
I apologize for not informing you earlier - I thought it was linked to the new interface.
I'll inform you here once I've news to share.
Thank you all for your contribution, and talk soon!
Version 15.42.6 also fails to wake a computer that will wake from version 15.39.6.
Version 15.42.7 also fails to wake a computer that will wake from version 15.39.6.
Version 15.42.9 also fails to wake a computer that will wake from version 15.39.6.
Hi @JeanK ,
The problem must lie with the initiating computer because, at the point where wake is initiated, TeamViewer is not running on the target computer.
I am testing with one computer running the latest version while keeping the others on 15.39.6 as controls. If it will help, I am happy to provide a demonstration of my test methods or carry out other tests.
Yes, of course.
Since last week the WOL function is doesn't work. The PC and the router/firewall settings are correct because if I use other method (Mikrotik,OpenWRT,Depicus,Linux) they power up my machines. Only Teamviewers wake button doesn't work. Why? I had used since several years ago without problem.
Many thanks
Same issue here . . . thought it might be due to system/windows updates, but it still does wake using a different program, so it's gotta be something with Teamviewer.
I have been using TeamViewer to wake a remote computer successfully for several months. All of a sudden it stopped working yesterday. I have two different remote computers and it will not wake up either one of them now.
I am able to use a separate windows program to wake up either computer over the internet so I know the computers can be powered up remotely.
Any suggestions would be apprecieated.
I had wake working well on Teamviewer for quite some time, and as of a few days ago, it no longer works. As you mentioned, I can connect while the computer is on, but it no longer wakes it up if it's off. Seems a few others have had the same issue recently, so thinking it must be something on the teamviewer side. I have an iPhone & started using Wolow, that wakes up my computer both on a local network, as well as thru DDNS, you might want to give that a try. Another app that only works locally for me is Wake Me Up.
I've been trying to get wake-on-LAN set up for one of my computers using an always on pc on the same network. I've followed the setup guide, but not only does it not work still, but now when the target PC is shut down, teamviewer on other devices shows that the target PC is still on. This of course removes the "Wake" button.
Fast startup disabled, BIOS setting set to allow WOL, both computers connected to the same network via ethernet, network adapter settings in windows set to allow this device to wake this computer, and magic packet checked.
Attempts to connect to the target PC while it is off result in "Error, No connection to partner! WaitforConnectFailed". As per some google searches, I disabled IPV6 on target PC and nothing changed.
I can connect to the always-on PC just fine, and when the target PC is turned on, I can connect to it as well. Just can't wake it, as the option won't show up seeing as the target PC shows online even when powered off.
I have WOL enabled for 2 machines in my local network. This has been working without problem for months, but in the last 1-2 weeks I can no longer wake the other machine.
Nothing has changed in either PC and the WOL is configured correctly as it has been working without any problems.
Anyone else having the same issue?
Hello everyone,
Thanks for this feedback.
We are more than happy to take a closer look and investigate this issue. Could you all please let me know if Wake-on-LAN is configured using the public address on the affected devices?
Thanks in advance!
Josh, mine is indeed configured using the public address.
Like many others mentioned, I also can no longer access TeamViewer using WoL as the precursor to login to a remote device.
TV WoL has worked seamlessly for many years and early in December just stopped! Despite checking and rechecking my settings, nothing changes. I can use TV to access remote device provided remote device is running! I can wake the remote device using other methods via mobile devices (magic packets) - all as mentioned by others.
It seems to be a TV issue, but any advice would be appreciated.
Regards
Yes, it is not working for me either.
I configured no-ip, set WOL, open port in router.
It used to work perfectly, but not 1-2 weeks ago.
same here
I have a DynDNS (provided by NoIP) set up on my router for various reasons, one of which is teamviewer's remote WoL feature.
However, recently (I'd say less than a month ago, after working flawlessly for over 2 years), that stopped working, and exclusively works if, as the WoL public address on my machine, I set the public IP (as in, actual numerical IP) of the router, which is not static so not a real solution.
The first thing that might come to mind is "Well, the DNS is clearly not working", but the DNS resolves correctly and works as intended in every other case, and I use it multiple times a day without issues, except for this specific situation.
Any insight on what the problem might be?
Same here
Interesting, but if i use my mikrotik's ddns address it works... only if use dyndns then not.
Just as the title says, I have confirmed that Wake on LAN is working using WakeMeOnLan, but the button to wake the device on TeamViewer does not appear. Is there a way to manually make this button appear, or another way to fix this? I'd rather not have to use 2 different programs each time, when i know WoL has worked for me before
I also have the same issue as multiple posts above. Everything was working fine, and WOL stopped working. I use No-IP DDNS. If it helps diagnose the issue, if I put my current IP address in TV settings, WOL works. If I put my DDNS address in TV settings, WOL does not work.
Any news?
What alternative did you find? Some other I found also only have this option for paid users.
Same here... Any other applications, web pages wake my PC but the TW wake button doesn't... interesting, but if i use my mikrotik's ddns address it works... only if use dyndns then not.
