Disabling DHCP in Ndis miniport driver
in [Device Drivers]
|
From: Michael on 16 Apr 2008 11:47 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!
From: subhash on 17 Apr 2008 04:37 On Apr 16, 8:47 pm, Michael <Mich...(a)discussions.microsoft.com> wrote: > 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! 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
From: chris.aseltine on 17 Apr 2008 08:28 On Apr 16, 10:47 am, Michael <Mich...(a)discussions.microsoft.com> wrote: > 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? 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.
From: subhash on 17 Apr 2008 08:47 On Apr 17, 5:28 pm, chris.aselt...(a)gmail.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. 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 .
From: PCAUSA on 17 Apr 2008 09:41
On Apr 17, 8:47 am, subhash <subhashsukuma...(a)gmail.com> wrote: > On Apr 17, 5:28 pm, chris.aselt...(a)gmail.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. > > 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 > . There is no NDIS OID for DHCP. WIndows simply sends/receives DHCP packets on the network. Thomas F. Divine http://www.pcausa.com |