Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


Unable to Contact your DHCP Server

  • Please log in to reply
1 reply to this topic

#1 Exoleti


  • Members
  • 68 posts
  • Gender:Male
  • Location:New England
  • Local time:05:35 AM

Posted 30 July 2010 - 09:33 AM

After a BSOD incident which now appears to be remedied, my desktop cannot connect to the internet. I receive a pop-up "This connection has limited or no connectivity....." etc. When I perform start>run>cmd>ipconfig /release and then /renew, I receive the message "unable to contact your DHCP server". A laptop connect to the same router and modem is working just fine (I'm on it now). I have already done the following based on advise from other sites:

-confirmed my DNS Client is Started and set to Automatic
-confirmed my DHCP Client is Started and set to Automatic
-downloaded and performed both lspfix.exe and winsockxpfix.exe
-Reset TCP/IP with the netsh command and tried the netsh dump
-Confirmed I do not have a network bridge running
-disabled my 3rd party firewall
-reset my modem and router
-checked cables
-deleted & re-installed the NIC
-Start >> run >> services.msc >> DHCP client >>go to "Dependencies" and
checked for the following items:

AFD Networking Support environment
Net BIOS over TCP/IP
TCP/IP Protocol Driver
-Reset winsock in the command prompt using netsh winsock reset

I am running 32-bit XP with SP3. Please ask for any other details required to help me resolve this.

BC AdBot (Login to Remove)


#2 hamluis



  • Moderator
  • 56,299 posts
  • Gender:Male
  • Location:Killeen, TX
  • Local time:04:35 AM

Posted 30 July 2010 - 10:45 AM

I would try a different NIC...the trail seems to lead that way.

These are not expensive and should allow more definitive troubleshooting.


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users