Jump to content

DHCP will not bind


Recommended Posts

Guest darkstar_rising
Posted

I have a server 2k3 R2 SP2 which is a DC and I cannot get the DHCP service to

bind to the IP address.

I have followed this post

http://www.winserverkb.com/Uwe/Forum.aspx/windows-server-sbs/45189/DHCP-not-renewing-leases

 

 

which pretty much describes what is happening to me.

when I go to

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TCpip\Parameter\Interfa

ces\[NIC''s GUID]\BindToDHCPServer - this key 'bind to DHCPServer' does not

exist.

 

Although this is a Dell machine I do not have open manage installed on this

server.

 

I have stopped short of restarting the server with a clean boot because I was

wondering if the fact that the above registry key is missing points to

something else.

  • Replies 12
  • Created
  • Last Reply

Popular Days

Guest Meinolf Weber
Posted

Re: DHCP will not bind

 

Hello darkstar_rising,

 

The key "BindToDHCPServer" i can not see on both of my 2003 SP2 server and

DHCP is working fine. So what is the problem your clients have? Is the server

authorized in AD?

 

Best regards

 

Meinolf Weber

Disclaimer: This posting is provided "AS IS" with no warranties, and confers

no rights.

** Please do NOT email, only reply to Newsgroups

** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

 

> I have a server 2k3 R2 SP2 which is a DC and I cannot get the DHCP

> service to

> bind to the IP address.

> I have followed this post

> http://www.winserverkb.com/Uwe/Forum.aspx/windows-server-sbs/45189/DHC

> P-not-renewing-leases

> which pretty much describes what is happening to me.

> when I go to

> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TCpip\Parameter\I

> nterfa

> ces\[NIC''s GUID]\BindToDHCPServer - this key 'bind to DHCPServer'

> does not

> exist.

> Although this is a Dell machine I do not have open manage installed on

> this server.

>

> I have stopped short of restarting the server with a clean boot

> because I was wondering if the fact that the above registry key is

> missing points to something else.

>

Guest darkstar
Posted

Re: DHCP will not bind

 

many thanks for your help.

 

the dhcp server will not authenticate, I'm sure the reason is that when I go

to the dhcp console and look at bindings in the advanced properties the NIC

is listed but it is not ticked. If I tick the box to bind dhcp to the NIC the

apply button is greyed out and the setting does not stick.

I can click OK to exit out of the properties, but when I go back in the

check box for the internal NIC remains unchecked.

 

This means that it will not server dhcp clients

 

"Meinolf Weber" wrote:

> Hello darkstar_rising,

>

> The key "BindToDHCPServer" i can not see on both of my 2003 SP2 server and

> DHCP is working fine. So what is the problem your clients have? Is the server

> authorized in AD?

>

> Best regards

>

> Meinolf Weber

> Disclaimer: This posting is provided "AS IS" with no warranties, and confers

> no rights.

> ** Please do NOT email, only reply to Newsgroups

> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

>

>

> > I have a server 2k3 R2 SP2 which is a DC and I cannot get the DHCP

> > service to

> > bind to the IP address.

> > I have followed this post

> > http://www.winserverkb.com/Uwe/Forum.aspx/windows-server-sbs/45189/DHC

> > P-not-renewing-leases

> > which pretty much describes what is happening to me.

> > when I go to

> > HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TCpip\Parameter\I

> > nterfa

> > ces\[NIC''s GUID]\BindToDHCPServer - this key 'bind to DHCPServer'

> > does not

> > exist.

> > Although this is a Dell machine I do not have open manage installed on

> > this server.

> >

> > I have stopped short of restarting the server with a clean boot

> > because I was wondering if the fact that the above registry key is

> > missing points to something else.

> >

>

>

>

Guest Meinolf Weber
Posted

Re: DHCP will not bind

 

Hello darkstar,

 

What is about the step with msconfig described from Steven Zhu? Did you follow

it?

 

Best regards

 

Meinolf Weber

Disclaimer: This posting is provided "AS IS" with no warranties, and confers

no rights.

** Please do NOT email, only reply to Newsgroups

** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

 

> many thanks for your help.

>

> the dhcp server will not authenticate, I'm sure the reason is that

> when I go

> to the dhcp console and look at bindings in the advanced properties

> the NIC

> is listed but it is not ticked. If I tick the box to bind dhcp to the

> NIC the

> apply button is greyed out and the setting does not stick.

> I can click OK to exit out of the properties, but when I go back in

> the

> check box for the internal NIC remains unchecked.

> This means that it will not server dhcp clients

>

> "Meinolf Weber" wrote:

>

>> Hello darkstar_rising,

>>

>> The key "BindToDHCPServer" i can not see on both of my 2003 SP2

>> server and DHCP is working fine. So what is the problem your clients

>> have? Is the server authorized in AD?

>>

>> Best regards

>>

>> Meinolf Weber

>> Disclaimer: This posting is provided "AS IS" with no warranties, and

>> confers

>> no rights.

>> ** Please do NOT email, only reply to Newsgroups

>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

>>> I have a server 2k3 R2 SP2 which is a DC and I cannot get the DHCP

>>> service to

>>> bind to the IP address.

>>> I have followed this post

>>> http://www.winserverkb.com/Uwe/Forum.aspx/windows-server-sbs/45189/D

>>> HC

>>> P-not-renewing-leases

>>> which pretty much describes what is happening to me.

>>> when I go to

>>> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TCpip\Parameter

>>> \I

>>> nterfa

>>> ces\[NIC''s GUID]\BindToDHCPServer - this key 'bind to DHCPServer'

>>> does not

>>> exist.

>>> Although this is a Dell machine I do not have open manage installed

>>> on

>>> this server.

>>> I have stopped short of restarting the server with a clean boot

>>> because I was wondering if the fact that the above registry key is

>>> missing points to something else.

>>>

Guest Meinolf Weber
Posted

Re: DHCP will not bind

 

Hello darkstar,

 

If you open Network connections and go to "Advanced", "Advanced settings",

do you see your Local area connection and what is listed/checked under the

bindings part?

 

Best regards

 

Meinolf Weber

Disclaimer: This posting is provided "AS IS" with no warranties, and confers

no rights.

** Please do NOT email, only reply to Newsgroups

** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

 

> many thanks for your help.

>

> the dhcp server will not authenticate, I'm sure the reason is that

> when I go

> to the dhcp console and look at bindings in the advanced properties

> the NIC

> is listed but it is not ticked. If I tick the box to bind dhcp to the

> NIC the

> apply button is greyed out and the setting does not stick.

> I can click OK to exit out of the properties, but when I go back in

> the

> check box for the internal NIC remains unchecked.

> This means that it will not server dhcp clients

>

> "Meinolf Weber" wrote:

>

>> Hello darkstar_rising,

>>

>> The key "BindToDHCPServer" i can not see on both of my 2003 SP2

>> server and DHCP is working fine. So what is the problem your clients

>> have? Is the server authorized in AD?

>>

>> Best regards

>>

>> Meinolf Weber

>> Disclaimer: This posting is provided "AS IS" with no warranties, and

>> confers

>> no rights.

>> ** Please do NOT email, only reply to Newsgroups

>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

>>> I have a server 2k3 R2 SP2 which is a DC and I cannot get the DHCP

>>> service to

>>> bind to the IP address.

>>> I have followed this post

>>> http://www.winserverkb.com/Uwe/Forum.aspx/windows-server-sbs/45189/D

>>> HC

>>> P-not-renewing-leases

>>> which pretty much describes what is happening to me.

>>> when I go to

>>> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TCpip\Parameter

>>> \I

>>> nterfa

>>> ces\[NIC''s GUID]\BindToDHCPServer - this key 'bind to DHCPServer'

>>> does not

>>> exist.

>>> Although this is a Dell machine I do not have open manage installed

>>> on

>>> this server.

>>> I have stopped short of restarting the server with a clean boot

>>> because I was wondering if the fact that the above registry key is

>>> missing points to something else.

>>>

Guest darkstar
Posted

Re: DHCP will not bind

 

True - I have not followed this step. I shall do this now!

 

"Meinolf Weber" wrote:

> Hello darkstar,

>

> What is about the step with msconfig described from Steven Zhu? Did you follow

> it?

>

> Best regards

>

> Meinolf Weber

> Disclaimer: This posting is provided "AS IS" with no warranties, and confers

> no rights.

> ** Please do NOT email, only reply to Newsgroups

> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

>

>

> > many thanks for your help.

> >

> > the dhcp server will not authenticate, I'm sure the reason is that

> > when I go

> > to the dhcp console and look at bindings in the advanced properties

> > the NIC

> > is listed but it is not ticked. If I tick the box to bind dhcp to the

> > NIC the

> > apply button is greyed out and the setting does not stick.

> > I can click OK to exit out of the properties, but when I go back in

> > the

> > check box for the internal NIC remains unchecked.

> > This means that it will not server dhcp clients

> >

> > "Meinolf Weber" wrote:

> >

> >> Hello darkstar_rising,

> >>

> >> The key "BindToDHCPServer" i can not see on both of my 2003 SP2

> >> server and DHCP is working fine. So what is the problem your clients

> >> have? Is the server authorized in AD?

> >>

> >> Best regards

> >>

> >> Meinolf Weber

> >> Disclaimer: This posting is provided "AS IS" with no warranties, and

> >> confers

> >> no rights.

> >> ** Please do NOT email, only reply to Newsgroups

> >> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> >>> I have a server 2k3 R2 SP2 which is a DC and I cannot get the DHCP

> >>> service to

> >>> bind to the IP address.

> >>> I have followed this post

> >>> http://www.winserverkb.com/Uwe/Forum.aspx/windows-server-sbs/45189/D

> >>> HC

> >>> P-not-renewing-leases

> >>> which pretty much describes what is happening to me.

> >>> when I go to

> >>> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TCpip\Parameter

> >>> \I

> >>> nterfa

> >>> ces\[NIC''s GUID]\BindToDHCPServer - this key 'bind to DHCPServer'

> >>> does not

> >>> exist.

> >>> Although this is a Dell machine I do not have open manage installed

> >>> on

> >>> this server.

> >>> I have stopped short of restarting the server with a clean boot

> >>> because I was wondering if the fact that the above registry key is

> >>> missing points to something else.

> >>>

>

>

>

Guest darkstar
Posted

Re: DHCP will not bind

 

mmmmm

I have restarted and used selective startup - no system.ini, no win.ini, no

startup items and all non microsoft services stopped.

I'm afraid there is no difference. DHCP still refuses to bind to the NIC

 

"darkstar" wrote:

> True - I have not followed this step. I shall do this now!

>

> "Meinolf Weber" wrote:

>

> > Hello darkstar,

> >

> > What is about the step with msconfig described from Steven Zhu? Did you follow

> > it?

> >

> > Best regards

> >

> > Meinolf Weber

> > Disclaimer: This posting is provided "AS IS" with no warranties, and confers

> > no rights.

> > ** Please do NOT email, only reply to Newsgroups

> > ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> >

> >

> > > many thanks for your help.

> > >

> > > the dhcp server will not authenticate, I'm sure the reason is that

> > > when I go

> > > to the dhcp console and look at bindings in the advanced properties

> > > the NIC

> > > is listed but it is not ticked. If I tick the box to bind dhcp to the

> > > NIC the

> > > apply button is greyed out and the setting does not stick.

> > > I can click OK to exit out of the properties, but when I go back in

> > > the

> > > check box for the internal NIC remains unchecked.

> > > This means that it will not server dhcp clients

> > >

> > > "Meinolf Weber" wrote:

> > >

> > >> Hello darkstar_rising,

> > >>

> > >> The key "BindToDHCPServer" i can not see on both of my 2003 SP2

> > >> server and DHCP is working fine. So what is the problem your clients

> > >> have? Is the server authorized in AD?

> > >>

> > >> Best regards

> > >>

> > >> Meinolf Weber

> > >> Disclaimer: This posting is provided "AS IS" with no warranties, and

> > >> confers

> > >> no rights.

> > >> ** Please do NOT email, only reply to Newsgroups

> > >> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> > >>> I have a server 2k3 R2 SP2 which is a DC and I cannot get the DHCP

> > >>> service to

> > >>> bind to the IP address.

> > >>> I have followed this post

> > >>> http://www.winserverkb.com/Uwe/Forum.aspx/windows-server-sbs/45189/D

> > >>> HC

> > >>> P-not-renewing-leases

> > >>> which pretty much describes what is happening to me.

> > >>> when I go to

> > >>> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TCpip\Parameter

> > >>> \I

> > >>> nterfa

> > >>> ces\[NIC''s GUID]\BindToDHCPServer - this key 'bind to DHCPServer'

> > >>> does not

> > >>> exist.

> > >>> Although this is a Dell machine I do not have open manage installed

> > >>> on

> > >>> this server.

> > >>> I have stopped short of restarting the server with a clean boot

> > >>> because I was wondering if the fact that the above registry key is

> > >>> missing points to something else.

> > >>>

> >

> >

> >

Guest darkstar
Posted

Re: DHCP will not bind

 

local area connection is listed in the network connections advanced settings

correctly. There are two NICS - one is disabled. The active one is static IP.

The active NIC is at the top and I have

file and printer sharing

internet protocol tcp/ip

client for microsoft networks

internet protocol tcp/ip

ALL ticked

 

provider order is

 

microsoft terminal services

microsoft windows network

web client network

 

....and then some print providers

 

"Meinolf Weber" wrote:

> Hello darkstar,

>

> If you open Network connections and go to "Advanced", "Advanced settings",

> do you see your Local area connection and what is listed/checked under the

> bindings part?

>

> Best regards

>

> Meinolf Weber

> Disclaimer: This posting is provided "AS IS" with no warranties, and confers

> no rights.

> ** Please do NOT email, only reply to Newsgroups

> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

>

>

> > many thanks for your help.

> >

> > the dhcp server will not authenticate, I'm sure the reason is that

> > when I go

> > to the dhcp console and look at bindings in the advanced properties

> > the NIC

> > is listed but it is not ticked. If I tick the box to bind dhcp to the

> > NIC the

> > apply button is greyed out and the setting does not stick.

> > I can click OK to exit out of the properties, but when I go back in

> > the

> > check box for the internal NIC remains unchecked.

> > This means that it will not server dhcp clients

> >

> > "Meinolf Weber" wrote:

> >

> >> Hello darkstar_rising,

> >>

> >> The key "BindToDHCPServer" i can not see on both of my 2003 SP2

> >> server and DHCP is working fine. So what is the problem your clients

> >> have? Is the server authorized in AD?

> >>

> >> Best regards

> >>

> >> Meinolf Weber

> >> Disclaimer: This posting is provided "AS IS" with no warranties, and

> >> confers

> >> no rights.

> >> ** Please do NOT email, only reply to Newsgroups

> >> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> >>> I have a server 2k3 R2 SP2 which is a DC and I cannot get the DHCP

> >>> service to

> >>> bind to the IP address.

> >>> I have followed this post

> >>> http://www.winserverkb.com/Uwe/Forum.aspx/windows-server-sbs/45189/D

> >>> HC

> >>> P-not-renewing-leases

> >>> which pretty much describes what is happening to me.

> >>> when I go to

> >>> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TCpip\Parameter

> >>> \I

> >>> nterfa

> >>> ces\[NIC''s GUID]\BindToDHCPServer - this key 'bind to DHCPServer'

> >>> does not

> >>> exist.

> >>> Although this is a Dell machine I do not have open manage installed

> >>> on

> >>> this server.

> >>> I have stopped short of restarting the server with a clean boot

> >>> because I was wondering if the fact that the above registry key is

> >>> missing points to something else.

> >>>

>

>

>

Guest Meinolf Weber
Posted

Re: DHCP will not bind

 

Hello darkstar,

 

Check out this one:

http://support.microsoft.com/kb/832689/en-us

 

If you run "netstat -a -n -o" in a command prompt, check for port 67, normally

used by DHCP Server, to see if another application/service is using it.

 

Also, did you use the latest NIC drivers and did you try to reinstall them?

 

Best regards

 

Meinolf Weber

Disclaimer: This posting is provided "AS IS" with no warranties, and confers

no rights.

** Please do NOT email, only reply to Newsgroups

** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

 

> mmmmm

> I have restarted and used selective startup - no system.ini, no

> win.ini, no

> startup items and all non microsoft services stopped.

> I'm afraid there is no difference. DHCP still refuses to bind to the

> NIC

> "darkstar" wrote:

>

>> True - I have not followed this step. I shall do this now!

>>

>> "Meinolf Weber" wrote:

>>

>>> Hello darkstar,

>>>

>>> What is about the step with msconfig described from Steven Zhu? Did

>>> you follow it?

>>>

>>> Best regards

>>>

>>> Meinolf Weber

>>> Disclaimer: This posting is provided "AS IS" with no warranties, and

>>> confers

>>> no rights.

>>> ** Please do NOT email, only reply to Newsgroups

>>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

>>>> many thanks for your help.

>>>>

>>>> the dhcp server will not authenticate, I'm sure the reason is that

>>>> when I go

>>>> to the dhcp console and look at bindings in the advanced properties

>>>> the NIC

>>>> is listed but it is not ticked. If I tick the box to bind dhcp to

>>>> the

>>>> NIC the

>>>> apply button is greyed out and the setting does not stick.

>>>> I can click OK to exit out of the properties, but when I go back in

>>>> the

>>>> check box for the internal NIC remains unchecked.

>>>> This means that it will not server dhcp clients

>>>> "Meinolf Weber" wrote:

>>>>

>>>>> Hello darkstar_rising,

>>>>>

>>>>> The key "BindToDHCPServer" i can not see on both of my 2003 SP2

>>>>> server and DHCP is working fine. So what is the problem your

>>>>> clients have? Is the server authorized in AD?

>>>>>

>>>>> Best regards

>>>>>

>>>>> Meinolf Weber

>>>>> Disclaimer: This posting is provided "AS IS" with no warranties,

>>>>> and

>>>>> confers

>>>>> no rights.

>>>>> ** Please do NOT email, only reply to Newsgroups

>>>>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

>>>>>> I have a server 2k3 R2 SP2 which is a DC and I cannot get the

>>>>>> DHCP

>>>>>> service to

>>>>>> bind to the IP address.

>>>>>> I have followed this post

>>>>>> http://www.winserverkb.com/Uwe/Forum.aspx/windows-server-sbs/4518

>>>>>> 9/D

>>>>>> HC

>>>>>> P-not-renewing-leases

>>>>>> which pretty much describes what is happening to me.

>>>>>> when I go to

>>>>>> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TCpip\Parame

>>>>>> ter

>>>>>> \I

>>>>>> nterfa

>>>>>> ces\[NIC''s GUID]\BindToDHCPServer - this key 'bind to

>>>>>> DHCPServer'

>>>>>> does not

>>>>>> exist.

>>>>>> Although this is a Dell machine I do not have open manage

>>>>>> installed

>>>>>> on

>>>>>> this server.

>>>>>> I have stopped short of restarting the server with a clean boot

>>>>>> because I was wondering if the fact that the above registry key

>>>>>> is

>>>>>> missing points to something else.

Guest darkstar
Posted

Re: DHCP will not bind

 

It is WDS

udp 127.0.0.1 and 10.18.59.7 both listening on port 67

pidis 2152 which is svchost.exe WDSserver.

 

My test lab that I use at home before rolling something out at work has WDS

running together with DHCP.

Do you think I should be looking at WDS. I had a lot of trouble getting this

to work so I am loath to start messing around with it unless it really is the

culprit

 

 

"Meinolf Weber" wrote:

> Hello darkstar,

>

> Check out this one:

> http://support.microsoft.com/kb/832689/en-us

>

> If you run "netstat -a -n -o" in a command prompt, check for port 67, normally

> used by DHCP Server, to see if another application/service is using it.

>

> Also, did you use the latest NIC drivers and did you try to reinstall them?

>

> Best regards

>

> Meinolf Weber

> Disclaimer: This posting is provided "AS IS" with no warranties, and confers

> no rights.

> ** Please do NOT email, only reply to Newsgroups

> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

>

>

> > mmmmm

> > I have restarted and used selective startup - no system.ini, no

> > win.ini, no

> > startup items and all non microsoft services stopped.

> > I'm afraid there is no difference. DHCP still refuses to bind to the

> > NIC

> > "darkstar" wrote:

> >

> >> True - I have not followed this step. I shall do this now!

> >>

> >> "Meinolf Weber" wrote:

> >>

> >>> Hello darkstar,

> >>>

> >>> What is about the step with msconfig described from Steven Zhu? Did

> >>> you follow it?

> >>>

> >>> Best regards

> >>>

> >>> Meinolf Weber

> >>> Disclaimer: This posting is provided "AS IS" with no warranties, and

> >>> confers

> >>> no rights.

> >>> ** Please do NOT email, only reply to Newsgroups

> >>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> >>>> many thanks for your help.

> >>>>

> >>>> the dhcp server will not authenticate, I'm sure the reason is that

> >>>> when I go

> >>>> to the dhcp console and look at bindings in the advanced properties

> >>>> the NIC

> >>>> is listed but it is not ticked. If I tick the box to bind dhcp to

> >>>> the

> >>>> NIC the

> >>>> apply button is greyed out and the setting does not stick.

> >>>> I can click OK to exit out of the properties, but when I go back in

> >>>> the

> >>>> check box for the internal NIC remains unchecked.

> >>>> This means that it will not server dhcp clients

> >>>> "Meinolf Weber" wrote:

> >>>>

> >>>>> Hello darkstar_rising,

> >>>>>

> >>>>> The key "BindToDHCPServer" i can not see on both of my 2003 SP2

> >>>>> server and DHCP is working fine. So what is the problem your

> >>>>> clients have? Is the server authorized in AD?

> >>>>>

> >>>>> Best regards

> >>>>>

> >>>>> Meinolf Weber

> >>>>> Disclaimer: This posting is provided "AS IS" with no warranties,

> >>>>> and

> >>>>> confers

> >>>>> no rights.

> >>>>> ** Please do NOT email, only reply to Newsgroups

> >>>>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> >>>>>> I have a server 2k3 R2 SP2 which is a DC and I cannot get the

> >>>>>> DHCP

> >>>>>> service to

> >>>>>> bind to the IP address.

> >>>>>> I have followed this post

> >>>>>> http://www.winserverkb.com/Uwe/Forum.aspx/windows-server-sbs/4518

> >>>>>> 9/D

> >>>>>> HC

> >>>>>> P-not-renewing-leases

> >>>>>> which pretty much describes what is happening to me.

> >>>>>> when I go to

> >>>>>> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TCpip\Parame

> >>>>>> ter

> >>>>>> \I

> >>>>>> nterfa

> >>>>>> ces\[NIC''s GUID]\BindToDHCPServer - this key 'bind to

> >>>>>> DHCPServer'

> >>>>>> does not

> >>>>>> exist.

> >>>>>> Although this is a Dell machine I do not have open manage

> >>>>>> installed

> >>>>>> on

> >>>>>> this server.

> >>>>>> I have stopped short of restarting the server with a clean boot

> >>>>>> because I was wondering if the fact that the above registry key

> >>>>>> is

> >>>>>> missing points to something else.

>

>

>

Guest Meinolf Weber
Posted

Re: DHCP will not bind

 

Hello darkstar,

 

Check out this one:

In WDS, expand Servers and right click on your server. Click Properties.

Click the DHCP tab and check "Do not listen on port 67".

 

Best regards

 

Meinolf Weber

Disclaimer: This posting is provided "AS IS" with no warranties, and confers

no rights.

** Please do NOT email, only reply to Newsgroups

** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

 

> It is WDS

> udp 127.0.0.1 and 10.18.59.7 both listening on port 67

> pidis 2152 which is svchost.exe WDSserver.

> My test lab that I use at home before rolling something out at work

> has WDS running together with DHCP. Do you think I should be looking

> at WDS. I had a lot of trouble getting this to work so I am loath to

> start messing around with it unless it really is the culprit

>

> "Meinolf Weber" wrote:

>

>> Hello darkstar,

>>

>> Check out this one:

>> http://support.microsoft.com/kb/832689/en-us

>> If you run "netstat -a -n -o" in a command prompt, check for port 67,

>> normally used by DHCP Server, to see if another application/service

>> is using it.

>>

>> Also, did you use the latest NIC drivers and did you try to reinstall

>> them?

>>

>> Best regards

>>

>> Meinolf Weber

>> Disclaimer: This posting is provided "AS IS" with no warranties, and

>> confers

>> no rights.

>> ** Please do NOT email, only reply to Newsgroups

>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

>>> mmmmm

>>> I have restarted and used selective startup - no system.ini, no

>>> win.ini, no

>>> startup items and all non microsoft services stopped.

>>> I'm afraid there is no difference. DHCP still refuses to bind to the

>>> NIC

>>> "darkstar" wrote:

>>>> True - I have not followed this step. I shall do this now!

>>>>

>>>> "Meinolf Weber" wrote:

>>>>

>>>>> Hello darkstar,

>>>>>

>>>>> What is about the step with msconfig described from Steven Zhu?

>>>>> Did you follow it?

>>>>>

>>>>> Best regards

>>>>>

>>>>> Meinolf Weber

>>>>> Disclaimer: This posting is provided "AS IS" with no warranties,

>>>>> and

>>>>> confers

>>>>> no rights.

>>>>> ** Please do NOT email, only reply to Newsgroups

>>>>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

>>>>>> many thanks for your help.

>>>>>>

>>>>>> the dhcp server will not authenticate, I'm sure the reason is

>>>>>> that

>>>>>> when I go

>>>>>> to the dhcp console and look at bindings in the advanced

>>>>>> properties

>>>>>> the NIC

>>>>>> is listed but it is not ticked. If I tick the box to bind dhcp to

>>>>>> the

>>>>>> NIC the

>>>>>> apply button is greyed out and the setting does not stick.

>>>>>> I can click OK to exit out of the properties, but when I go back

>>>>>> in

>>>>>> the

>>>>>> check box for the internal NIC remains unchecked.

>>>>>> This means that it will not server dhcp clients

>>>>>> "Meinolf Weber" wrote:

>>>>>>> Hello darkstar_rising,

>>>>>>>

>>>>>>> The key "BindToDHCPServer" i can not see on both of my 2003 SP2

>>>>>>> server and DHCP is working fine. So what is the problem your

>>>>>>> clients have? Is the server authorized in AD?

>>>>>>>

>>>>>>> Best regards

>>>>>>>

>>>>>>> Meinolf Weber

>>>>>>> Disclaimer: This posting is provided "AS IS" with no warranties,

>>>>>>> and

>>>>>>> confers

>>>>>>> no rights.

>>>>>>> ** Please do NOT email, only reply to Newsgroups

>>>>>>> ** HELP us help YOU!!!

>>>>>>> http://www.blakjak.demon.co.uk/mul_crss.htm

>>>>>>>> I have a server 2k3 R2 SP2 which is a DC and I cannot get the

>>>>>>>> DHCP

>>>>>>>> service to

>>>>>>>> bind to the IP address.

>>>>>>>> I have followed this post

>>>>>>>> http://www.winserverkb.com/Uwe/Forum.aspx/windows-server-sbs/45

>>>>>>>> 18

>>>>>>>> 9/D

>>>>>>>> HC

>>>>>>>> P-not-renewing-leases

>>>>>>>> which pretty much describes what is happening to me.

>>>>>>>> when I go to

>>>>>>>> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TCpip\Para

>>>>>>>> me

>>>>>>>> ter

>>>>>>>> \I

>>>>>>>> nterfa

>>>>>>>> ces\[NIC''s GUID]\BindToDHCPServer - this key 'bind to

>>>>>>>> DHCPServer'

>>>>>>>> does not

>>>>>>>> exist.

>>>>>>>> Although this is a Dell machine I do not have open manage

>>>>>>>> installed

>>>>>>>> on

>>>>>>>> this server.

>>>>>>>> I have stopped short of restarting the server with a clean boot

>>>>>>>> because I was wondering if the fact that the above registry key

>>>>>>>> is

>>>>>>>> missing points to something else.

Guest darkstar
Posted

Re: DHCP will not bind

 

Thats it!!!!

Meinolf, thank you very very much.

You've made my day

 

"Meinolf Weber" wrote:

> Hello darkstar,

>

> Check out this one:

> In WDS, expand Servers and right click on your server. Click Properties.

> Click the DHCP tab and check "Do not listen on port 67".

>

> Best regards

>

> Meinolf Weber

> Disclaimer: This posting is provided "AS IS" with no warranties, and confers

> no rights.

> ** Please do NOT email, only reply to Newsgroups

> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

>

>

> > It is WDS

> > udp 127.0.0.1 and 10.18.59.7 both listening on port 67

> > pidis 2152 which is svchost.exe WDSserver.

> > My test lab that I use at home before rolling something out at work

> > has WDS running together with DHCP. Do you think I should be looking

> > at WDS. I had a lot of trouble getting this to work so I am loath to

> > start messing around with it unless it really is the culprit

> >

> > "Meinolf Weber" wrote:

> >

> >> Hello darkstar,

> >>

> >> Check out this one:

> >> http://support.microsoft.com/kb/832689/en-us

> >> If you run "netstat -a -n -o" in a command prompt, check for port 67,

> >> normally used by DHCP Server, to see if another application/service

> >> is using it.

> >>

> >> Also, did you use the latest NIC drivers and did you try to reinstall

> >> them?

> >>

> >> Best regards

> >>

> >> Meinolf Weber

> >> Disclaimer: This posting is provided "AS IS" with no warranties, and

> >> confers

> >> no rights.

> >> ** Please do NOT email, only reply to Newsgroups

> >> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> >>> mmmmm

> >>> I have restarted and used selective startup - no system.ini, no

> >>> win.ini, no

> >>> startup items and all non microsoft services stopped.

> >>> I'm afraid there is no difference. DHCP still refuses to bind to the

> >>> NIC

> >>> "darkstar" wrote:

> >>>> True - I have not followed this step. I shall do this now!

> >>>>

> >>>> "Meinolf Weber" wrote:

> >>>>

> >>>>> Hello darkstar,

> >>>>>

> >>>>> What is about the step with msconfig described from Steven Zhu?

> >>>>> Did you follow it?

> >>>>>

> >>>>> Best regards

> >>>>>

> >>>>> Meinolf Weber

> >>>>> Disclaimer: This posting is provided "AS IS" with no warranties,

> >>>>> and

> >>>>> confers

> >>>>> no rights.

> >>>>> ** Please do NOT email, only reply to Newsgroups

> >>>>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> >>>>>> many thanks for your help.

> >>>>>>

> >>>>>> the dhcp server will not authenticate, I'm sure the reason is

> >>>>>> that

> >>>>>> when I go

> >>>>>> to the dhcp console and look at bindings in the advanced

> >>>>>> properties

> >>>>>> the NIC

> >>>>>> is listed but it is not ticked. If I tick the box to bind dhcp to

> >>>>>> the

> >>>>>> NIC the

> >>>>>> apply button is greyed out and the setting does not stick.

> >>>>>> I can click OK to exit out of the properties, but when I go back

> >>>>>> in

> >>>>>> the

> >>>>>> check box for the internal NIC remains unchecked.

> >>>>>> This means that it will not server dhcp clients

> >>>>>> "Meinolf Weber" wrote:

> >>>>>>> Hello darkstar_rising,

> >>>>>>>

> >>>>>>> The key "BindToDHCPServer" i can not see on both of my 2003 SP2

> >>>>>>> server and DHCP is working fine. So what is the problem your

> >>>>>>> clients have? Is the server authorized in AD?

> >>>>>>>

> >>>>>>> Best regards

> >>>>>>>

> >>>>>>> Meinolf Weber

> >>>>>>> Disclaimer: This posting is provided "AS IS" with no warranties,

> >>>>>>> and

> >>>>>>> confers

> >>>>>>> no rights.

> >>>>>>> ** Please do NOT email, only reply to Newsgroups

> >>>>>>> ** HELP us help YOU!!!

> >>>>>>> http://www.blakjak.demon.co.uk/mul_crss.htm

> >>>>>>>> I have a server 2k3 R2 SP2 which is a DC and I cannot get the

> >>>>>>>> DHCP

> >>>>>>>> service to

> >>>>>>>> bind to the IP address.

> >>>>>>>> I have followed this post

> >>>>>>>> http://www.winserverkb.com/Uwe/Forum.aspx/windows-server-sbs/45

> >>>>>>>> 18

> >>>>>>>> 9/D

> >>>>>>>> HC

> >>>>>>>> P-not-renewing-leases

> >>>>>>>> which pretty much describes what is happening to me.

> >>>>>>>> when I go to

> >>>>>>>> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TCpip\Para

> >>>>>>>> me

> >>>>>>>> ter

> >>>>>>>> \I

> >>>>>>>> nterfa

> >>>>>>>> ces\[NIC''s GUID]\BindToDHCPServer - this key 'bind to

> >>>>>>>> DHCPServer'

> >>>>>>>> does not

> >>>>>>>> exist.

> >>>>>>>> Although this is a Dell machine I do not have open manage

> >>>>>>>> installed

> >>>>>>>> on

> >>>>>>>> this server.

> >>>>>>>> I have stopped short of restarting the server with a clean boot

> >>>>>>>> because I was wondering if the fact that the above registry key

> >>>>>>>> is

> >>>>>>>> missing points to something else.

>

>

>

Guest Meinolf Weber
Posted

Re: DHCP will not bind

 

Hello darkstar,

 

You're welcome, glad to help.

 

Best regards

 

Meinolf Weber

Disclaimer: This posting is provided "AS IS" with no warranties, and confers

no rights.

** Please do NOT email, only reply to Newsgroups

** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

 

> Thats it!!!!

> Meinolf, thank you very very much.

> You've made my day

> "Meinolf Weber" wrote:

>

>> Hello darkstar,

>>

>> Check out this one:

>> In WDS, expand Servers and right click on your server. Click

>> Properties.

>> Click the DHCP tab and check "Do not listen on port 67".

>> Best regards

>>

>> Meinolf Weber

>> Disclaimer: This posting is provided "AS IS" with no warranties, and

>> confers

>> no rights.

>> ** Please do NOT email, only reply to Newsgroups

>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

>>> It is WDS

>>> udp 127.0.0.1 and 10.18.59.7 both listening on port 67

>>> pidis 2152 which is svchost.exe WDSserver.

>>> My test lab that I use at home before rolling something out at work

>>> has WDS running together with DHCP. Do you think I should be looking

>>> at WDS. I had a lot of trouble getting this to work so I am loath to

>>> start messing around with it unless it really is the culprit

>>> "Meinolf Weber" wrote:

>>>

>>>> Hello darkstar,

>>>>

>>>> Check out this one:

>>>> http://support.microsoft.com/kb/832689/en-us

>>>> If you run "netstat -a -n -o" in a command prompt, check for port

>>>> 67,

>>>> normally used by DHCP Server, to see if another application/service

>>>> is using it.

>>>> Also, did you use the latest NIC drivers and did you try to

>>>> reinstall them?

>>>>

>>>> Best regards

>>>>

>>>> Meinolf Weber

>>>> Disclaimer: This posting is provided "AS IS" with no warranties,

>>>> and

>>>> confers

>>>> no rights.

>>>> ** Please do NOT email, only reply to Newsgroups

>>>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

>>>>> mmmmm

>>>>> I have restarted and used selective startup - no system.ini, no

>>>>> win.ini, no

>>>>> startup items and all non microsoft services stopped.

>>>>> I'm afraid there is no difference. DHCP still refuses to bind to

>>>>> the

>>>>> NIC

>>>>> "darkstar" wrote:

>>>>>> True - I have not followed this step. I shall do this now!

>>>>>>

>>>>>> "Meinolf Weber" wrote:

>>>>>>

>>>>>>> Hello darkstar,

>>>>>>>

>>>>>>> What is about the step with msconfig described from Steven Zhu?

>>>>>>> Did you follow it?

>>>>>>>

>>>>>>> Best regards

>>>>>>>

>>>>>>> Meinolf Weber

>>>>>>> Disclaimer: This posting is provided "AS IS" with no warranties,

>>>>>>> and

>>>>>>> confers

>>>>>>> no rights.

>>>>>>> ** Please do NOT email, only reply to Newsgroups

>>>>>>> ** HELP us help YOU!!!

>>>>>>> http://www.blakjak.demon.co.uk/mul_crss.htm

>>>>>>>> many thanks for your help.

>>>>>>>>

>>>>>>>> the dhcp server will not authenticate, I'm sure the reason is

>>>>>>>> that

>>>>>>>> when I go

>>>>>>>> to the dhcp console and look at bindings in the advanced

>>>>>>>> properties

>>>>>>>> the NIC

>>>>>>>> is listed but it is not ticked. If I tick the box to bind dhcp

>>>>>>>> to

>>>>>>>> the

>>>>>>>> NIC the

>>>>>>>> apply button is greyed out and the setting does not stick.

>>>>>>>> I can click OK to exit out of the properties, but when I go

>>>>>>>> back

>>>>>>>> in

>>>>>>>> the

>>>>>>>> check box for the internal NIC remains unchecked.

>>>>>>>> This means that it will not server dhcp clients

>>>>>>>> "Meinolf Weber" wrote:

>>>>>>>>> Hello darkstar_rising,

>>>>>>>>>

>>>>>>>>> The key "BindToDHCPServer" i can not see on both of my 2003

>>>>>>>>> SP2 server and DHCP is working fine. So what is the problem

>>>>>>>>> your clients have? Is the server authorized in AD?

>>>>>>>>>

>>>>>>>>> Best regards

>>>>>>>>>

>>>>>>>>> Meinolf Weber

>>>>>>>>> Disclaimer: This posting is provided "AS IS" with no

>>>>>>>>> warranties,

>>>>>>>>> and

>>>>>>>>> confers

>>>>>>>>> no rights.

>>>>>>>>> ** Please do NOT email, only reply to Newsgroups

>>>>>>>>> ** HELP us help YOU!!!

>>>>>>>>> http://www.blakjak.demon.co.uk/mul_crss.htm

>>>>>>>>>> I have a server 2k3 R2 SP2 which is a DC and I cannot get the

>>>>>>>>>> DHCP

>>>>>>>>>> service to

>>>>>>>>>> bind to the IP address.

>>>>>>>>>> I have followed this post

>>>>>>>>>> http://www.winserverkb.com/Uwe/Forum.aspx/windows-server-sbs/

>>>>>>>>>> 45

>>>>>>>>>> 18

>>>>>>>>>> 9/D

>>>>>>>>>> HC

>>>>>>>>>> P-not-renewing-leases

>>>>>>>>>> which pretty much describes what is happening to me.

>>>>>>>>>> when I go to

>>>>>>>>>> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TCpip\Pa

>>>>>>>>>> ra

>>>>>>>>>> me

>>>>>>>>>> ter

>>>>>>>>>> \I

>>>>>>>>>> nterfa

>>>>>>>>>> ces\[NIC''s GUID]\BindToDHCPServer - this key 'bind to

>>>>>>>>>> DHCPServer'

>>>>>>>>>> does not

>>>>>>>>>> exist.

>>>>>>>>>> Although this is a Dell machine I do not have open manage

>>>>>>>>>> installed

>>>>>>>>>> on

>>>>>>>>>> this server.

>>>>>>>>>> I have stopped short of restarting the server with a clean

>>>>>>>>>> boot

>>>>>>>>>> because I was wondering if the fact that the above registry

>>>>>>>>>> key

>>>>>>>>>> is

>>>>>>>>>> missing points to something else.


×
×
  • Create New...