Re: About NdisQueryPacket!!
From: Thomas F. Divine [DDK MVP] (tdivine_at_NOpcausaSPAM.com)
Date: 02/22/05
- Next message: Doron Holan [MS]: "Re: addDevice failure"
- Previous message: Max Paklin: "Re: BDA -S Problem"
- In reply to: Frog: "Re: About NdisQueryPacket!!"
- Next in thread: Frog: "Re: About NdisQueryPacket!!"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 22 Feb 2005 01:23:52 -0500
"Frog" <Frog@discussions.microsoft.com> wrote in message
news:F31A76BA-14D6-43BC-889D-A339DC13A59E@microsoft.com...
> yes, it is a Gigabit NIC. Does Passthru not support Gigabit NIC? thank
> you.
>
PassThru supports Gigabit Jumbo frames fairly nicely AFAIK. You will simply
see packet total sizes that are larger than 1514 bytes. The maximum Jumbo
packet size is set on the Advanced tab of the adapter's Properties dailog in
the Network Control Pannel.
You can query for the maximum total size using OID_GEN_MAXIMUM_TOTAL_SIZE.
Tools like OIDScope can let you make the query fairly simply. See:
http://www.pcausa.com/Utilities/ndistools.htm
If the value that you are seeing from NdisQueryPacket is bigger that the
value returned by the OID_GEN_MAXIMUM_TOTAL_SIZE query or is larger than the
Jumbo frame size specified for the adapter, then there is some other
problem...
Good luck,
Thomas F. Divine, Windows DDK MVP
http://www.rawether.net
> "Thomas F. Divine [DDK MVP]" wrote:
>
>> Humm...
>>
>> Could this be an adapter that supports Large Send function of NDIS Task
>> Offload?
>>
>> If the number was a little smaller I might think it was a Gigabit NIC
>> sending Jumbo frames, but I don't think that Jumbo frames are that
>> large...
>>
>> Thomas F. Divine, Windows DDK MVP
>> http://www.pcausa.com
>>
>> "Pavel A." <pavel_a@NOwritemeNO.com> wrote in message
>> news:OCeZ$VIGFHA.1260@TK2MSFTNGP12.phx.gbl...
>> > "Frog" <Frog@discussions.microsoft.com> wrote in message
>> > news:BB5ECDCA-EBA9-4C6E-8EA3-3161F8AFA7AA@microsoft.com...
>> >> If error happens , in most case ,the wrong packet size is 16114, and
>> >> sometimes 17574. why? Is there something wrong with NdisQueryPacket
>> >> itself?
>> >
>> > Maybe yes. These numbers are too big - can't be explained by VLAN tags
>> > or
>> > anything like.
>> > --PA
>> >
>> >
>> >
>> >> "Pavel A." wrote:
>> >>
>> >> > "About NdisQueryPacket" <About
>> >> > NdisQueryPacket@discussions.microsoft.com> wrote in message
>> >> > news:4F3ED3D7-702F-4FBD-86D9-66B5C47529C6@microsoft.com...
>> >> > > Unfortunately, sometimes(when accessed through the network
>> >> > > neighbor),
>> >> > > the
>> >> > > value of TotalPacketSize is bigger than 1514 which is the max size
>> >> > > of
>> >> > > Ethernet frame.
>> >> >
>> >> > Can you tell what exactly is the TotalPacketSize?
>> >> > --PA
>> >> >
>> >> >
>> >> >
>> >
>> >
>>
>>
>>
- Next message: Doron Holan [MS]: "Re: addDevice failure"
- Previous message: Max Paklin: "Re: BDA -S Problem"
- In reply to: Frog: "Re: About NdisQueryPacket!!"
- Next in thread: Frog: "Re: About NdisQueryPacket!!"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
