Windows 10: Can't get WOL to work

Yeah! Turning out to be a rare mystery. I really appreciate the time and effort you're putting in to try and help. Have to see a client first thing this morning so will not be in the office until mid-day.
Ken

 

Are you using magic packets? if no uncheck "Only allow magic..."

 

I use a WOL App to start the PC from my iPhone or iPad normally. I assume the app sends magic packets?
The App is Mocha WOL 2.1.

 

Yes it should be "magic",
have you insert MAC address of the sleeping PC?

 

Yes, it’s all set up correctly with MAC address and a reserved IP address in the router. As I said earlier, the whole thing was working fine until I had to re-install Windows 10 a week or so ago.

 

Sorry Ed, I don’t appear to have a BIOS setting Erp Support. Went carefully through every line of the BIOS settings, even the headings which obviously weren’t relevant just in case. :-(

Ken

 

Old saying "If it seems to good to be true, it probably isn't." It was too easy. I'm starting to think it's some odd bug in the IP stack in the latest build. FWIW, WOL works fine on the three systems I've tried it on. I'm fresh out of ideas now, so we must hope you stumble upon something.
--Ed--

 

Well, thanks for all the helpful suggestions. I blame MS because it was working fine until an automatic Windows update caused a crash resulting in a re-installation of the O/S. None of the repair or recovery options would work by the way!

If I ever find a solution I'll post it up of course.

Ken

 

Ed - Are the machines you tested running build 1709?

Ken

 

Yes: all I have up and running right now is either production 1709, or Insider Preview versions that are newer than that (Windows 10 Pro Build 17101.1000, currently). Does that help, or hurt, here?
--Ed--

 

I was running Insider Previews for quite a while but stopped because the program became too intrusive on my everyday activities.

Thanks for the info.

Ken

 

Yr wlcm! And again: nice snapshot. Best wishes,
--Ed--

 

I've done some further work on this by installing wolsniffer on the target machine then trying WOL from the remote.

It appears that the magic packets are being sent to port 52967!? At least, that's what the sniffer sees. Since WOL worked before the re-installation of W10 it must have been sent correctly to port 9 previously. I'm using the Solar Winds WOL as before and no changes were made to the router.

Any thoughts anybody?

 

You can always just use this social.technet info to change your port assignment to match what's in use! Change WOL Port number for clients

This just keeps getting more interesting, but not necessarily in an entertaining way...
--Ed--

 

Interesting line of enquiry; thanks Ed. Started my weekend now so, until Monday .................*Wink