Thu, 08 Jul 2004
Hunting a Rogue DHCP Server
posted by Chip Witt
As much as I hate the effects, I have to admit that I love the challenges presented when a user places a piece of unauthorized equipment on one of my networks. Only under this kind of pressure does one get to stretch the legs, and refine the hunting techniques.
About a week ago my team was presented with several symptoms that indicated we had a rogue DHCP (Dynamic Host Control Protocol, for assigning IP addresses to hosts on a network dynamically) server somewhere in the enterprise. New machines, and laptop users were getting bad network configuration information, and our RAS services customers began complaining that they could not connect to resources on the network after successfully authenticating. That, in a word, sucked. I began my hunt for the naughty piece of equipment with the tools I had at my immediate disposal.
- conferences-training
- cool_software
- good_books
- hey_mr_DJ
- laugh_lest_we_cry
- stayin_active
- tech_tips
- the_new_unix
- thinking_outloud
- whatznew
"Each blog is like a fireplace, and each post is like a log heaved on top to keep the fire burning. Every post has its own ¨permalink¨, so others can point directly to it. As long as a blog puts out heat and light, others who care about the author's subject are drawn to it. So are Google and other search engines, which sift constantly through the ashes".
Doc Searls
and David Sifry,
Linux Journal
| Last Modified: 05 May 2009 21:38 by wittzend.com |
© 2006 - 2009 Witt'z End Technologies. All rights reserved. |
Powered by Vim |