Coming Soon: GET:IT Endpoint Management 1-Day Conference on September 28th at 9:30 AM ET Coming Soon: GET:IT Endpoint Management 1-Day Conference on September 28th at 9:30 AM ET

Bad_address

Viewing 1 post (of 1 total)
  • Author
    Posts

  • spn
    Member
    #167668

    hi,

    Lately, i have been having these BAD_ADDRESS(es) on our DHCP server and i am not sure what triggers it to happen. i dont know if it is something wrong with our dhcp or else. For this problem, if i reserved an IP address for this device then it would go away for a couple of weeks then it would start again on a different machine. Let me know if you ever ran into this problem before. I really appreciate your time. TIA.

    In the Address Leases on the DHCP, the unique id for these BAD_ADDRESS(es) are showing something like this ‘6701a8c0’. it is not a valid MAC address.
    The sequence of request and update is really confusing me. The ip addresses on the BAD_ADDRESS lines are not pingable and no device in our network had those IPs during this time.

    here is a piece of the dhcp log.


    24,08/27/18,02:25:33,Database Cleanup Begin,,,,,0,6,,,,,,,,,0
    25,08/27/18,02:25:33,0 leases expired and 0 leases deleted,,,,,0,6,,,,,,,,,0
    25,08/27/18,02:25:33,0 leases expired and 0 leases deleted,,,,,0,6,,,,,,,,,0
    30,08/27/18,02:25:39,DNS Update Request,192.168.1.103,CONFPC.DOMAINNAME.com,,,0,6, ,,,,,,,,0
    10,08/27/18,02:25:39,Assign,192.168.1.103,CONFPC.DOMAINNAME .com,PC-MACADDRESS,,122985220,0,,,,0x4D53465420352E30,MSFT 5.0,,,,0
    32,08/27/18,02:25:39,DNS Update Successful,192.168.1.103,CONFPC.DOMAINNAME.com,,,0 ,6,,,,,,,,,0
    30,08/27/18,02:25:39,DNS Update Request,192.168.1.103,CONFPC,DOMAINNAME.com,,,0,6, ,,,,,,,,0
    13,08/27/18,02:25:39,Conflict,192.168.1.103,BAD_ADDRESS,,,0 ,6,,,,,,,,,0
    32,08/27/18,02:25:39,DNS Update Successful,192.168.1.103,CONFPC.DOMAINNAME.com,,,0 ,6,,,,,,,,,0
    30,08/27/18,02:25:52,DNS Update Request,192.168.1.104,CONFPC.DOMAINNAME.com,,,0,6, ,,,,,,,,0
    10,08/27/18,02:25:52,Assign,192.168.1.104,CONFPC.DOMAINNAME .com,PC-MACADDRESS,,641243928,0,,,,0x4D53465420352E30,MSFT 5.0,,,,0
    32,08/27/18,02:25:53,DNS Update Successful,192.168.1.104,CONFPC.DOMAINNAME.com,,,0 ,6,,,,,,,,,0
    30,08/27/18,02:26:09,DNS Update Request,192.168.1.104,CONFPC.DOMAINNAME.com,,,0,6, ,,,,,,,,0
    13,08/27/18,02:26:09,Conflict,192.168.1.104,BAD_ADDRESS,,,0 ,6,,,,,,,,,0
    32,08/27/18,02:26:09,DNS Update Successful,192.168.1.104,CONFPC.DOMAINNAME.com,,,0 ,6,,,,,,,,,0
    30,08/27/18,02:26:19,DNS Update Request,192.168.1.107,CONFPC.DOMAINNAME.com,,,0,6, ,,,,,,,,0
    10,08/27/18,02:26:19,Assign,192.168.1.107,CONFPC.DOMAINNAME .com,PC-MACADDRESS,,2953808784,0,,,,0x4D53465420352E30,MSF T 5.0,,,,0
    32,08/27/18,02:26:20,DNS Update Successful,192.168.1.107,CONFPC.DOMAINNAME.com,,,0 ,6,,,,,,,,,0
    24,08/27/18,02:30:35,Database Cleanup Begin,,,,,0,6,,,,,,,,,0
    25,08/27/18,02:30:35,0 leases expired and 0 leases deleted,,,,,0,6,,,,,,,,,0
    …..

    DOMAINNAME: our network domain name
    The above sequence is from one pc (CONFPC).
    OS: Windows Server 2012 R2

    Thanks again.

Viewing 1 post (of 1 total)

You must be logged in to reply to this topic.

Live Webinar: Active Directory Security: What Needs Immediate Priority!Live on Tuesday, October 12th at 1 PM ET

Attacks on Active Directory are at an all-time high. Companies that are not taking heed are being punished, both monetarily and with loss of production.

In this webinar, you will learn:

  • How to prioritize vulnerability management
  • What attackers are leveraging to breach organizations
  • Where Active Directory security needs immediate attention
  • Overall strategy to secure your environment and keep it secured

Sponsored by: