![]() ![]() That being said, WOL uses Directed Broadcast for delivery across subnets. All IP broadcast packets are addressed to the broadcast MAC address. Only a Layer 2 broadcast or an unknown unicast frame is sent out to all switch ports. If there is a Layer 2 switch between the router and the PC, which is true for most networks today, the switch does not know to which port the PC is physically connected. Therefore, only a local subnet IP broadcast packet will be transmitted on the broadcast segment. So if you can deliver this packet to the target NIC you are in business.īecause the PC is asleep, it will not have an IP address and will not respond to Address Resolution Protocols (ARPs) from the router. It is not actually parsed by a full protocol stack, all the target NIC card looks for is the unique WOL payload for that MAC Address. The target NIC card doesn't care what protocol or port it is using. WOL is primarily a Layer 2 function in that it is solely dependent on the MAC address. ![]() Here's a very in-depth technical background of WOL (for those who care): subnet 255.255.255.0 -mac ','true') "> Įnjoy waking up all those sleepy computers! With: (Fix the Path to poweroff.exe to match your environment) Lansweeper support says in the next version you can specify a custom action for WOLīut for now, here's a simple way to get WOL to work across subnets in 3.5.2:Ģ)Place poweroff.exe into the folder with the rest of the tools you use for custom actionsģ)Backup & then modify your it-compdetail.aspx file as follows The way to Wake up computers in different subnets is via "Directed Broadcast" Unfortunately the utility included in 3.5.2 (WOL.exe) does not generate directed broadcast packets. In Lansweeper 3.5.2 the link for Network Wake on Lan will only wake up computers in the same subnet. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |