Constant "Acquiring Network Address" status; No IP address from DH

Discussion in 'Windows Networking' started by Masitpro_mcse, Aug 25, 2007.

  1. Have a station in the domain that is unable to obtain an IP address from the
    Standard 2003 DHCP server. Tried variuos methods to solve by:

    Restarting DHCP Server - Checked Logs - Reserved IP Scope - IPConfig
    /flushdns - netsh - arp - DLSFix (Winsock) - reinstalling driver - regedit,
    etc.,

    The weird thing is it will pick up IP on a local consumer router, another
    DHCP server on a differnet segment or a created VLAN.

    Thinking is there something I missed in the domain where it is blocking this
    particular mac address somewhere? Unable to detect this problem. Please clear
    the air for me!
     
    Masitpro_mcse, Aug 25, 2007
    #1
    1. Advertisements

  2. Hello,

    did you try changing the network cable or switch port ?
     
    Mathieu CHATEAU, Aug 25, 2007
    #2
    1. Advertisements

  3. That was the first steps that were done to troubleshoot this problem. As
    mentioned previously this station (notebook pc) can pick up DHCP from another
    segment or consumer router but not from this particular DHCP server on our
    domain. There must be something blocking it or a registry entry on the
    notebook that is preventing it from acquiring an IP address.
     
    Masitpro_mcse, Aug 27, 2007
    #3
  4. Hello,

    is DHCP audit logging enabled (from the DHCP MMC, right click server name,
    properties checkbox)?
    If so, go to :
    C:\WINDOWS\System32\Dhcp
    And check logs

    Else activate it, try to get a lease and check logs
     
    Mathieu CHATEAU, Aug 27, 2007
    #4
  5. Here is what is generated in the log file:

    30,08/27/07,09:15:35,DNS Update
    request,117.62.168.192,MOXACOM41.abc.domain.com,,
    11,08/27/07,09:15:35,Renew,192.168.62.117,MOXACOM41.abc.domain.com,00400504F59A,
    30,08/27/07,09:15:35,DNS Update
    Request,117.62.168.192,MOXACOM41.abc.domain.com,,
    11,08/27/07,09:15:35,Renew,192.168.62.117,MOXACOM41.abc.domain.com,00400504F59A,
    31,08/27/07,09:15:36,DNS Update
    Failed,192.168.62.117,MOXACOM41.abc.domain.com,-1,
    31,08/27/07,09:15:36,DNS Update
    Failed,192.168.62.117,MOXACOM41.abc.domain.com,-1,
    15,08/27/07,09:16:15,NACK,192.168.62.188,MOXACOM41.abc.domain.com,001560B73C90,

    The DHCP server is denying a lease to mac address 001560B73C90 - Also is
    denying lease to mac address 00400504F59A, which is a PCMCIA card I also used
    to identify if there was a problem with the integrated NIC. DNS Update
    Failed; What to do next from here?
     
    Masitpro_mcse, Aug 28, 2007
    #5
  6. Hello,

    DNS update may file if there is a dns ownership issue. You may delete the
    dns IN A entry and try again.

    You may read this KB, starting at Use the DnsUpdateProxy security group:

    How to configure DNS dynamic updates in Windows Server 2003
    http://support.microsoft.com/kb/816592/en-us


    --
    Cordialement,
    Mathieu CHATEAU
    http://lordoftheping.blogspot.com


     
    Mathieu CHATEAU, Aug 28, 2007
    #6
  7. Unjoined the domain using a PCMCIA nic and renamed the computer. Still had to
    use PCMCIA nic to rejoin domain, then deleted old DNS entries and tried
    again. All settings described in KB816592 you sent are implemented to a tee.
    Still not acquiring IP address, so decided to create reservation and got
    error "The specified IP address or hardware address is being used by another
    client" or get this message "An error occurred while accessing the DHCP
    database. Look at the DHCP server event log for more info on this error"
    Something is causing a decline to IP but what is it? Nothing in the logs show
    any errors and there is no DHCP server event log! Frustration settling
    in............???!
     
    Masitpro_mcse, Aug 29, 2007
    #7
  8. Finally solved the DHCP IP addressing in the onboard ether port. Checked log
    and discovered that DHCP was trying to distribute IP address out of the scope
    range. It was attempting at the same time to distibute an IP address marked
    as reserved. Temporarily deleted the reserved IP and then the computer
    connected! Recreated reserved IP record and all is fine now.
     
    Masitpro_mcse, Aug 30, 2007
    #8
  9. great!
     
    Mathieu CHATEAU, Aug 30, 2007
    #9
  10. Masitpro_mcse

    dolev pony Guest

    Thanks
    work for me

    i just restarted the DHCP client service and done !
    (it was manualy stoped)


    regards
    Dolev
     
    dolev pony, Nov 13, 2011
    #10
  11. Masitpro_mcse

    Pickenser

    Joined:
    Mar 16, 2012
    Messages:
    2
    Likes Received:
    0
    They were the first steps to this problem have been made​​. as
    mentions this station (notebook pc) can pick up another DHCP
    Segment or consumer router but not to that particular DHCP server of our
    Domain. There must be something blocking or a registry entry to the
    Laptop, which is essential to avoid the purchase of an IP address.
     
    Pickenser, Apr 11, 2012
    #11
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.