Getting this?

-bash-4.2$ ping 192.168.0.224
PING 192.168.0.224 (192.168.0.224) 56(84) bytes of data.
64 bytes from 192.168.0.224: icmp_seq=1 ttl=127 time=0.860 ms
64 bytes from 192.168.0.224: icmp_seq=1 ttl=127 time=1.22 ms (DUP!)
64 bytes from 192.168.0.224: icmp_seq=2 ttl=127 time=0.622 ms
64 bytes from 192.168.0.224: icmp_seq=2 ttl=127 time=0.872 ms (DUP!)

Apparently this can cause issues on different subnets as well:

# ping 192.168.0.224
PING 192.168.0.224 (192.168.0.224) 56(84) bytes of data.
^C
— 192.168.0.224 ping statistics —
3 packets transmitted, 0 received, 100% packet loss, time 2000ms

It’s probably because of this:

PS C:\Users\Administrator.DC01.000> Get-NlbClusterNode dc01 | fl *

Cluster : ADDNS
Name : dc01
InterfaceName : NLB
Host : dc01.domain.abc
State : Converged(default)
HostPriority : 1
AdapterGuid : {61065CC2-4C37-419F-9A8C-B3ED9277427E}
InitialHostState : Started
PersistSuspendOnReboot : False
MaskSourceMac : True
FilterIcmp : 0
GreDescriptorTimeout : 10

PS C:\Users\Administrator.DC01.000>

To set this in the registry, go to:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\services\WLBS\Parameters\Interface\{GUID}\FilterICMP

And set this to 1 instead of 0.  And restart.  Right now, there doesn’t appear to be any PowerShell commands for this.  Test it out:

-bash-4.2$ ping 192.168.0.224
PING 192.168.0.224 (192.168.0.224) 56(84) bytes of data.
64 bytes from 192.168.0.224: icmp_seq=1 ttl=127 time=1.54 ms
64 bytes from 192.168.0.224: icmp_seq=2 ttl=127 time=0.931 ms
64 bytes from 192.168.0.224: icmp_seq=3 ttl=127 time=0.815 ms

Great!  This solves the DUP problem, but not the ping problem to the NLB from other subnets.  This is a different problem with a different solution that can be seen here:

Unable to ping NLB Gateway from outside the NLB subnet or different subnets

Enjoy uninterrupted connectivity.

Cheers,