Wake On LAN works within LAN, but not from over the Internet. Why?

[nLinked]

Wake On LAN works within LAN, but not from over the Internet. Why (more details...)?I am trying to get a computer behind a router to wake up using a Wake On LAN magic packet. I have entered the correct DDNS address of the host, and the correct MAC address of the PC behind the remote router. I have forwarded port 9 on the remote router so it can go through their NAT.

Do I have to forward port 9 to the router's local IP address or to the PC's LAN IP address?

The PC will wake up if I send a magic packet from a computer on the same LAN, but not from over the net. There are no firewalls and I have temporarily disabled the router's firewall.

How do I get it to turn on from over the Internet? I have tried different software, and the BIOS settings on the remote PC have been checked.

 

[JackMDS]

May be this can Help, http://www.ezlan.net/WOL.html

 

[her209]

The short of is WOL functionality works by doing a broadcast. If the computer your are trying to wake up is on the other side of a router, the router effectively blocks the computer (as it should) on the other side from seeing the broadcast.

 

[LightninTrip]

 

[nLinked]

Originally posted by: her209
The short of is WOL functionality works by doing a broadcast. If the computer your are trying to wake up is on the other side of a router, the router effectively blocks the computer (as it should) on the other side from seeing the broadcast.

I can understand that. But I have setup port forwarding to allow this WoL packet to be sent through a specific port. The router will recieve the packet from my request and see that it is trying to go through port x to xxx.xxx.xxx.xxx IP address on the LAN. Obviously that computer is turned off so the router can't find it. Is this where the packet it simply dropped?

Can't the router just broadcast my packet onto the media anyway and since the NIC is turned on just let the NIC accept the packet? Because how does it do this while I turn on the PC from a PC on the same LAN?

 

[JackMDS]

Use th utility that is linked in the page that in my first post.

Since the computer is Off No IP can be involved it has to work with MAC number.

 

[cdcooker]

I got the exact problem as you did. Have you solved the problem yet? I am still trying to figure out why. I followed all the required procedures from the smallnetbuilder, ezlan and depicus sites, with no success. Here is what I have done:

1. Acquire a ddns from dyndns.org.
2. Setup the ddns on my router.
3. Setup static DHCP for my computer that will take WOL with it's MAC address on the router setup page.
4. Open port 9 for the incoming packet to my WOL computer's IP.
5. Download all the softwares listed on wikipedia's WOL page. I used the one that let me specify the port # explicitly.

Things work within the LAN. But not over the web.

Originally posted by: nLinked
Wake On LAN works within LAN, but not from over the Internet. Why (more details...)?I am trying to get a computer behind a router to wake up using a Wake On LAN magic packet. I have entered the correct DDNS address of the host, and the correct MAC address of the PC behind the remote router. I have forwarded port 9 on the remote router so it can go through their NAT.

Do I have to forward port 9 to the router's local IP address or to the PC's LAN IP address?

The PC will wake up if I send a magic packet from a computer on the same LAN, but not from over the net. There are no firewalls and I have temporarily disabled the router's firewall.

How do I get it to turn on from over the Internet? I have tried different software, and the BIOS settings on the remote PC have been checked.

 

[JackMDS]

1. I am not sure that the WOL Utility work with URL.

So, try it while using you actual External IP number.

2. In case you are trying it from within your network, some Router block going out and returning in from the same address.

So, try from a real remote location.

 

[GregGreen]

You might try connecting to your router's web interface and seeing if there is a WOL page on there. I know tomato-wrt lets you run the WOL commands from the router's web and even includes a list of recent MAC addresses to connect to it.

 

[cdcooker]

Originally posted by: JackMDS
1. I am not sure that the WOL Utility work with URL.

So, try it while using you actual External IP number.

2. In case you are trying it from within your network, some Router block going out and returning in from the same address.

So, try from a real remote location.

Hi, I have tried real external IP and DDNS, neither work in my case. I also tried it from a real remote location, not inside my house from another computer and doing it on the web.

I have downloaded the network utility software mentioned in SmallNetBuilder's site. Strangely when I tried to test the destination port from the same magic packet software, it varies from time to time. When the destination port match the port I setup in my router, it will work, as I have tested it with my friend from a remote site. However, that only happened when I turn off the computer immediately before asking my friend to try. And I must emphasize that it doesn't work all the time, probably only 20%.

Thanks

 

[JackMDS]

The port is essential otherwise the Packet does not know were to Go. Use Higher port Not 9.

Make sure that the Router's DHCP does not change its IP to the computer each time when the system starts.

The computer should be off but has to be left plugged to a live outlet and the On-Off switch on the PSU (if there is one) has to be on.

 

[cdcooker]

Originally posted by: JackMDS
The port is essential otherwise the Packet does not know were to Go. Use Higher port Not 9.

Make sure that the Router's DHCP does not change its IP to the computer each time when the system starts.

The computer should be off but has to be left plugged to a live outlet and the On-Off switch on the PSU (if there is one) has to be on.

I have tried something in the 5000s range also for the magic packet port.

I use static DHCP for that particular computer, which the router tied the MAC address with a static internal IP.

When the computer is off, it remains plugged to a live outlet, and the network jack has the light on, which means it is accepting signal for remote wake up. PSU is on also.

Thanks

 

[networkman]

This may or may not be of help to you, but I recently just got WOL working myself in my WAN environment - 19 locations. In my case, the solution(Cisco equipment) was to make sure the ip directed-broadcast command was in each of the physical interfaces so that the magic packets could be forwarded to the right location. In most cases that meant having said line in both the local FastEthernet0 or GigabitEthernet0 interfaces as well as the Serial0 (T1) connection back to the main homw office where I would be sending the magic packets from.

YMMV

 

[spidey07]

ouch, directed-broadcasts are a big security risk.

 

[networkman]

Quite true, which is why the next step was to go through and establish a vlan to restrict who could send them and from which direction.

Edit: FWIW, this is me being asked to figure it out without being certified and not having a Tier2 to fall back on. I'm quite proud of myself actually.