Jon00 Remote Computer Control & Network Monitor (HS2, HS3 & HS4)

[BootsC5]

The WOL generator GUI works fine. Here are the captures, first from the HS machine running the GUI link you posted, the second is from my linux box using "wakeonlan". The packets are the same.

Packet recieved from 192.168.1.9 on port 34885
at 11:11:04 packet length : 102
00000000 : FF FF FF FF FF FF 00 23 54 B5 0A 61 00 23 54 B5
00000010 : 0A 61 00 23 54 B5 0A 61 00 23 54 B5 0A 61 00 23
00000020 : 54 B5 0A 61 00 23 54 B5 0A 61 00 23 54 B5 0A 61
00000030 : 00 23 54 B5 0A 61 00 23 54 B5 0A 61 00 23 54 B5
00000040 : 0A 61 00 23 54 B5 0A 61 00 23 54 B5 0A 61 00 23
00000050 : 54 B5 0A 61 00 23 54 B5 0A 61 00 23 54 B5 0A 61
00000060 : 00 23 54 B5 0A 61
Packet recieved from 192.168.1.2 on port 47645
at 11:11:34 packet length : 102
00000000 : FF FF FF FF FF FF 00 23 54 B5 0A 61 00 23 54 B5
00000010 : 0A 61 00 23 54 B5 0A 61 00 23 54 B5 0A 61 00 23
00000020 : 54 B5 0A 61 00 23 54 B5 0A 61 00 23 54 B5 0A 61
00000030 : 00 23 54 B5 0A 61 00 23 54 B5 0A 61 00 23 54 B5
00000040 : 0A 61 00 23 54 B5 0A 61 00 23 54 B5 0A 61 00 23
00000050 : 54 B5 0A 61 00 23 54 B5 0A 61 00 23 54 B5 0A 61
00000060 : 00 23 54 B5 0A 61


The script seems to refuse to send the WOL unless the target machine is actually up and pingable.

[BootsC5]

I am viewing all packets from a seperate machine on the same subnet.

Machine 1: HS
Machine 2: Touch Screen (the one I want to WOL)
Machine 3: Linux box
Machine 4: My main/gaming rig (monitoring network traffic)

[BootsC5]

If not then your router is probably preventing access some how (clearing the ARP table maybe?)

If that was the case the linux box would also not be able to WOL the target machine. In fact the wakeonlan command only take the MAC address and has no knowledge, from the commandline at least, about the targets ip addr.

Do you bind the IP to the MAC address BTW?

I think you are asking if my DHCP server statically assigns ip addr X to mac addr Y? Yes it does.

[Guest]

Brian,

Would you try the same as I suggested to BootsC5 please. Also where are you viewing the packets?

Yes tried the app and it is sending the packets and waking the machine.
The Wake on Lan Monitor and Magic Packet are running on a virtual machine.

The problem that i am seeing only seems to happen when a standby command is sent.

[BootsC5]

The problem that i am seeing only seems to happen when a standby command is sent.

I'm also using standby.


[VDButton11]
Buttontext=Standby
Command=standby

[Guest]

I'm also using standby.

[VDButton11]
Buttontext=Standby
Command=standby

Yes that is what mine is set as.

If a standby command is sent and the machine goes into standby i cannot control any other computer until the machine that went into standby wakes up.

[jon00]

So as a recap, if you shutdown the PC, WOL works but if you set it to standby, it does not?

Have you tried hibernate as well?

[BootsC5]

Correct. WOLs were successfully sent after a hibernate and shutdown, but not after a standby.

[Guest]

Correct. WOLs were successfully sent after a hibernate and shutdown, but not after a standby.

Same Here

[jon00]

How bizarre! OK, I'll have to do some testing.

[jon00]

Ok, I can reproduce this but don't have a resolution for it. Time for some Googling!

[antoon]

After a lot of testing I get one Windows 7 machine running and WOL is also working now.
I will take a look at the rest of the systems when I have more time.

The client still keep crashing,but at the moment only on the wireless systems.

[jon00]

Correct. WOLs were successfully sent after a hibernate and shutdown, but not after a standby.

Same Here

OK, working on the next version!

[Guest]

Unfortunately still got the problem.

[jon00]

Hmm... odd, it is now waking my Win 7 machine from standby.

This is a bit of a cop out but I've now added support for an external freeware wol command line application. If it sees this in your Homeseer root directory, it will use that rather than the code in the script. Look at the Q & A section in the docs for the URL.

Version 1.03 is now available with this modification.

The only other change is more robust checking within the client which hopefully will stop it crashing with TCP socket problems.