- Disabling DHCP in Ndis miniport driver
- Posted by Michael on April 16th, 2008
I have an NDIS miniport driver in an embedded device that will always use a
static address. The static address is configured using netsh.exe after the
driver has been installed. However, by the time netsh.exe runs, the adapter
is already attempting to DHCP. We don't have DHCP on this internal network,
and never will. This causes a very long delay in netsh.exe being able to
configure the static address. Sometimes it seems to delay forever, and
netsh.exe is never able to complete. During this time when netsh is trying
to configure the adapter but isn't able to, we can't even configure the
TCP/IP properties manually. The Properties sheet gives the following error:
"Some of the controls on this property sheet are disabled because one or
more other Network property sheets are already open. To use these controls,
close all these property sheets and then reopen this one."
Is there a way to prevent DHCP from ever being attempted during driver
installation time? If not, how can DHCP be aborted so that the static
address can be configured quickly?
Thanks!
- Posted by subhash on April 17th, 2008
On Apr 16, 8:47*pm, Michael <Mich...@discussions.microsoft.com> wrote:
NDIS miniport driver is in data link layer. DHCP is in application
layer.
So nothing realted to DHCP is done in driver. you might need to
change
start up configuration of your system. may be disabling DHCP client
during startup will work.
Use "msconfig" utility to cofigure your startup.
With Best Regards
Subhash Sukumaran
- Posted by chris.aseltine@gmail.com on April 17th, 2008
On Apr 16, 10:47 am, Michael <Mich...@discussions.microsoft.com>
wrote:
I embedded a DHCP server right into my NDIS miniport itself. When the
DHCP request comes, I just feed it my static address. Thus, it's
ready right away, *and* you don't have to mess with netsh.exe later.
Just a thought.
- Posted by subhash on April 17th, 2008
On Apr 17, 5:28*pm, chris.aselt...@gmail.com wrote:
good. But then the driver becomes pretty customised. Otherwise we
need to differentiate
between normal request and the request in this situation. By the way
what is the OID corresponding to
DHCP request in miniport driver.
Regards
Subhash
.
- Posted by PCAUSA on April 17th, 2008
On Apr 17, 8:47*am, subhash <subhashsukuma...@gmail.com> wrote:
There is no NDIS OID for DHCP. WIndows simply sends/receives DHCP
packets on the network.
Thomas F. Divine
http://www.pcausa.com
- Posted by subhash on April 18th, 2008
On Apr 17, 6:41*pm, PCAUSA <pca...@gmail.com> wrote:
static address and send upwards(back to NDIS layer), right?
Regards
Subhash
