WOL not working consistently

[Endulini]

Hi,

I've been trying to set up WOL on a Windows 8 system and am confident that
it's configured ok as I can confirm that the Magic Packets are getting
through and are recognised both through the internal LAN and over the
Internet (using a combination of Magic Packet software and TeamViewer). The
problem comes when I shut the system down or set it to sleep or hibernate.
Whilst I can wake it remotely for the first 20 minutes or so after this it
doesn't respond at all. I've disabled hybrid shut-down and have read that
WOL isn't supposedly supported in shut-down or sleep but even putting it in
hibernate doesn't help. It's set up with dynamic DNS so I'm also confident
that it's not due to the IP changing.

Anyone have any suggestions or comments?

Thanks.

[Rob Morley]

On Tue, 24 Sep 2013 23:22:42 +0100

Post by Endulini
Hi,
I've been trying to set up WOL on a Windows 8 system and am confident
that it's configured ok as I can confirm that the Magic Packets are
getting through and are recognised both through the internal LAN and
over the Internet (using a combination of Magic Packet software and
TeamViewer). The problem comes when I shut the system down or set it
to sleep or hibernate. Whilst I can wake it remotely for the first 20
minutes or so after this it doesn't respond at all.

Is the PSU maintaining standby power for the network port?

Post by Endulini
I've disabled
hybrid shut-down and have read that WOL isn't supposedly supported in
shut-down or sleep but even putting it in hibernate doesn't help.
It's set up with dynamic DNS so I'm also confident that it's not due
to the IP changing.

Have you checked the correct options in the network card's Power
Management settings?

[Endulini]

"Rob Morley" wrote in message news:***@hyperion...

On Tue, 24 Sep 2013 23:22:42 +0100

Post by Endulini
Hi,
I've been trying to set up WOL on a Windows 8 system and am confident
that it's configured ok as I can confirm that the Magic Packets are
getting through and are recognised both through the internal LAN and
over the Internet (using a combination of Magic Packet software and
TeamViewer). The problem comes when I shut the system down or set it
to sleep or hibernate. Whilst I can wake it remotely for the first 20
minutes or so after this it doesn't respond at all.
Is the PSU maintaining standby power for the network port?

The green light is on when the computer is off so presumably yes it is
.

Post by Endulini
I've disabled
hybrid shut-down and have read that WOL isn't supposedly supported in
shut-down or sleep but even putting it in hibernate doesn't help.
It's set up with dynamic DNS so I'm also confident that it's not due
to the IP changing.
Have you checked the correct options in the network card's Power

Management settings?

"Allow this device to wake the computer" is selected
"Allow the computer to turn off this device to save power" is selected (is
that right?)
"Only allow a magic packet to wake the computer" is selected.

Can't see a problem here - is there anything in Power Management might
inhibit it?

[Dave Saville]

Post by Endulini
"Allow the computer to turn off this device to save power" is selected (is
that right?)

Wouldn't think so. If it's been turned off to save power how is it
going to wake up except by re-application of power? It ain't goning to
see any signal on the wire.

[Rob Morley]

On Wed, 25 Sep 2013 17:42:12 +0100

Post by Rob Morley
On Tue, 24 Sep 2013 23:22:42 +0100

Post by Endulini
I've been trying to set up WOL on a Windows 8 system and am
confident that it's configured ok as I can confirm that the Magic
Packets are getting through and are recognised both through the
internal LAN and over the Internet (using a combination of Magic
Packet software and TeamViewer). The problem comes when I shut the
system down or set it to sleep or hibernate. Whilst I can wake it
remotely for the first 20 minutes or so after this it doesn't
respond at all.
Is the PSU maintaining standby power for the network port?

The green light is on when the computer is off so presumably yes it is
.

If it's on even when the machine doesn't respond then that doesn't seem
to be the problem.

Post by Rob Morley

Post by Endulini
Have you checked the correct options in the network card's Power

Management settings?
"Allow this device to wake the computer" is selected
"Allow the computer to turn off this device to save power" is
selected (is that right?)

I'd be inclined to switch that one off, but I'm only guessing and I
don't have a Windows 8 machine to play with.

[Adrian C]

Post by Endulini
Hi,
I've been trying to set up WOL on a Windows 8 system and am confident
that it's configured ok as I can confirm that the Magic Packets are
getting through and are recognised both through the internal LAN and
over the Internet (using a combination of Magic Packet software and
TeamViewer). The problem comes when I shut the system down or set it to
sleep or hibernate. Whilst I can wake it remotely for the first 20
minutes or so after this it doesn't respond at all. I've disabled hybrid
shut-down and have read that WOL isn't supposedly supported in shut-down
or sleep but even putting it in hibernate doesn't help. It's set up with
dynamic DNS so I'm also confident that it's not due to the IP changing.
Anyone have any suggestions or comments?
Thanks.

In the router's configuration, as well as the port forwarding you may
have done, You might need to _statically_ assign the MAC address of the
PC's network card to the IP address used for it. This normally has to be
done in CLI, overturning the dynamic assign which is forgotton a time
after the PC powers off.

Which router?

[Adrian C]

Post by Adrian C

Post by Endulini
Hi,
I've been trying to set up WOL on a Windows 8 system and am confident
that it's configured ok as I can confirm that the Magic Packets are
getting through and are recognised both through the internal LAN and
over the Internet (using a combination of Magic Packet software and
TeamViewer). The problem comes when I shut the system down or set it to
sleep or hibernate. Whilst I can wake it remotely for the first 20
minutes or so after this it doesn't respond at all. I've disabled hybrid
shut-down and have read that WOL isn't supposedly supported in shut-down
or sleep but even putting it in hibernate doesn't help. It's set up with
dynamic DNS so I'm also confident that it's not due to the IP changing.
Anyone have any suggestions or comments?
Thanks.

In the router's configuration, as well as the port forwarding you may
have done, You might need to _statically_ assign the MAC address of the
PC's network card to the IP address used for it. This normally has to be
done in CLI, overturning the dynamic assign which is forgotton a time
after the PC powers off.
Which router?

Ah, see here.

http://talktalkmembers.com/t5/Unlimited-Broadband/HG533-Wake-on-LAN-problems/td-p/852729

[Endulini]

Post by Endulini
Hi,
I've been trying to set up WOL on a Windows 8 system and am confident
that it's configured ok as I can confirm that the Magic Packets are
getting through and are recognised both through the internal LAN and
over the Internet (using a combination of Magic Packet software and
TeamViewer). The problem comes when I shut the system down or set it to
sleep or hibernate. Whilst I can wake it remotely for the first 20
minutes or so after this it doesn't respond at all. I've disabled hybrid
shut-down and have read that WOL isn't supposedly supported in shut-down
or sleep but even putting it in hibernate doesn't help. It's set up with
dynamic DNS so I'm also confident that it's not due to the IP changing.
Anyone have any suggestions or comments?
Thanks.

In the router's configuration, as well as the port forwarding you may have
done, You might need to _statically_ assign the MAC address of the PC's
network card to the IP address used for it. This normally has to be done
in CLI, overturning the dynamic assign which is forgotton a time after the
PC powers off.
Which router?
--
Adrian C

It's a Thomson TG587n v2 i.e. an O2 router (I know I've also posted a
question about a TalkTalk router but that's a different story.....)

[Adrian C]

Post by Endulini

Post by Adrian C
In the router's configuration, as well as the port forwarding you may
have done, You might need to _statically_ assign the MAC address of
the PC's network card to the IP address used for it. This normally has
to be done in CLI, overturning the dynamic assign which is forgotton a
time after the PC powers off.
Which router?
--
Adrian C

It's a Thomson TG587n v2 i.e. an O2 router (I know I've also posted a
question about a TalkTalk router but that's a different story.....)

Here ya go.

http://npr.me.uk/wol.html

[Endulini]

Post by Adrian C

Post by Endulini

Post by Adrian C
In the router's configuration, as well as the port forwarding you may
have done, You might need to _statically_ assign the MAC address of
the PC's network card to the IP address used for it. This normally has
to be done in CLI, overturning the dynamic assign which is forgotton a
time after the PC powers off.
Which router?
--
Adrian C

It's a Thomson TG587n v2 i.e. an O2 router (I know I've also posted a
question about a TalkTalk router but that's a different story.....)

Here ya go.
http://npr.me.uk/wol.html
--
Adrian C

Cheers Adrian. I've seen this and used it to successfully set my router to
forward on the packets and I can see that the packets are getting through
even from the internet. What is happening though is that after the computer
has been 'asleep', powered down or 'hibernating' for longer than around 20
minutes it doesn't reboot when the magic packet is sent. It's like it's only
dozing initially and then something further powers off after 20 minutes and
stops it from rebooting.....

[Adrian C]

Post by Endulini
Cheers Adrian. I've seen this and used it to successfully set my router
to forward on the packets and I can see that the packets are getting
through even from the internet. What is happening though is that after
the computer has been 'asleep', powered down or 'hibernating' for longer
than around 20 minutes it doesn't reboot when the magic packet is sent.
It's like it's only dozing initially and then something further powers
off after 20 minutes and stops it from rebooting.....

So you've done the arpadd stuff?

e.g. arpadd intf=LocalNetwork ip=192.168.1.66 hwaddr=00:00:48:8f:03:9a

Hmmm... me confused.

Look at network card properties, advanced tab - there may be other
settings there. Wake from power off, hybernate, sleep are all a
minefield of known compatibility snags existing between BIOS, APM/APCI
and OS. On some plaforms (e.g. HP Microserver) only wake from power off
is properly supported.

I've even come across slightly different implementions of the magic
packet and differing port numbers. In windows powercfg.exe reveals a lot
on current settings, and so does wireshark if you do some sniffing.

[j***@gmail.com]

did you ever figure out what was stopping the PC's from responding to WOL after 20 minutes? I basically have the same issue and don't know where to start..

Thanks
James

[Adrian Caspersz]

Post by j***@gmail.com
did you ever figure out what was stopping the PC's from responding to WOL after 20 minutes? I basically have the same issue and don't know where to start..

Read the rest of the original thread you've dug up.

or watch this

SOLVED: Why Wake on WAN (Wake on Internet) stops working after 15 minutes