NDIS protocol bind error

NTDEV
1

Hi,

I have a NDIS miniport that has a WDM lower edge and a ndis upper edge. When
I install a 3rd party PPPoE client, it is not binding to my miniport. What
could be the problem?

I compared my miniport’s INF with another NIC’s INF (to which the
abovementioned PPPoE client is binding successfully). The only difference
was in the Ndi\Interfaces\LowerRange key…I have specified “adsl” and the
NIC INF has mentioned “ethernet”…Could this be a problem?

I’d appreciate any suggestions/ideas reg this.

TIA
MRK

2

On Wed, 2003-11-26 at 12:11, Kannan RAMANATHAN wrote:

Hi,

I have a NDIS miniport that has a WDM lower edge and a ndis upper edge. When
I install a 3rd party PPPoE client, it is not binding to my miniport. What
could be the problem?

I compared my miniport’s INF with another NIC’s INF (to which the
abovementioned PPPoE client is binding successfully). The only difference
was in the Ndi\Interfaces\LowerRange key…I have specified “adsl” and the
NIC INF has mentioned “ethernet”…Could this be a problem?

If your miniport emulates an Ethernet adapter, it should list Ethernet
in its LowerRange. Check out the netvmini inf for a minimal ethernet
nic inf (but note that it is set up for a virtual nic, which may not be
what you want).

I don’t know if that’s the problem or not, though. How is the
third-party PPPoE driver structured? It’s hard to say what the bindings
*should* look like without some more information.

I’d recommend setting up a physical ethernet NIC and digging around with
!ndiskd in WinDbg. See what a normal bindings setup looks like and
compare notes. RAS bindings can be tricky to sort out with ndiskd, but
if you stare at it long enough it should eventually make sense.

-sd

3

Hi Kannan,

Look at the Inf file of PPPoE that will give u a better understanding, for this problem.

 

Good Luck,



From: Kannan RAMANATHAN <kannan.ramanathan>

>Reply-To: “Windows System Software Devs Interest List”
>To: “Windows System Software Devs Interest List”
>Subject: [ntdev] NDIS protocol bind error
>Date: Wed, 26 Nov 2003 23:41:13 +0530
>
>Hi,
>
>I have a NDIS miniport that has a WDM lower edge and a ndis upper edge. When
>I install a 3rd party PPPoE client, it is not binding to my miniport. What
>could be the problem?
>
>I compared my miniport’s INF with another NIC’s INF (to which the
>abovementioned PPPoE client is binding successfully). The only difference
>was in the Ndi\Interfaces\LowerRange key…I have specified “adsl” and the
>NIC INF has mentioned “ethernet”…Could this be a problem?
>
>I’d appreciate any suggestions/ideas reg this.
>
>TIA
>MRK
>
>
>—
>Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
>
>You are currently subscribed to ntdev as: xxxxx@hotmail.com
>To unsubscribe send a blank email to xxxxx@lists.osr.com
</kannan.ramanathan>

The Great MSN Sale. Get shopping discounts. Win exciting prizes!

4

Thanks a lot guys. The problem is fixed now.

— MRK

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Steve Dispensa
Sent: Thursday, November 27, 2003 12:34 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] Re: NDIS protocol bind error

If your miniport emulates an Ethernet adapter, it should list Ethernet in
its LowerRange. Check out the netvmini inf for a minimal ethernet nic inf
(but note that it is set up for a virtual nic, which may not be
what you want).

I don’t know if that’s the problem or not, though. How is the third-party
PPPoE driver structured? It’s hard to say what the bindings
*should* look like without some more information.

I’d recommend setting up a physical ethernet NIC and digging around with
!ndiskd in WinDbg. See what a normal bindings setup looks like and compare
notes. RAS bindings can be tricky to sort out with ndiskd, but if you stare
at it long enough it should eventually make sense.

-sd

5

> abovementioned PPPoE client is binding successfully). The only difference

was in the Ndi\Interfaces\LowerRange key…I have specified “adsl” and the
NIC INF has mentioned “ethernet”…Could this be a problem?

Surely.

Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com