![]() ![]()
I have completed some of the steps in the Wake-on-LAN manual. TEAMVIEWER WAKE ON LAN TUTORIAL PCThere will be a period of time where I will be away from home and would like the ability to wake the PC from sleep mode. ![]() Now, if the port forwarding doesn't work, I don't have a fix, and if you found one, I'd love to hear it, but at least it would narrow down the issue. Teamviewer is loaded on both my PC and laptop. You could do the same to check if your router is doing that properly, unless, aas stated above, an online tool should return a negative result for some reason. Now, either I am understanding something wrong and this should be how it would appear externally, or my FRITZ! Box simply isn't forwarding port 9 for some reason. Now, to make sure the port forwarding was owrking, I used several online tools that connect to your external IP with a given port and check its status, all of which returned it was being trashed/filtered, meaning my router wasn't forwarding it. I then went ahead and configured port forwarding in the FRITZ! Box for port 9 at my PC, and configured Teamviewer to use the DynDNS I get with (which I made sure works by pinging it, which connected to the correct external IP address) and port 9. For me I find that the ideal sweet spot of security and usability.Have you checked if your port forwarding is working correctly? I am currently trying to set up Wake on LAN for my home PC, and the PC itself is configured properly, which I have made sure of by connecting to my router (FRITZ! Box) via from a different location and turning the PC on from there. That's obviously super-secure providing you have your SSH config logged down (public key auth etc). What I've always done for WOL is have my router contain the wakeonlan binary and have an SSH session on my phone which is preconfigured to connect home (via the dyndns, say) then run the correct wol command and exit. However although that is convenient I just don't like the thought of having WOL open to the internet at large (although seeing as there is no reply from the port, using a non-standard port here is one version of 'security through obscurity' that is actually perfectly fine). TEAMVIEWER WAKE ON LAN TUTORIAL MACIt is possible to have WOL port-forwarded directly form internet into your LAN but some firmware won't allow you to forward to the broadcast address so you need to 'spoof' a new broadcast address by mapping that magic MAC address (FF:FF:FF:FF:FF:FF) to a different IP and forwarding to that. To find the MAC address, ensure the PC is connected to your router via a wired Ethernet connection. If you can do the latter then the Dyn client can run anywhere on your network, not necessarily on your 'main' router.Īlso some advice on WOL. Have the MAC address ready for the remote computer that you would like to wake up. I'm not sure about Tomato but certainly on DDWRT there is config as to whether to use the interface IP, or the public IP as determined by querying an external website. Not sure you can send one over the internet, but do try. Normally you need to connect to a device that is capable of sending a magic packet, like a server or an enterprise-lite router like a EdgeRouter Lite or Mikrotik. ![]() The first method simply requires you to configure the hardware of the target computer and configure TeamViewer on it in order wake it up from another device connected on the network. This can be done via another computer within the same network or via its public address. Do you know if this works already? You don't need to have DDNS installed to test it, you can do it via phone connected to 3/4G. TeamViewer’s Wake-on-LAN feature enables you to turn on a computer that is turned off or in sleep mode. Now, for magic packet / wake on lan, you said via teamviewer. This is what I think they actually have done. Basically if they never thought that the router doing the DDNS could be a secondary one, then they might have just set it to "pick your wan IP address and send it to DDNS provider". TEAMVIEWER WAKE ON LAN TUTORIAL SOFTWARENow, the issue is how the tomato software was coded to do this. After all it's a service and it just sends info out to the DDNS provider. I am not sure if you need the internet facing router to be the one that manages DDNS, it does stand to reason, but I also could not think of any reason why it could not be managed by another device behind the router, like another router or a PC. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |