How can I scan for any statically configured IP addresses in use, within a Windows Server DHCP scope, of which the DHCP server is not aware?

I'm dealing with a network I inherited on which I found devices configured with a static IP within the DHCP server scope (without a matching configured reservation). DHCP leases for new (or clients roaming between VLAN's) within this scope sometimes take a long time to register. Also WiFi clients sometimes get configured with an APIPA address.

I want to rule out faulty static IP configurations within the IPV4 scope being the cause of this.


Develop an IP Address Management strategy. Resource this project by getting people and IPAM tools to accurately track your address space.

The implementation is up to you. You know your environment, and we don't recommend products.

Yes, it will be very tedious to clean up by correlating traffic on the wire, DHCP, DNS, host static config, and an IPAM database. Impose discipline now to at least not make it worse.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.