Excluding A Network Adapter During INetCfgClassSetup::Install

Hi!

Is there a way to exclude one or more network interfaces from being bound to
a network component during the components installation through either the
INetCfgClassSetup::Install or INetCfgClassSetup::SelectAndInstall methods?
Also, is this possible using Difx?

Thanks!

Arkady
Sun Sep 02 01:30:58 PDT 2007

Check bindview sample in DDK
Arkady

"Jake" <ImInSoquel@nospam.nospam> wrote in message
news:%23bwmiwM7HHA.3716@TK2MSFTNGP03.phx.gbl...
> Hi!
>
> Is there a way to exclude one or more network interfaces from being bound
> to a network component during the components installation through either
> the INetCfgClassSetup::Install or INetCfgClassSetup::SelectAndInstall
> methods? Also, is this possible using Difx?
>
> Thanks!
>

Stephan
Wed Sep 05 04:35:57 PDT 2007

Well, you cannot prevent the network configuration subsystem from
actually *creating* the binding pathes between protocols and network
interfaces.

But you can prevent an individual binding path from getting *enabled*.
This is usually done by implementing a Notify Object for a protocol.
The Notify Object can then control all bindings to its own protocol as
well as to other protocols and/or network interfaces.

IIRC, there are some Notify Object samples coming with some of the
protocol samples in the DDK/WDK (e.g. "...\WINDDK\3790.1830\src\network
\ndis\mux\notifyob").

Stephan
---
On Sep 1, 9:13 pm, "Jake" <ImInSoq...@nospam.nospam> wrote:
> Hi!
>
> Is there a way to exclude one or more network interfaces from being bound to
> a network component during the components installation through either the
> INetCfgClassSetup::Install or INetCfgClassSetup::SelectAndInstall methods?
> Also, is this possible using Difx?
>
> Thanks!