[zebraitis]

PS...  While attempting to toggle WOL on and off a handful of times (over 10?), Win11 locked me out of my own Admin account.

see:   https://allthings.how/how-to-unlock-a-lo...indows-11/ 

Microsoft decided to tighten that up as well.  That may be an annoyance for others as your Win11 OS install base continues to go up.

[Aphykit2006]

Hi
I have the same problem.
3 computers
Windows 11, kodi 21.1 ( and nightly too)
Test WOL error ( ip AND name)
But serveur wake up

Note :
Set-SmbClientConfiguration -RequireSecuritySignature $false .... don't do anything.
Regards

[Aphykit2006]

Hi
Find a way to keep server awake :
https://forums.tomshardware.com/threads/...k.3247607/

I made an automatic task
Here is my batch (KeepAwake.bat)

:repeat
@echo %RANDOM% > \\SERVERNAME\SharedFolder\tmp.txt
ping -n 50 127.0.0.1 > NUL
goto repeat

Regards

[zebraitis]

@Aphykit2006 - I think that you may misunderstand the need:

I have a main server running as a NAS, and I have several remote Win11 boxes that access the shared content and MySQL DB.

I very much WANT my main server (Win11) to go to sleep.  I can easily have it go to sleep, and wake it remotely using rconsole and other WOL utilities.

The problem is that KODI 21.1 will not wake it. 

Previous to v21, KODI WOL worked flawlessly.  Now, it does not.

That means that my main server is running 24/7 (turning both sleep and hibernate off), wasting a shit-ton of energy for the only purpose of working around the KODI flaw.  

Still, I have patience, and believe that the developer team will realize that Windows has changed the WOL methods and address the shortcomming.

[CrystalP]

nope the WOL methods haven't changed.
The previous troubleshooting showed that there is something different in the server name resolution to IP on your computer/in your network. I tried but wasn't able to reproduce the case.
The workaround for you is to create/edit the wol file by hand and Kodi will use it to wake the server.

[zebraitis]

I'm not one to turn down advice, especially when it comes from @CrystalP.

Based on the last message,  I can now say that my KODI devices will wake my NAS Server.    The workaround worked.


1) FIRST - I verified that everything on the NAS server (name, IP address, MAC, workgroup, etc) were what I thought that they were.

2) With my NAS server on, I went into KODI, and selected wake server

3) As before, MAC address discovery failed for server name (ZebServer) and IP Address (192.168.15.14), and when it fails MAC discovery, no WOL.xml file is created.

4) I left Wake Server button selected, and then exited KODI.

5) I found an old back-up copy of KODI and copied the WOL.xml file.  I verified that server name, IP address and MAC address were correct, and then moved it into the userdata folder.

6) I changed the power settings in my Win11 NAS to sleep after three hours.  And then I put my server to sleep.

7) I restarted the Kodi device, and KODI WOL woke the NAS server.

Great !!!  WHOO-HOO !!!  (Confetti falls from the ceiling in celebration.)  


HOWEVER.....

In a former life, I was a Consulting SE for Cisco.  So me, and networks...  pretty OK.   And now, we spend time split between Colorado and Florida.  (mountains/ beach, of course).

And this issue of not being able to discover the MAC address for the Win11 NAS server happened in BOTH networks (CO & FL).   I say that, because I really don't think it is in any way related to the network.  While both are set up in the same way ( ISP end device --> one fixed IP address --> local owned router doing DHCP -->  NAS server w/ static IP address), there is different equipment in both locations.  So, likely not the network.

AND...  as CrystalP said:  on her system, she could not recreate the issue.  

So, that leaves two things:  
1) Win11 doing something weird & different, or...
2) The NIC choosing not to share the MAC address with others.

A good test would be to put a different network card into the NAS server and see if that different card and different driver would fix the issue completely...  but at this point...  it's a bit of "who cares", as it is working as I hoped.  

CrystalP, I do want to thank you for making the suggestion which will allow me to save power and not run the server needlessly.  

I really appreciate the time that you shared.  

[zebraitis]

... crap.

Spoke too soon.

I'm still having problems.  Looks like trying to manually set up the WOL.xml file cause the KODI client to hang while it was attempting to find what it could not fined during the setup of the WOL file.

I'm just going to try a full reinstall and see what happens.

[zebraitis]

OK...  Tried a different NIC in my Win11 NAS... same error.

Did a fresh reload of KODI to a Kodi portable config...  same error.

Two completely separate networks... same error

I guess at this point I will just throw in the towel, give up on KODI WOL, and keep my server running.

[CrystalP]

Need a debug log to get an idea of where things break now. But with a problem in name resolution it wouldn't be too surprising for other parts of the program that need the lookup to fail.

With your network experience it shouldn't be a problem to describe how name resolution is supposed to work in your networks? and what non-default settings (if any) are used on the windows computers.

[CrystalP]

The v22 test version below has more logging code. Please provide a debug log of an attempt to turn on WOL to generate a new file. This is still is expected to fail, although since the name resolution is done slightly differently, who knows.
https://mirrors.kodi.tv/test-builds/wind...e--x64.exe

[zebraitis]

Thanks, but I'm going to put this on hold for a week or two...  

I'm going to buy a different motherboard, and see if that has an impact.

(...the current one had flakey RAM issues, so it's something that I should have done a while ago.)