Wake On Lan uses wrong IP

AI Logic 1

I’m trying to wake up some of my clients using endpoint configuration manager. After issuing the request, I can see the following two lines in the BgbServer.log:

Sending machine specific push task (ClientID: GUID:62563B92-B9C6-4476-B494-9CE9BAD0E2C6 TaskParam: <WakeupInfo WakerMachineID="16778080"> <NetworkInfo SleepingMachineID="16777836" IPAddress="192.168.56.1" IPSubnet="192.168.56.0" MACAddress="6C:0B:84:3C:B7:AC" MulticastAddress="" Flags="0" /></WakeupInfo>)    SMS_NOTIFICATION_SERVER 02.07.2021 23:01:29 10868 (0x2A74)
Sending machine specific push task (ClientID: GUID:EB14E467-80A6-4FAD-AA01-FB4F49906452 TaskParam: <WakeupInfo WakerMachineID="16778102"> <NetworkInfo SleepingMachineID="16777836" IPAddress="192.168.56.1" IPSubnet="192.168.56.0" MACAddress="0A:00:27:00:00:03" MulticastAddress="" Flags="0" /></WakeupInfo>)    SMS_NOTIFICATION_SERVER 02.07.2021 23:01:29 10868 (0x2A74)

If I check the device in endpoint configuration manager, both MAC addresses from the two log entries, i.e. 0A:00:27:00:00:03 and 6C:0B:84:3C:B7:AC, are listed there. And in fact, the device has two NICs, one being the actual ethernet NIC (6C:0B:84:3C:B7:AC, 10.25.34.141) and one being a virtual NIC (0A:00:27:00:00:03, 192.168.56.1) created by oracle virtual box to allow network access for VMs hosted on the device. Unfortunately, the wake up does not work and in fact, a closer look at the two log entries shows that the entries for both MAC addresses uses the IP subnet 192.168.56.0, which of course wont work. It should use 10.25.34.0 for the MAC 6C:0B:84:3C:B7:AC but it does not seem to. In fact, if I check which clients got the given IDs (GUID:62563B92-B9C6-4476-B494-9CE9BAD0E2C6, GUID:EB14E467-80A6-4FAD-AA01-FB4F49906452) they are in completely different subnets, probably also having the 192.168.56.1 subnet due to also having the virtual NIC.

Does someone have an idea how I can fix this?
Any help would be highly appreciated!

Simon Ren-MSFT 30,116 Reputation points Microsoft Vendor

2021-07-05T08:38:58.963+00:00

Hi,

Thanks for posting in Microsoft Q&A forum.

Do the problematic clients all have two NICs? To narror down the issue, if we disable the virtual NIC, does Wake On Lan work well?

Best regards,
Simon
AI Logic 1 Reputation point

2021-07-06T13:51:56.643+00:00

Hello,
yes, they all have two NICs. If I disable the second NIC and rerun the hardware inventory, the second MAC and IP vanishes from the device object and the log now only shows the correct MAC and IP. Furthermore, a device in the correct subnet is now elected to wake up the other device. However, using Wireshark, I could verify that the WoL Paket is send on the virtual NIC and thus again never reaches the device that is to be woken up. Only if I also disable the virtual NIC on the device sending the WoL packet it works as expected.
Simon Ren-MSFT 30,116 Reputation points Microsoft Vendor

2021-07-07T02:08:39.317+00:00

Hi,

Thanks for your reply.

It's really a strange issue. Due to limited resource, it's recommended to submit a case with Microsoft to get better support:
https://support.serviceshub.microsoft.com/supportforbusiness

Best regards,
Simon
AI Logic 1 Reputation point

2021-07-07T12:46:40.827+00:00

Hey Simon,
thank you for trying to help us. Unfortunately, we’re a school and don’t really have the budget for a support contract. Is there anything else we can try?
Best regards
Alex
Simon Ren-MSFT 30,116 Reputation points Microsoft Vendor

2021-07-09T09:00:20.303+00:00

Hi,

Thanks for your reply.

If possible, please contact oracle virtual box support to see if they have any useful information.

I will also do more research, if there is any update, I will let you know. Thanks for your understanding.

Best regards,
Simon