The computer I wanted to wake up was in another network segment. When the computer had been turned on in the last hours and i had a connection to him, my computer got his ip and mac in his arp-table.
After 4 hours, the arp tables are cleared. This is the reason why i couldnt wake up the computer over night.
The solution was to use netcast WOL, not direct WOL. So you have to use the broadcast-address of the network where the other computer resides in. And be careful to use the right netmask when calculating the broadcast-address.
I use WOL two ways. One is via Landesk and broadcast to a "machine Domain Rep" on the same subnet. The Landesk sever is in a different location, but I remote into it.
The box I am testing is in the same room as me. So, when I do a Landesk WOL, it is originating from a MDR on the same subnet, and the same switch as me.And when I do WOL locally thru a magic packet program (nirsoft wakemeonlan) It is also originating from a box on the same subnet . . . .and behind the same switch again. My computer is both the MDR for Landesk AND the computer trying the nirsoft wake up.
And WOL fails BOTH ways after the machine is off overnight. What you are saying about ARP table sounds right, but I.m just not sure that comes into play here in either of the scenarios. But I'm looking.
I have an e-mail into Dell about it now. we shall see. Thanks for the response.
Mr Toves
2 Posts
0
March 2nd, 2016 12:00
Did you ever get this resolved. I am seeing that problem now with same setting you indicated back then.
hdtewes
2 Posts
0
March 2nd, 2016 23:00
The computer I wanted to wake up was in another network segment. When the computer had been turned on in the last hours and i had a connection to him, my computer got his ip and mac in his arp-table.
After 4 hours, the arp tables are cleared. This is the reason why i couldnt wake up the computer over night.
The solution was to use netcast WOL, not direct WOL. So you have to use the broadcast-address of the network where the other computer resides in. And be careful to use the right netmask when calculating the broadcast-address.
Mr Toves
2 Posts
0
March 3rd, 2016 10:00
Thanks for responding. Hmmm,
I use WOL two ways. One is via Landesk and broadcast to a "machine Domain Rep" on the same subnet. The Landesk sever is in a different location, but I remote into it.
The box I am testing is in the same room as me. So, when I do a Landesk WOL, it is originating from a MDR on the same subnet, and the same switch as me.And when I do WOL locally thru a magic packet program (nirsoft wakemeonlan) It is also originating from a box on the same subnet . . . .and behind the same switch again. My computer is both the MDR for Landesk AND the computer trying the nirsoft wake up.
And WOL fails BOTH ways after the machine is off overnight. What you are saying about ARP table sounds right, but I.m just not sure that comes into play here in either of the scenarios. But I'm looking.
I have an e-mail into Dell about it now. we shall see. Thanks for the response.