> Any network engineer worth his salt better be able to locate one > extremely quickly, and cut it from the network, until the one in charge > of the rogue box has disabled it. After all, it isn't that difficult to > chase a cable from the port in question on the switch to the box running > the rogue DHCP server. >
A little bit off topic, but bear with me here. Would a packet sniff on the network reveal the rogue dhcp server by inspecting from what IP address the DHCPOFFER packets are coming from? If you've got two servers, you'll know which one is yours, so the other would have to be the offending server. Jake Adams -------------------- BYU Unix Users Group http://uug.byu.edu/ The opinions expressed in this message are the responsibility of their author. They are not endorsed by BYU, the BYU CS Department or BYU-UUG. ___________________________________________________________________ List Info (unsubscribe here): http://uug.byu.edu/mailman/listinfo/uug-list
