The attempt to retrieve the MAC address using a SendARP succeeded however the MAC address returned may not be correct because the EminentWare Server is not on the same subnet

5/2/2021 1:22 PM

5/2/2021 1:22 PM

When you run Check and Manage Computer connectivity via deploy the client components you may see following result in the task.

Successfully connected to WMI.
Hostname is DWIS01.SWT.xyz.com

The attempt to retrieve the MAC address using a SendARP succeeded, however the MAC address returned (00-00-0C-07-AC-D3) may not be correct because the EminentWare Server is not on the same subnet as the targeted IP address. Tracing route to ********* over a maximum of 30 hops:

You may notice following errors in patch manager logs
ERROR_BAD_NET_NAME = 67
The network name cannot be found. This error is returned on Windows Vista and later when an ARP reply to the SendARP request was not received. This error occurs if the destination IPv4 address could not be reached because it is not on the same subnet or the destination computer is not operating.

We can partly-reproduce using PC from other subnet by running cmd from PAS to retrieve MAC of one of the end point nodes.
Example:
nbtstat -a 10.14.220.127 #expected result no MAC address resolved for 10.14.220.127

You have verified the WMI requirements as well.

 

Patch Manager

Patch manager server and the end point are not in same subnet
 

This can be due to Patch manager server and the end points are in different network segments i.e another physical network segment (ARP requests are routed).

In this case having automation server in same subnet as the target nodes can make difference with MAC resolution during Check and Manage Computer connectivity, and it is the only workaround we can see per design of the product.