E Fernandez
asked on
The BAD_ADDRESS
The BAD_ADDRESS leases on dhcp server. Does this mean that he have a duplicate ip address somewhere?
What type of DHCP server? Windows Server, router, firewall, Cisco box ... and what is the complete, specific error message?
BAD_ADDRESS typically means that the DHCP server attempted to lease that address to a client but determined that something on the network is already using the address. It creates a BAD_ADDRESS record so that it won't keep attempting to assign an address that's already in use.
ASKER
I have a windows server 2016 dhcp server .
Log Name: System
Source: Microsoft-Windows-DHCP-Ser ver
Date: 10/5/2018 12:12:37 PM
Event ID: 1063
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: LESD1.lesd.us
Description:
There are no IP addresses available for lease in the scope or superscope "lesdla".
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-DH CP-Server" Guid="{6D64F02C-A125-4DAC- 9A01-F0555 B41CA84}" EventSourceName="DhcpServe r" />
<EventID Qualifiers="0">1063</Event ID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000 </Keywords >
<TimeCreated SystemTime="2018-10-05T19: 12:37.0000 00000Z" />
<EventRecordID>265244</Eve ntRecordID >
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>LESD1.lesd.us</C omputer>
<Security />
</System>
<EventData>
<Data>lesdla</Data>
</EventData>
</Event>
it just runs out of leases.
ESther
Log Name: System
Source: Microsoft-Windows-DHCP-Ser
Date: 10/5/2018 12:12:37 PM
Event ID: 1063
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: LESD1.lesd.us
Description:
There are no IP addresses available for lease in the scope or superscope "lesdla".
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-DH
<EventID Qualifiers="0">1063</Event
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000
<TimeCreated SystemTime="2018-10-05T19:
<EventRecordID>265244</Eve
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>LESD1.lesd.us</C
<Security />
</System>
<EventData>
<Data>lesdla</Data>
</EventData>
</Event>
it just runs out of leases.
ESther
If you look at the active leases in the DHCP console, is it completely full of BAD_ADDRESS entries?
ASKER
no ther are probably like 300 or so.
This may be caused by a malfunctioning device on the network. Do the BAD_ADDRESS entries have legitimate MAC addresses associated with them? If not, check the DHCP logs (at C:\Windows\System32\dhcp), which should show the actual MAC addresses. If all of the applicable log entries show a single MAC address, see if you can determine what device it belongs to. This MAC Address Lookup site may help, as it should at least be able to identify the manufacturer.
ASKER
31,10/08/18,00:00:34,DNS Update Failed,10.10.29.134,DELLOP TRM09A.les d.us,,,0,6 ,,,,,,,,,2
I see allot of these.
I see allot of these.
Sorry for the delay. Are you saying that you're seeing a lot of log entries referencing that particular device (DELLOPTRM09A.lesd.us), or just a lot of those events referencing different devices on your network?
Also, have you checked to see whether you've got another DHCP server handing out addresses on the same network?
Also, have you checked to see whether you've got another DHCP server handing out addresses on the same network?
ASKER
No, not that particular device just allot or dns update failed ones.
In that case, I don't think those "DNS update failed" log entries are related to the BAD_ADDRESS records in the DHCP database.
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.