Server 2003 R2 is not renewing its DHCP address when rebooting

I'm running some server 2003 which are build up with an automatic routine
from PXE boot. After OS deployment and application installation they start up
as domain members, everything works fine, but since R2 they do not renew
their dhcp lease when starting up and do not update their DNS records which
is needed. Only one warning is logged:

Event Type: Warning
Event Source: Dhcp
Event Category: None
Event ID: 1003
Date: 6/13/2007
Time: 5:07:21 PM
User: N/A
Computer: S836813
Description:
Your computer was not able to renew its address from the network (from the
DHCP Server) for the Network Card with network address 0015C7DAB3BF. The
following error occurred:
The semaphore timeout period has expired. . Your computer will continue to
try and obtain an address on its own from the network address (DHCP) server.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 79 00 00 00 y...

Other 2003 servers pre R2 update their leases und dns records. And a manual
ipconfig /renew or restart of the DHCP client does the update at the R2
servers.

Any idea?

Hello Chris,

Maybe this helps you even it is older:
http://support.microsoft.com/default...;en-us;Q168455

or this:
http://www.eventid.net/display.asp?e...e=DHCP&phase=1

I would prefer for servers, always use fixed IP configuration.

Best regards

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

> I'm running some server 2003 which are build up with an automatic
> routine from PXE boot. After OS deployment and application
> installation they start up as domain members, everything works fine,
> but since R2 they do not renew their dhcp lease when starting up and
> do not update their DNS records which is needed. Only one warning is
> logged:
>
> Event Type: Warning
> Event Source: Dhcp
> Event Category: None
> Event ID: 1003
> Date: 6/13/2007
> Time: 5:07:21 PM
> User: N/A
> Computer: S836813
> Description:
> Your computer was not able to renew its address from the network (from
> the
> DHCP Server) for the Network Card with network address 0015C7DAB3BF.
> The
> following error occurred:
> The semaphore timeout period has expired. . Your computer will
> continue to
> try and obtain an address on its own from the network address (DHCP)
> server.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 79 00 00 00 y...
> Other 2003 servers pre R2 update their leases und dns records. And a
> manual ipconfig /renew or restart of the DHCP client does the update
> at the R2 servers.
>
> Any idea?
>

Thanks Myweb,

I also found this eventid articel but the Q168455 is a good one to take it
with me when I go to the network guys.

Regards,

Chris


"Myweb" wrote:

> Hello Chris,
>
> Maybe this helps you even it is older:
> http://support.microsoft.com/default...;en-us;Q168455
>
> or this:
> http://www.eventid.net/display.asp?e...e=DHCP&phase=1
>
> I would prefer for servers, always use fixed IP configuration.
>
> Best regards
>
> Myweb
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
>
> > I'm running some server 2003 which are build up with an automatic
> > routine from PXE boot. After OS deployment and application
> > installation they start up as domain members, everything works fine,
> > but since R2 they do not renew their dhcp lease when starting up and
> > do not update their DNS records which is needed. Only one warning is
> > logged:
> >
> > Event Type: Warning
> > Event Source: Dhcp
> > Event Category: None
> > Event ID: 1003
> > Date: 6/13/2007
> > Time: 5:07:21 PM
> > User: N/A
> > Computer: S836813
> > Description:
> > Your computer was not able to renew its address from the network (from
> > the
> > DHCP Server) for the Network Card with network address 0015C7DAB3BF.
> > The
> > following error occurred:
> > The semaphore timeout period has expired. . Your computer will
> > continue to
> > try and obtain an address on its own from the network address (DHCP)
> > server.
> > For more information, see Help and Support Center at
> > http://go.microsoft.com/fwlink/events.asp.
> > Data:
> > 0000: 79 00 00 00 y...
> > Other 2003 servers pre R2 update their leases und dns records. And a
> > manual ipconfig /renew or restart of the DHCP client does the update
> > at the R2 servers.
> >
> > Any idea?
> >
>
>
>