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
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 .................
Hi Ed
I know it's Saturday but had a quick look at your link. However, it all relates to an organised
network with a server and clients. Mine is just a simple peer-to-peer network
Ken
There's plenty of other interesting discussion on this topic, including this SuperUser thread, which indicates some of this can be handled at the router: networking - Change WOL port - Super User. I have to believe that searching on "change UDP port address for WOL Windows 10" will help to turn up the answer you need. I just haven't been able to find it yet!
HTH,
--Ed--
PS: Winaero has an interesting article on this that indicates turning on Simple TCPIP Services in Programs and Features/Turn Windows features on or off also helps, where he shows how to change the port number for the Windows Firewall. In particular he shows how to use a freeware app named WolCmd to wake up PCs on the LAN. Might also be helpful... Given enough will, research, and fooling around I'm sure we can figure this out.
Last edited by EdTittel; 24 Feb 2018 at 10:46. Reason: Add PS
Quote
