Windows 10: Can't get WOL to work

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 *Sad

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.

 

Well guys & gals, I got there! I was sure that MS had screwed things up again and I was right. The NIC drivers included in Windows updates were to blame. By downloading the Realtek drivers and installing in Windows 8 compatibility mode - voila! Problem solved!
*chuckle
Ken

 

Alas, Ken, with niggling network details -- and I'd put WOL stuff square inside that category -- the drivers are almost always where things get sorted out. Glad you got the right stuff at long last. You showed dogged perseverance along the way, too. Congrats!
--Ed--

 

It's interesting to discover just how important WOL is to so many people. When one has done as much research into the subject as I have over the last week or so, one discovers that there are hundreds of users who consider it vital to their systems.

It's a pity Microsoft haven't recognised its significance and made sure that updates do not disable the WOL capability. It must have precipitated huge financial loss for many whose entire working methodology relies on that system. I've spent over a week on-and-off but, then, I'm retired. I feel sorry for those who have had to waste precious business time in trying to resolve matters.

Thanks for all your support over the last couple of weeks Ed and thanks to everybody who contributed.

Ken