Super User is a question and answer site for computer enthusiasts and power users. It only takes a minute to sign up.
Sign up to join this community
My PC is running Windows 10 64 bit. I don't know why it is not getting an IP address from the DHCP server; I am sure it's a configuration problem. It is getting an IP like 169.…
Here is what I have tried:
To check whether it a hardware issue, I booted Ubuntu and it worked perfectly.
In Windows, when I assign static IP in DHCP range, it works. But it does not get IP automatically from DHCP. ipconfig /renew shows DHCP connection timed out.
I found this error in some Intel 82579DM network adapters, and I solved restarting DHCP Client service with an administrative prompt:
net stop dhcp
net start dhcp
Or with the services.msc interface.
Restarting DHCP Client from services solved my problem.
I know this is old but it happened to me today after we changed our router (SSID stayed the same).
My advice before going through a ton of troubleshooting steps is to delete your network in ‘manage known networks’ and then reconnect.
I went through all the tips from the answers here but none worked. I then assigned an IP address within my routers range and my computer connected to the internet fine but I noticed my home network had a ‘2’ at the end of it when connected even though that is not what my router broadcasts
Seeing this I then Deleted my SSID’s in ‘manage known networks’ once this was done I re-connected to the network absolutely fine with no issues and DHCP picked up an IP address fine.
I foun this error from 2016-12-07 on. Detected on Lenovo M90 with Intel 82578DM adapter. Fastest solution was to set fixed IP on adapter. The solution with alternate configuration didn't work.
Somehow the command "net stop dhcp" followed by "shutdown /r /f /t 0" and doing almost all the stuff described at "https://support.microsoft.com/en-us/help/10741/windows-10-fix-network-connection-issues" fixed the problem for me. I don't understand how and why. I didn't understood how the problem occurred neither but this is another story. Thanks for the help everyone.
Encountered the same on a computer I was called to. Turned out that the driver for the network card (realtek 8168) wasn't installed. Windows 10 did recognize the card, but never fully initialized it. So look up the brand and type of the network chip on the motherboard and download & install it.
Solution: Enable "DHCP Client" in "Services". That's it. Mine was set to "disabled". Remember that this is not "DHCP Server". You are not switching your PC to serve IP's. You are setting it up to listen for an IP address.
You could try what helps with a current Microsoft Windows 10 bug.
Microsoft tells to press Shift and restart your computer:
To accomplish this you could also type ´shutdown /r /f /t 0´ in your console.
I just came across this issue on a Lenovo Edge E530. It was happening on both wireless & LAN.
Followed Tobia's suggestion for stopping & starting DHCP Client service. When stopping the DHCP Client service via services.msc, it gave me an error message, but the service was stopped. When I restarted the service, problem was solved.
I did not have to do anything with the network stack.
