Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

What's the best approach towards determining if I have a rogue DHCP server inside my network?

I'm wondering how most admins approach these kinds of problems. I found DHCP Probe through searching, and thought about trying it out. Has anyone had experience with it? (I would like to know before taking the time to compile it and install).

Do you know any useful tools or best-practices towards finding rogue DHCP servers?

share|improve this question
MS Tool and very simple to use! Rogue DHCP Server detection -… – aa.malta Nov 8 '13 at 10:38
I found an official reference to your link aa.malta at… but the link no longer appears to work as of 2016. It shows me blog posts from 2009, but I only see posts for July 6 and June 29. There doesn't seem to be a July 3 post as indicated by the link URL you posted. Looks like MS removed it for who knows what reason. – Daniel Jan 24 at 17:59
Looks like this direct link (which I found on a wordpress site) works to download the file from a Microsoft Server. Link is working as of January 2016. Since the URL is Microsoft, I feel it can be trusted, but I make no guarantees:… – Daniel Jan 24 at 18:04

11 Answers 11

up vote 47 down vote accepted

One simple method is to simply run a sniffer like tcpdump/wireshark on a computer and send out a DHCP request. If you see any offers other then from your real DHCP server then you know you have a problem.

share|improve this answer
Helps using the following filter: "bootp.type == 2" (for only showing DHCP offers, and seeing if there is response from different/unknown sources) – l0c0b0x Jun 16 '09 at 20:13
Use a program like DHCP-Find (…) in conjunction with TCPDump/Wireshark to trigger DHCP responses. – saluce May 19 '12 at 15:03

To recap and add to some of the other answers:

Temporarily disable your production DHCP server and see if other servers respond.

You can get the IP address of the server by running ipconfig /all on a windows machine, and then you can get the MAC address by looking for that IP address using arp -a.

On a Mac, run ipconfig getpacket en0 (or en1). See

The DHCP server information is usually in /var/log/messages. sudo grep -i dhcp /var/log/messages*

Disabling your production DHCP server might not be a good option, of course.

Use a tool that specifically looks for rogue DHCP servers

See for a list of tools (many of which were listed in other responses).

Configure switches to block DHCP offers

Most managed switches can be configured to prevent rogue DHCP servers:

share|improve this answer

The Wireshark / DHCP explorer / DHCP Probe approaches are good for a one time or periodic check. However, I'd recommend looking into DHCP Snooping support on your network. This feature will provide constant protection from rogue DHCP servers on the network, and is supported by many different hardware vendors.

Here's the feature set as indicated in the Cisco docs.

• Validates DHCP messages received from untrusted sources and filters out invalid messages.

• Rate-limits DHCP traffic from trusted and untrusted sources.

• Builds and maintains the DHCP snooping binding database, which contains information about untrusted hosts with leased IP addresses.

• Utilizes the DHCP snooping binding database to validate subsequent requests from untrusted hosts.

share|improve this answer
Juniper's DHCP Snooping doc:… ProCurve's DHCP Snooping:… – sparks May 15 '09 at 14:25

dhcpdump, which takes input form tcpdump and shows only DHCP related packets. Helped me find rootkited Windows, posing as fake DHCP in our LAN.

share|improve this answer

dhcploc.exe is the quickest and handiest way on Windows systems. It is available in the XP Support Tools. The Support Tools are on every OEM/retail XP disk, but may or may not be on "recovery disks" provided by some OEMs. You can also download them from MS.

It's a simple commandline tool. You run dhcploc {yourIPaddress} and then press the 'd' key to do a fake discovery. If you leave it running without pressing any keys, it will display every DHCP request and answer it hears. Press 'q' to quit.

share|improve this answer
Just used this in combination with killing individual switch ports to track down a sneaky rogue server we were dealing with. Good stuff! – DHayes Sep 10 '10 at 15:44
You can still use DHCPloc.exe on Windows 7: 1. Download "Windows XP Service Pack 2 Support Tools" from [here][1]. 2. Right-click on the executable and select Properties->Compatibility then turn on Compatibility Mode and set it to "Windows XP (Service Pack 3)". 3. Install as normal. DHCPLoc.exe works fine on my Win7 x64 installation. [1]: – parsley72 Apr 29 '12 at 23:24

Scapy is a python based packet crafting tool that is good for these sort tasks. There is an example of how to do exactly this here.

share|improve this answer
Wow, I find Scapy is so powerful after delving into it for several days. It surpasses the crappy tools like dhcpfind.exe and dhcploc.exe. Scapy 2.2 can run on Linux and Windows -- I tried both. The only barrier is you HAVE TO know Python programming language to quite some extent to harness its power. – Jimm Chen May 21 '13 at 1:35
The link you posted is broken – Jason S Feb 10 '15 at 20:46
@JasonS Hi I've updated the link, but the changing is pending peer review... While waiting you can find it here: – Huygens Aug 14 '15 at 16:06

once you've established that there's a rogue dhcp server on the network I found the quickest way to resolve it was...

Send an email round to the whole company saying:

"which one of you has added a wireless router into the LAN, you've killed the internet for everyone else"

expect a sheepish response, or the conflicting device to disappear, quickly :)

share|improve this answer

To expand on l0c0b0x's comment about using bootp.type == 2 as a filter. The bootp.type filter is only available in Wireshark/tshark. It is not available in tcpdump which the contextual location of his comment inclined me to believe.

Tshark works perfectly for this.

We have our network divided up into numerous broadcast domains, each with their own Linux-based probe with a point of presence on the "local" broadcast domain and on an administrative subnet in one fashion or another. Tshark combined with ClusterSSH allows me to easily look for DHCP traffic or (anything else for that matter) on the further flung corners of the network.

This will find DHCP replies using Linux:

# ifconfig ethX promisc
# tshark -i ethX -n port 68 -R 'bootp.type == 2'
share|improve this answer

Disable the main DHCP server and (re)configure a connection.

If you get an IP address, you've got a rogue.

If you have a Linux handy, the standard dhcpclient tells you the IP address of the DHCP server (else you can sniff the traffic to see where the DHCP response came from).

share|improve this answer
While this would of course work, stopping a production DHCP server is probably not the best approach if you are actually concerned about providing the service... – Massimo Feb 14 '12 at 11:04
Depends on the amount of people you are serving. You can disrupt the service for a couple of minutes in most cases and nobody will notice, especially in the middle of the day when most people have their lease already. – Vinko Vrsalovic Feb 16 '12 at 11:44

There are several ways, if your running a small network the simplest way is to turn off / disable / un-plug your dhcp server and then run ipconfig /renew or similar on a client and if you obtain and IP you have something rougue on your network.

Another way would be to use Wireshark packet capturer/analyser to look at your network traffic and find DHCP connections, there is a lab worksheet on how do do this avaliable from here.

There are also a number of utilies avaliable which proport to do this one is DHCP explorer another is DHCP probe which you mentioned in your original post.

share|improve this answer

You could do a ping sweep of your networks and then compare that to the number of DHCP leases handed out by your DHCP server.

You need to have a general idea of the number of static devices (router interfaces and printers perhaps) which will skew this number slightly, but this should be a quick and accurate way of identifying them across multiple networks.

share|improve this answer

protected by Chris S Nov 8 '13 at 14:22

Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).

Would you like to answer one of these unanswered questions instead?

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