i am waking up the remote PC via 'Wake On Lan ' successfully but for some reason i cant do it with command line . i tried using the 'listener' window for debugging , but whenever the 'listener' window is opened the the remote PC wakes up and when i close the window , the script in command prompt doesn't work . i tried using netstat -ano | find ":9" to see if a process reserved the port and i could not find any process using that port . can anyone help ?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
i need to understand better.
Can you turn on the remote machine and run the listener on it. Make sure the WOL packets are getting to the remote machine. That is step one.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
OK , for making sure everything is alright , i send the package using GUI and i receive it at the remote PC ( i see it in the listener window) . then i try sending the package with Command line with both machine name and mac address options and nothing received at the remote PC .
if it is any help , i tried sending the magic package with a UDP Utility and as you would expect , the remote PC wakes up . and i already checked the "simple TCPIP services" and it was not checked .
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
OK. Please go to your firewall advanced settings, check the rules for WakeOnLan and WakeOnLan Command Line, make sure the command line is able to send packets out.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
there was no rule for WakeOnLan Command Line , so for making sure nothing is wrong with the rules i added inbound and outbound rules for it with no restrictions . but nothing changed .
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
i am waking up the remote PC via 'Wake On Lan ' successfully but for some reason i cant do it with command line . i tried using the 'listener' window for debugging , but whenever the 'listener' window is opened the the remote PC wakes up and when i close the window , the script in command prompt doesn't work . i tried using
netstat -ano | find ":9"to see if a process reserved the port and i could not find any process using that port . can anyone help ?Hi, what version are you using? What is the command you are trying?
Hi, i am using version : 2.11.20 and the command is :
WakeOnLanC.exe -w -m nas, nas is the name of the machine that i created with the GUIDoes that return a message? An error?
Please try using the MAC address instead of -m nas. If that works, then we have a problem with the command line finding your database.
No error , and i test the MAC Address option too , same thing.
the returning message is this :
but nothing happens, but when 'listener' windows is open , the same message (on cmd)appears and the remote pc wake up
i need to understand better.
Can you turn on the remote machine and run the listener on it. Make sure the WOL packets are getting to the remote machine. That is step one.
Just a side note, you asked about other things using port 9. Please check if you have "simple TCPIP services" running. https://wol.aquilatech.com/help/troubleshooting/listener.html
OK , for making sure everything is alright , i send the package using GUI and i receive it at the remote PC ( i see it in the listener window) . then i try sending the package with Command line with both machine name and mac address options and nothing received at the remote PC .
if it is any help , i tried sending the magic package with a UDP Utility and as you would expect , the remote PC wakes up . and i already checked the "simple TCPIP services" and it was not checked .
OK. Please go to your firewall advanced settings, check the rules for WakeOnLan and WakeOnLan Command Line, make sure the command line is able to send packets out.
there was no rule for WakeOnLan Command Line , so for making sure nothing is wrong with the rules i added inbound and outbound rules for it with no restrictions . but nothing changed .
I'm sorry I'm still thinking. The command line program and GUI both call the same exact DLL function. So it should work...