If NdisSend returns PENDING, then your protocol's SendCompleteHandler
should be getting called with the end result.

Bryan S. Burgin
bburgin@microsoft.com

This posting is provided "AS IS" with no warranties, and confers no rights.

Strangely, NdisSend returns PENDING (I can see the IM
sends it), but protocol's SendCompleteHandler was not
called and that's the problem.

This happens when I pull the LAN cable(s) out from NIC.
The target runs XP.
Thanks Bryan.