DHCP BINDING-ACK message

One of my domain controllers (Windows Server 2012 R2 Standard) is logging the following event to event viewer every 5 minutes:

A BINDING-ACK message with transaction id: 1234 was sent for IP address: x.x.x.x with reject reason: (Illegal IP address (not part of any address pool)) to partner server: server1.domain.local for failover relationship: server1.domain.local-server2.domain.local.
The event ID listed is 20291.  It's the same IP address in every event but I'm not sure why.  That IP isn't in use and isn't showing up in DNS at all.  I have found the following:
and although the event ID matches what is being discussed, neither of the two issues listed make sense in my environment.  I don't have any reservations set, and these servers were not migrated.  

I also found this:  
but the reject reasons listed are different from mine so I'm not sure if the hotfix still applies or not.  

Any suggestions on how to fix this error?
fallriverelectricAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

nociSoftware EngineerCommented:
appearantly you have a m that want to use ip addres x.x.x.x, the problem is that x.x.x.x is not known on the DHCP server.
That's why you see the reject. after a reject the system needs to ask for a valid address, not attempt the wrong request again.

so you need to identify the system that does it wrong... Now the MAC adress of the requester can be traced by looking at the MAC/CAM address tables on your switches (if you have managed switches that is). And identify on which port the culprit lives.
fallriverelectricAuthor Commented:
If the device is wanting to use that IP address would that mean it's been statically assigned to it?  Because we allow static IPs on the network so why would I get a reject message for this device but no others that are statically assigned?  I checked the arp tables on the switch but don't see anything with that address listed at all.
nociSoftware EngineerCommented:
Depends, if it is a static assignment on the system itself, it will not do a DHCP request.
So the system should be setup as DHCP. to do a request.
It can be a static assignment on the DHCP server, in that case the address is known to the server.

Is it possible there are multiple DHCP servers active?

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
fallriverelectricAuthor Commented:
I'm wondering if it's an issue with failover.  We do have 2 DHCP servers set up, one as primary and one as hot standby.  The address in question is part of the scope on server 1, but not on server 2.  (the one with the error)  How does that happen?  Should those scopes match exactly?  Because I'm not sure why they don't.
fallriverelectricAuthor Commented:
DHCP failover needed to be reconfigured.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
DHCP

From novice to tech pro — start learning today.