Forum Home
Press F1
Thread ID: 143008	2016-10-30 10:54:00	Help with Teamviewer wake on LAN	Chikara (5139)	Press F1

Post ID	Timestamp	Content	User
1428003	2016-10-30 10:54:00	Hi all, I use TeamViewer, have for years - great too - especially if I am travelling and want to securely access something on my home PC, I can access it from TV mobile or from my laptop. I use to leave my PC on, mainly for this reason. I was reading about how to enable TeamViewer to use wake on LAN - meaning if I could just have my PC sleeping, and then send a wakeonLAN message to wake it up when I need to - access what I need -then have it sleep again. Saving power etc. I have read on the TV site that I can do this from either mobile or laptop via internet. I have read the TeamViewer instructions on this, and while it seems a bit complicated I thought I have followed it - but I cannot get it to work. Hoping some of the experts here can guide me and help troubleshoot for me? Firstly, I am running Win 10, latest version of TV - plus 'Teamviewer for Remote Control' on Android. My router is running Gargoyle, and my ISP used dynamic IP's. Here are the guides I have been following: 1) www.teamviewer.com (Yep I know it's for TV 9, but I can't find an updated version) 2) www.teamviewer.com (their support page) As I want to do this from the internet, it seems I need a dynamic DNS provider. SO, here is what I have done so far: - Set up a free dynamic DNS domain via changeip.com (it's set up using the domain (myname.changeip.org ) - PC is set to enable wake on LAN in BIOS - Network controller has both 'allow this device to wake the computer' and 'only allow a magic packet to wake the computer' selected in device's power management settings, and also the option 'wake on magic packet' is enabled (from advanced tab) - Team viewer is configured with Wake on Lan enabled for public address - I used the domain above (myname.changeip.org), and port 9 - In my router, in the Dynamic DNS setting, I added the same domain (myname.changeip.org) - In my router, I added a port forward - type UDP, from port 9, to IP 192.168.1.254 port 9 (wouldn't allow 255) this part was a bit confusing in the TV instructions but I think this is how it should be When I turn the PC to sleep, and then try and access it via teamviewer on Android, the PC shows offline. There is an icon that looks like a power icon, but clicking it does nothing. And yes I did test it using the mobile phones network, not from my home wifi. WHat am I doing wrong?	Chikara (5139)
1428004	2016-10-30 19:12:00	Do you have or setup a team viewer Account ? Re Read section 5.1 In order to guarantee that the computer cannot be wakened by an unauthorized person, it must be ensured that the computer really belongs to you. You must therefore assign the computer to your TeamViewer account. Only the TeamViewer account linked with the computer can wake it up.	wainuitech (129)
1428005	2016-10-30 20:02:00	WHat am I doing wrong? Just my opinion, but if you want RELIABLE remote access, set the PC to allways on. Dont try and save a few $ in power. What happens if it wont wake from sleep when you're away. What happens if the LAN/NIC goes into sleep mode/low power mode & therefore cant "wake from lan " Ive seen issues with NIC power saving/reduced link speed causing network dropouts . If that happens when youre away there might be no remote access.	1101 (13337)
1428006	2016-10-30 23:22:00	Do you have or setup a team viewer Account ? Re Read section 5.1 Hi Wainui, Yes sorry I should have also mentioned this in my first post, I have a teamviewer account, it's logged on on both PC and phone and the PC is correctly assigned to the account	Chikara (5139)
1428007	2016-10-30 23:26:00	Just my opinion, but if you want RELIABLE remote access, set the PC to allways on. Dont try and save a few $ in power. What happens if it wont wake from sleep when you're away. What happens if the LAN/NIC goes into sleep mode/low power mode & therefore cant "wake from lan " Ive seen issues with NIC power saving/reduced link speed causing network dropouts . If that happens when youre away there might be no remote access. Hi 1101, thanks, and point taken. I think I'd like to try to get the wake on LAN working first if I can, and then see how it goes. If I do find it's unreliable as you say, I can always revert back to always power on. Remote access is useful but not absolutely critical, so the occasional unavailability is not a deal breaker for me	Chikara (5139)
1428008	2016-10-30 23:53:00	Hi all, - In my router, I added a port forward - type UDP, from port 9, to IP 192.168.1.254 port 9 (wouldn't allow 255) this part was a bit confusing in the TV instructions but I think this is how it should be For port forward , the laptop/pc needs a static IP. So set the PC's static IP to (say) 192.168.1.250 , and then port forward to 192.168.1.250 In some routers you can set PC's static IP, some routers cant set static IP's so you set the static Ip via the PC itself If the Pc isnt 1.254 as per your setup, then it wont be getting that wakeup call :) Also, sorry if its obvious, but make sure the router isnt 1.254 If doing all this, would it be be just as easy to use RDC via a port forward ? (Assuming WinPro)	1101 (13337)
1428009	2016-10-31 00:16:00	Hi, from what I understand in the guide I need either a static IP, *or* need to use a dynamic DNS provider, if my ISP uses dynamic IP's (it does). regarding the port forwarding, I followed the steps in section 7.1.1 of the manual. I may have misinterpreted this instruction though, but I based my setting on the following instruction from that guide Quote from manual: "Example: If the local network is configured with 192.168.1.0 and the subnet mask 255.255.255.0, then port forwarding must be configured from UDP port 9 to 192.168.1.255:9. Sometimes routers do not allow a broadcast address ending in ".255" as the port forwarding destination. This problem can sometimes be avoided by selecting a smaller subnet mask for the local network (e.g. 255.255.255.128),thus the broadcast address ends with “.127”." As the manual said may happen, I also was not able to set port forwarding address ending with 255. I used 254 instead, I suspect this may be the problem? I'm a little confused exactly what I should set here instead and where to validate the correct ip addresses from?	Chikara (5139)
1428010	2016-10-31 00:38:00	a static internet IP is different to a static PC IP think of the internet static IP as your street adress, the PC static like a PC number, or like the PC's local network adress . PC static : the wake up call (via port forward) needs to know the internal/local ~adress~(IP) of the PC . If the router port forwards it to 1.254 & you PC isnt 1.254 the PC wont receive it . If the router is 1.254 (some are) it wont go anywhere Its getting complex, with lots of points of possible failure , you need to work through & test each one . Even the DynDNS may not be working properly , that may be harder to check Theres a reason techs prefer to not use DynDNS and just tell companies to get a internet static IP. Good luck	1101 (13337)
1428011	2016-10-31 00:51:00	To simply , the PC's IP MUST be the same as the port forward IP number . And the PC's IP must not change on the PC, run cmd , ipconfig : thats the PC's IP dont try & use 255 , it wont work. 254 isnt the best choice either(poor choice in the manual) ,some routers use that .	1101 (13337)
1428012	2016-10-31 01:15:00	Ahh OK, maybe that's why. I must admit, I'm no expert on networking and router config so some of these steps in the manual were not as clear as they could be. Thanks for the explanation. So, does that mean the PC's IP address will never change, even if it's restarted? For some reason I thought each time it disconnects and reconnects to my home network, it may get a different IP (last 3 digits)	Chikara (5139)
1 2