Microsoft DHCP

Thu 15 December 2005

Filed under OS

Tags Lamer Moments

It all starts with an innocent user.... "Hey, I can't see the Internet". "Oh, wow, I can't see email." "Oh, actually I can't work on files." (I can't help but notice the progression here: Oh, the Internet is down, I guess I'll send some email. Wait, that's broken too, I'll have to do some work.)

Ten minutes later, you are on the DHCP Servers doorstep, being thouroughly convinced that there are no workstation ills afoot.

You have to love errors like this:

The DHCP service is not servicing
any clients because none of the
active network interfaces have
statically configured IP addresses,
or there are no active interfaces.

For more information, see Help and
Support Center at
http://go.microsoft.com/fwlink/events.asp.

So naturally the admin launches himself into the standard fare of troubleshooting.

  • Duh! The server has static IPs, another fruitful error message from Microsoft.
  • Will a reboot fix it? no
  • DHCP Database Corruption? no
  • Will a reboot fix it? no
  • DHCP Errors with static IPs? no
  • Will a reboot fix it? no
  • Switch related ? no
  • Will a reboot fix it? no
  • Will a reboot fix it? no
  • The Reboot DIDN'T fix it? no
  • A Reboot must do it, it's Windows... no

The solution is priceless. The problem is a farking DELL MANAGEMENT DRIVER. [WTF, how does this even BIND port 67? But, I digress] Netstat to the rescue. (Another aside: Where is the GUI utility that should ship with Windows and show you anything at all about IP sessions on your local box?)

netstat -a -b -n > ipdetails.txtstart notepad ipdetails.txt

Then we searched for ':67'. Low and behold the offending process (beginning with oam....) We disabled all of the Dell Managment services, and rebooted. DHCP comes up without a flaw. image0

Judgement: LAME


Comments


Up To Something © Joshua M Schmidlkofer Powered by Pelican and Twitter Bootstrap. Icons by Font Awesome and Font Awesome More