The rogue server detection in Windows only works with other Windows DHCP servers, so it's not much help if someone hooks up an unauthorized router or Linux box.
One way to detect a rogue DHCP server is by using a packet sniffer. This allows you to analyze data moving across the network and look for DHCP traffic. Wireshark (formerly known as Ethereal) is a good free sniffer.
http://www.wireshark.org
Note that if you aren't the head network admin then be sure to get authorization to use this kind of tool ahead of time. They can be used for malicious purposes and you wouldn't want to get fired over a misunderstanding.
Main Topics
Browse All Topics





by: oBdAPosted on 2007-11-15 at 11:44:31ID: 20291750
A DHCP client will always take an offered DHCP address from the first DHCP server that answers.
You can only authorize a DHCP server running on Windows 2000 or later, and that only means that *this* *authorized* *server* will start to give out IP addresses. This is a Windows implementation only and will only keep a *Windows* DHCP server from starting in a domain.
This has nothing at all to do with non-Windows DHCP servers. Any DHCP server plugged into a network will be handing out IP addresses if the client accepts it. There is no way to prevent that.
The way to solve it: look at the address of the DHCP server on a client that has a bad address, ping it, check the local ARP table for the MAC address of the DHCP server. Then check the ports on your switch(es) for this address.
You might want to check the rogue server's MAC address for the vendor as well, could help to determine what you're looking for (in your case, it would have helped immensely, because you would have identified the DHCP server as being VMWare immediately).