DHCP Causes CPU Spikes

  • Thread starter Thread starter MGB
  • Start date Start date
M

MGB

Hi again,

I posted yesterday with a problem that my CPU Usage spiked
every few minutes and I had tried uninstalling a MS fix,
which didn't do the trick.

Well, I have found the root of my problem after hours of
searching knowledge bases and forums and speaking to a few
colleagues at work, but now I need to find a fix to the
problem;

I had recently bought a D-Link ADSL Router and set it up
and configured it and all was well and good.

Except for the CPU spiking!

Through a process of elimination I have now discovered
that it was my DHCP Service which was causing the spike. I
stop the process, I have no problem with hanging PC's
except then I cannot access the Internet.

Anyone know a workaround for this?

Many thanks...
 
Is the DHCP service required on your network? It sounds like the ADSL
router could do the job for your computer. Shut the service down if it
isn't needed.
 
Thanks for the reply Gerry. I tried shutting the service
down on my PC but when I do that I cannot then access the
Internet.
I have found that not only is it the DHCP Client, but also
the DNS Client.

Should I stop this on my router settings and just let the
PC do the work? (I only have 1 home use PC but bought the
router/firewall as extra protection)
 
Are you running Win2k server or pro? On my pro box, DHCP service isn't
available -- and you don't want to turn off either the dhcp client or dns
client. On my server box, all 3 are seperate, and can be turned off
individually.
 
Hey,

I'm running Win 2000 Pro, jst as a normal OS for my PC. I
tried re-assigning the IP addresses, masks, gateways and
DNS and switched DHCP off on my router, but then couldn't
access the Internet.

Didn't get any support from D-Link either (well not much
anyway!!)

Confused!!!
 
OK, try this...

Set a fixzed IP on the Pro box, using an unused IP in your DHCP scope. If I
remember how a d-link works with NAT, then I'd guess that an available IP
address is somewhere between 192.168.100.2 and 100.25. Make sure that NAT
is turned on, but local DHCP is turned off.

Set your netmask to 255.255.255.0

Set your default gateway and primary DNS to 192.168.100.1.

Make sure that the d-link either has been assigned an IP, netmask, gateway,
and primary dns by the ISP's DHCP server, or you have assigned manually
based on what they have told you to set.
 
Back
Top