A bug in NDISPROT or an issue in the NDIS core?

Tech-Archive recommends: Fix windows errors by optimizing your registry

I've just tested the same things with the original NDISPROT sample from Win 2003 Server DDK SP1.

It behaves the same strange way when I use uiotest.exe to send RAW packets between 2 machines (Win 2003 SP! x86 and Win XP SP2 x86).
Only 'Bytes received' is updated when raw packets are sent/received.
'Bytes sent' and both sent/received packets counters are not updated.

So I suspect the NDISPROT sample does not do something that needed for correct counting of raw outcoming packets.

But not counting of incoming packets says that an issue may be present in the NDIS core logic.

Can somebody shed some light on the problem?

Thank you.
--
Best regards,
Valeriy Glushkov

"Stephan Wolf [MVP]" <stewo68@xxxxxxxxxxx> ???????/???????? ? ???????? ?????????: news:1157119408.267109.39590@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hmm, this is really weird. I would expect TaskMan to read the NIC
driver's counters, i.e. the NDIS OIDs. But this is apparently not the
case.

Tom/Eliyas/Max/others: Which network counters does TaskMan use to show
the network usage?

Thanks, Stephan
---
Valeriy Glushkov wrote:
Hi,

One more detail:
It seems that the packet counters in the NIC are different from the counters
in the Task manager.
While the NIC's 'Status' window shows real packet counts, the Network tab
from the Task Manager counts only IP packets and completely ignores my
custom Ethernet frames (with exception for receive byte counts).

Has anybody seen the issue with a custom protocol driver?

--
Best regards,
Valeriy Glushkov


.