Author Topic: Wake On Lan problem  (Read 9847 times)

  • Offline Eagle

  • Posts: 1,902
  • Hero Member
Re: Wake On Lan problem
Reply #15 on: July 31, 2011, 17:32:05 PM
...also, do you know if it'll be possible to create a 'catch-all' wake so that it'll wake whether the phone is connected to WAN or LAN?

Re: Wake On Lan problem
Reply #16 on: August 01, 2011, 18:32:58 PM
Been a fiddling with mocha but just cant seem to get it to work (on WAN (Internet)).  I'll arrange a static IP, see if that helps.

I'm unable to put 255 on the end, so can we get complicated? ;)

Shamelessly copied from the above link.. but basically you need to adjust your subnet, and this will be assuming that all of your devices use DHCP to get their IP address, and that any other port forwarding rules you currently have in place may be impacted and need changing..

If you need more details about subnets, there's a guide in the guides section ;)

Your current subnet will most likely be 255.255.255.0

So setup your port forwarding and set the target IP to XXX.XXX.X.127 (first blocks of Xs are automatic in Belkin's case I think)

Save the settings

Then go in to your DHCP options and change your subnet to assign from 255.255.255.0 to 255.255.255.128 this will limit your LAN IP range to a max of 126 devices (127 is used for broadcast)

Save your settings, and hopefully it wont work out you have put the port forward on a broadcast address..

Reboot your router and PC you want to power on, any other devices are likely to need a power cycle as well to pick up the new dhcp settings, or just pull and re-connect the network cable..

Let me know how you get on..

Stolen text:

"If the router does not allow NAT to be forwarded on a broadcast address (it is a bug in some routers), a work around is to define the subnet for your LAN as 255.255.255.128 , and forward the UDP port 9 to IP 192.168.2.127, which is the broadcast address for your new subnet (if your network is using range 192.168.2.xxx).
On some routers, first define subnet as 255.255.255.0, and NAT UDP port 9 to 192.168.2.127 (if your network is using range 192.168.2.xxx), save the configuration, and hereafter change the subnet to 255.255.255.128."

Re: Wake On Lan problem
Reply #17 on: August 01, 2011, 18:34:41 PM
...also, do you know if it'll be possible to create a 'catch-all' wake so that it'll wake whether the phone is connected to WAN or LAN?

No I don't think so, not without having a router that you could configure the external range, I think we are talking CISCO or DD-WRT territory here :)

  • Offline Eagle

  • Posts: 1,902
  • Hero Member
Re: Wake On Lan problem
Reply #18 on: August 01, 2011, 20:31:42 PM
Yeesh!  I think I'm going to have to set aside a quiet day to get my head around all of this.  It kinda makes sense...

Cheers. :)

  • Offline Eagle

  • Posts: 1,902
  • Hero Member
Re: Wake On Lan problem
Reply #19 on: August 01, 2011, 20:41:20 PM
Quote
and this will be assuming that all of your devices use DHCP to get their IP address
How can I tell?

Re: Wake On Lan problem
Reply #20 on: August 01, 2011, 21:51:19 PM
If you have to ask the question then I expect they will all be DHCP, as you would have had to have configured otherwise..

It should only be 5 mins work, change the port forwarding, then change the DHCP setting, reboot..

  • Offline Eagle

  • Posts: 1,902
  • Hero Member
Re: Wake On Lan problem
Reply #21 on: August 01, 2011, 22:30:54 PM
Ok, cheers - will it affect the ability to wake on LAN?

I'm assuming I should record/export settings incase it all goes horribly wrong?  :panic:

Re: Wake On Lan problem
Reply #22 on: August 01, 2011, 22:45:36 PM
No shouldn't make any difference... Might be a good idea to export settings... If you are on DSL make sure you have your login for the internet.. worst comes to the worst you can always do a hard reset, although you shouldn't have any problems making the above changes..

Oh and also if you can set your DHCP range make sure it is anywhere between 2 and 254.

Re: Wake On Lan problem
Reply #23 on: February 18, 2014, 12:36:46 PM
Not sure if anyone with the original problem is still around ... and if you solved it or not ... but I am having the same exact issue.

I have an ActionTec router from Verizon and I know my external IP address.
I have configured my MWOL iPhone app to wake my computer from both inside my network and from outside (on 3G).
Both methods work just fine, 99% of the time.

What I am finding is that if I shut my PC down completely (say I go out of town for a few days), then the MWOL via outside connection (3G) will not wake my computer. But, if I switch over my iPhone onto my home network and use the configuration in MWOL, it wakes the PC up, just fine.

I have a reserved IP address set for this PC -and- I have an outside port (1966) forwarding to that specific PC's port #9.

If I power down the PC completely right now, take my iPhone off my home network, get on 3G and use the outside-in MWOL configuration, my PC wakes up just fine.  But, if I shut my PC down and let it stay off overnight (just tried this last night), it does NOT wake my PC.  I then switched back to having my iPhone on my home network and used the inside-my-network configuration in MWOL and it woke my PC.

So, it has nothing to do with the Windows configuration of turning power off to the NIC to save power, because - shut down - Windows is not up and running to control the power save on the NIC.

Very, very odd!

Re: Wake On Lan problem
Reply #24 on: February 18, 2014, 23:52:38 PM
I'm assuming you are on ADSL? If there is no activity on the network then it'll disconnect the connection meaning that you are unable to make a connection externally

You could either check the logs to see when the connection is down, you might need to enable logs. Or alternatively next time try WOL while on the mobile network, if it doesn't work then go on to wifi and browse to a web page to force the modem to connect then go back on to mobile network and try WOL again. Let us know how you get on?
Last Edit: February 19, 2014, 09:05:54 AM by XEntity #187;

Re: Wake On Lan problem
Reply #25 on: February 19, 2014, 17:27:26 PM
I still reckon it could be power management related.  Are you sure you're fully shut down and not in hybrid sleep?  I was under the impression that WOL wouldn't work on a shut down computer, only a sleeping one.

Re: Wake On Lan problem
Reply #26 on: February 19, 2014, 20:13:18 PM
WOL should work fine on a shutdown computer, although I've seen problems on computers that have been disconnected from the mains, but anyway he's saying its fine on the local network just not over the tinter webs

0 Members and 1 Guest are viewing this topic.