search

basildane / WakeOnLAN

Wake On LAN, WakeOnLAN, shutdown software for Windows. A powerful WOL, ping, shutdown, GUI application.
http://wol.aquilatech.com
Other
991 stars 146 forks source link

Status unknown but wakeup is working #208

Open adgm1 opened 11 months ago

adgm1 commented 11 months ago

hello. All my computers are notified as unknown status even if they are on or off. The wol and RDP are working fine but the shutdown is not working. How can I have the normal status of my computers ?

aquila wol

jan-oratowski commented 10 months ago

That's because there is no IP Address filled in.

That means the app doesn't know which address should it ping to check if the host is up or not.

vvhitesmoke commented 8 months ago

Hi, I've the same issue as reported by adgm1. I've properly configured (filled in) the IP addresses of my hosts. I tried to spy the ping activity using wireshark: I can't see any ICMP requests sent by application, but can see the ICMP requests sent "manually" using ping command (both using target IP and using target host name). Suprisingly, it worked properly some time ago... I checked Windows firewall settings, disabled it - nothing helps... I'm using Win10 Pro. How can I diagnose and solve this?

basildane commented 8 months ago

Please click the Pinger button to turn on that function. Shutdown is a different problem. Are the machines on a domain or a workgroup?

vvhitesmoke commented 8 months ago

Hi, Thanks for reaction. The Pinger button is clicked of course :) And finally I found the reason: pinger doesn't work for me if I use DNS name of the host. Changing this to IP address results in proper work. I've local DNS domain, configured on bind/named instance working on one of my hosts. What is interesting: while WakeOnLan is not able to ping a host using DNS host name, I'm able to ping the same host from the PC running WakeOnLan, from Windows command line using 'ping' command. And there are no visible delays related to potentially slow DNS resolution or something similar - DNS works fast enough. The rev-DNS is properly configured too. I'm not using any Windows domain - all Windows machines are in the same workgroup. But the issue causes the linux hosts too - and these hosts are not in any Windows domain/workgroup. If it is important, my DNS domain is 'villagetech.local' - so the suffix is slightly non-typical, but should work for WakeOnLan as it works for all other purposes (RDP connections, ssh, ftp etc).

basildane commented 8 months ago

For ping DNS resolution, enter the machine.villagetech.local into the FQDN field on Wake Up, and leave the IP blank on Status tab. Did you try that?

vvhitesmoke commented 8 months ago

Yes, I did - doesn't help :(