Alireza
Wed Mar 19 16:04:40 CDT 2008
Right. Using new version of NDIS_OFFLOAD implies providing support for IPSec
task offload. On the other hand very likely you don't have a
DirectOidRequestHandler and NDIS fails the call.
-ali
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Peter" <x@y> wrote in message news:egwxeKeiIHA.6136@TK2MSFTNGP03.phx.gbl...
>I was using V2 of all of the structures, especially V2 of the NDIS_OFFLOAD.
>However, that seems to be the problem since this driver doesn't support
>IPsecV2. If I use V1 of this structure, then the call to
>NdisMSetMiniportAttributes doesn't fail when I register the offload
>capabilities.
>
> So, it appears that Server 2008 will fail the registration if V2 is used
> and IPsevV2 member of NDIS_OFFLOAD is all 0's. Is this correct?
>
> "Alireza Dabagh [MS]" <alid@online.microsoft.com> wrote in message
> news:%23npukhViIHA.3400@TK2MSFTNGP03.phx.gbl...
>> In NDIS 6.1, Some of the data structures referenced in this structure
>> have moved to version 2. NDIS expects an NDIS 6.1 driver to use NDIS 6.1
>> data structures whenever applicable.
>>
>> -ali
>>
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Peter" <x@y> wrote in message
>> news:uClkP4SiIHA.3780@TK2MSFTNGP06.phx.gbl...
>>> Hi!
>>>
>>> I'm running into failures with my NDIS 6.1 miniport when it calls
>>> NdisMSetMiniportAttributes to register its
>>> NDIS_MINIPORT_ADAPTER_OFFLOAD_ATTRIBUTES. Although this driver supports
>>> TOE, I see STATUS_NOT_SUPPORTED returned from NdisMSetMiniportAttributes
>>> regardless of whether I set DefaultTcpConnectionOffloadConfiguration and
>>> TcpConnectionOffloadHardwareCapabilities to NULL.
>>>
>>> What's odd is this call works if I set the MajorNdisVersion to 6 and
>>> MinorNdisVersion to 0 in the NDIS_MINIPORT_DRIVER_CHARACTERISTICS struct
>>> passed into NdisMRegisterMiniportDriver.
>>>
>>> Has anyone else seen anything like this?
>>>
>>> Thanks!
>>>
>>
>
>