Windows 10 not getting IP address from DHCP
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:
- Changing router.
- Reset TCP stack and winsock.
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.
windows-10 ip dhcp
edited Jan 4 '17 at 22:15
Kamil Maciorowski
28.2k156185
asked Jun 17 '16 at 6:03
MrigankMrigank
26114
add a comment |
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:
- Changing router.
- Reset TCP stack and winsock.
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.
windows-10 ip dhcp
edited Jan 4 '17 at 22:15
Kamil Maciorowski
28.2k156185
asked Jun 17 '16 at 6:03
MrigankMrigank
26114
Once check restarting DHCP client in services.
– vembutech
Jun 17 '16 at 6:53
1
169... is the link local IP address. Your computer assigns it to itself when it cannot contact the DHCP server. See: askleo.com/why_cant_i_connect_with_a_169254xx_ip_address
– InterLinked
Jan 4 '17 at 21:58
add a comment |
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:
- Changing router.
- Reset TCP stack and winsock.
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.
windows-10 ip dhcp
edited Jan 4 '17 at 22:15
Kamil Maciorowski
28.2k156185
asked Jun 17 '16 at 6:03
MrigankMrigank
26114
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:
- Changing router.
- Reset TCP stack and winsock.
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.
windows-10 ip dhcp
windows-10 ip dhcp
edited Jan 4 '17 at 22:15
Kamil Maciorowski
28.2k156185
asked Jun 17 '16 at 6:03
MrigankMrigank
26114
edited Jan 4 '17 at 22:15
Kamil Maciorowski
28.2k156185
asked Jun 17 '16 at 6:03
MrigankMrigank
26114
edited Jan 4 '17 at 22:15
Kamil Maciorowski
28.2k156185
edited Jan 4 '17 at 22:15
Kamil Maciorowski
28.2k156185
edited Jan 4 '17 at 22:15
Kamil Maciorowski
28.2k156185
28.2k156185
asked Jun 17 '16 at 6:03
MrigankMrigank
26114
asked Jun 17 '16 at 6:03
MrigankMrigank
26114
asked Jun 17 '16 at 6:03
MrigankMrigank
26114
26114
Once check restarting DHCP client in services.
– vembutech
Jun 17 '16 at 6:53
1
169... is the link local IP address. Your computer assigns it to itself when it cannot contact the DHCP server. See: askleo.com/why_cant_i_connect_with_a_169254xx_ip_address
– InterLinked
Jan 4 '17 at 21:58
add a comment |
Once check restarting DHCP client in services.
– vembutech
Jun 17 '16 at 6:53
1
169... is the link local IP address. Your computer assigns it to itself when it cannot contact the DHCP server. See: askleo.com/why_cant_i_connect_with_a_169254xx_ip_address
– InterLinked
Jan 4 '17 at 21:58
Once check restarting DHCP client in services.
– vembutech
Jun 17 '16 at 6:53
Once check restarting DHCP client in services.
– vembutech
Jun 17 '16 at 6:53
1
1
169... is the link local IP address. Your computer assigns it to itself when it cannot contact the DHCP server. See: askleo.com/why_cant_i_connect_with_a_169254xx_ip_address
– InterLinked
Jan 4 '17 at 21:58
169... is the link local IP address. Your computer assigns it to itself when it cannot contact the DHCP server. See: askleo.com/why_cant_i_connect_with_a_169254xx_ip_address
– InterLinked
Jan 4 '17 at 21:58
add a comment |
8 Answers
8
active
oldest
votes
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.
answered Nov 28 '16 at 7:51
TobiaTobia
1,09171940
add a comment |
Restarting DHCP Client from services solved my problem.
answered Oct 1 '18 at 10:46
eneskieneski
1134
add a comment |
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.
answered Dec 11 '16 at 22:03
AkisAkis
11
The author's problem has nothing to do with the Windows 10 bug introduced by KB3201845.
– Ramhound
Jan 4 '17 at 22:22
add a comment |
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.
answered Sep 16 '17 at 14:26
MorphMorph
1
add a comment |
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.
answered Jan 20 at 17:40
Keith BosenbergKeith Bosenberg
1
add a comment |
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.
answered Dec 10 '16 at 18:30
GokkyGokky
1
Hi, your answer would be more useful if you'd explain more on what do to exactly and where to do it. Read How to Answer to learn about providing good answers.
– user 99572 is fine
Dec 24 '16 at 15:30
add a comment |
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.
answered Dec 10 '16 at 19:51
JaleksJaleks
1799
The author's problem has nothing to do with the Windows 10 bug introduced by KB3201845.
– Ramhound
Jan 4 '17 at 22:22
And did the hint not help out?
– Jaleks
Jan 6 '17 at 7:54
Your hint is for an entirely different problem. You should edit your answer so it addrsss specifically the problem the author had
– Ramhound
Jan 6 '17 at 12:55
add a comment |
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.
answered Jan 4 '17 at 21:53
Eagle_eyeEagle_eye
1
1
Your problem is entirely different the author's problem. You need to simply update to the current build of Windows 10. See this answer for more information. This also doesn't actually answer the author's question but instead ask's your own question within the body of an answer.
– Ramhound
Jan 4 '17 at 22:21
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1090319%2fwindows-10-not-getting-ip-address-from-dhcp%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
8 Answers
8
active
oldest
votes
8 Answers
8
active
oldest
votes
active
oldest
votes
active
oldest
votes
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.
answered Nov 28 '16 at 7:51
TobiaTobia
1,09171940
add a comment |
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.
answered Nov 28 '16 at 7:51
TobiaTobia
1,09171940
add a comment |
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.
answered Nov 28 '16 at 7:51
TobiaTobia
1,09171940
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.
answered Nov 28 '16 at 7:51
TobiaTobia
1,09171940
edited Nov 28 '16 at 8:00
answered Nov 28 '16 at 7:51
TobiaTobia
1,09171940
answered Nov 28 '16 at 7:51
TobiaTobia
1,09171940
answered Nov 28 '16 at 7:51
TobiaTobia
1,09171940
1,09171940
add a comment |
add a comment |
Restarting DHCP Client from services solved my problem.
answered Oct 1 '18 at 10:46
eneskieneski
1134
add a comment |
Restarting DHCP Client from services solved my problem.
answered Oct 1 '18 at 10:46
eneskieneski
1134
add a comment |
Restarting DHCP Client from services solved my problem.
answered Oct 1 '18 at 10:46
eneskieneski
1134
Restarting DHCP Client from services solved my problem.
answered Oct 1 '18 at 10:46
eneskieneski
1134
answered Oct 1 '18 at 10:46
eneskieneski
1134
answered Oct 1 '18 at 10:46
eneskieneski
1134
answered Oct 1 '18 at 10:46
eneskieneski
1134
1134
add a comment |
add a comment |
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.
answered Dec 11 '16 at 22:03
AkisAkis
11
The author's problem has nothing to do with the Windows 10 bug introduced by KB3201845.
– Ramhound
Jan 4 '17 at 22:22
add a comment |
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.
answered Dec 11 '16 at 22:03
AkisAkis
11
The author's problem has nothing to do with the Windows 10 bug introduced by KB3201845.
– Ramhound
Jan 4 '17 at 22:22
add a comment |
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.
answered Dec 11 '16 at 22:03
AkisAkis
11
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.
answered Dec 11 '16 at 22:03
AkisAkis
11
answered Dec 11 '16 at 22:03
AkisAkis
11
answered Dec 11 '16 at 22:03
AkisAkis
11
answered Dec 11 '16 at 22:03
AkisAkis
11
11
The author's problem has nothing to do with the Windows 10 bug introduced by KB3201845.
– Ramhound
Jan 4 '17 at 22:22
add a comment |
The author's problem has nothing to do with the Windows 10 bug introduced by KB3201845.
– Ramhound
Jan 4 '17 at 22:22
The author's problem has nothing to do with the Windows 10 bug introduced by KB3201845.
– Ramhound
Jan 4 '17 at 22:22
The author's problem has nothing to do with the Windows 10 bug introduced by KB3201845.
– Ramhound
Jan 4 '17 at 22:22
add a comment |
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.
answered Sep 16 '17 at 14:26
MorphMorph
1
add a comment |
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.
answered Sep 16 '17 at 14:26
MorphMorph
1
add a comment |
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.
answered Sep 16 '17 at 14:26
MorphMorph
1
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.
answered Sep 16 '17 at 14:26
MorphMorph
1
answered Sep 16 '17 at 14:26
MorphMorph
1
answered Sep 16 '17 at 14:26
MorphMorph
1
answered Sep 16 '17 at 14:26
MorphMorph
1
1
add a comment |
add a comment |
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.
answered Jan 20 at 17:40
Keith BosenbergKeith Bosenberg
1
add a comment |
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.
answered Jan 20 at 17:40
Keith BosenbergKeith Bosenberg
1
add a comment |
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.
answered Jan 20 at 17:40
Keith BosenbergKeith Bosenberg
1
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.
answered Jan 20 at 17:40
Keith BosenbergKeith Bosenberg
1
answered Jan 20 at 17:40
Keith BosenbergKeith Bosenberg
1
answered Jan 20 at 17:40
Keith BosenbergKeith Bosenberg
1
answered Jan 20 at 17:40
Keith BosenbergKeith Bosenberg
1
1
add a comment |
add a comment |
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.
answered Dec 10 '16 at 18:30
GokkyGokky
1
Hi, your answer would be more useful if you'd explain more on what do to exactly and where to do it. Read How to Answer to learn about providing good answers.
– user 99572 is fine
Dec 24 '16 at 15:30
add a comment |
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.
answered Dec 10 '16 at 18:30
GokkyGokky
1
Hi, your answer would be more useful if you'd explain more on what do to exactly and where to do it. Read How to Answer to learn about providing good answers.
– user 99572 is fine
Dec 24 '16 at 15:30
add a comment |
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.
answered Dec 10 '16 at 18:30
GokkyGokky
1
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.
answered Dec 10 '16 at 18:30
GokkyGokky
1
answered Dec 10 '16 at 18:30
GokkyGokky
1
answered Dec 10 '16 at 18:30
GokkyGokky
1
answered Dec 10 '16 at 18:30
GokkyGokky
1
1
Hi, your answer would be more useful if you'd explain more on what do to exactly and where to do it. Read How to Answer to learn about providing good answers.
– user 99572 is fine
Dec 24 '16 at 15:30
add a comment |
Hi, your answer would be more useful if you'd explain more on what do to exactly and where to do it. Read How to Answer to learn about providing good answers.
– user 99572 is fine
Dec 24 '16 at 15:30
Hi, your answer would be more useful if you'd explain more on what do to exactly and where to do it. Read How to Answer to learn about providing good answers.
– user 99572 is fine
Dec 24 '16 at 15:30
Hi, your answer would be more useful if you'd explain more on what do to exactly and where to do it. Read How to Answer to learn about providing good answers.
– user 99572 is fine
Dec 24 '16 at 15:30
add a comment |
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.
answered Dec 10 '16 at 19:51
JaleksJaleks
1799
The author's problem has nothing to do with the Windows 10 bug introduced by KB3201845.
– Ramhound
Jan 4 '17 at 22:22
And did the hint not help out?
– Jaleks
Jan 6 '17 at 7:54
Your hint is for an entirely different problem. You should edit your answer so it addrsss specifically the problem the author had
– Ramhound
Jan 6 '17 at 12:55
add a comment |
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.
answered Dec 10 '16 at 19:51
JaleksJaleks
1799
The author's problem has nothing to do with the Windows 10 bug introduced by KB3201845.
– Ramhound
Jan 4 '17 at 22:22
And did the hint not help out?
– Jaleks
Jan 6 '17 at 7:54
Your hint is for an entirely different problem. You should edit your answer so it addrsss specifically the problem the author had
– Ramhound
Jan 6 '17 at 12:55
add a comment |
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.
answered Dec 10 '16 at 19:51
JaleksJaleks
1799
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.
answered Dec 10 '16 at 19:51
JaleksJaleks
1799
answered Dec 10 '16 at 19:51
JaleksJaleks
1799
answered Dec 10 '16 at 19:51
JaleksJaleks
1799
answered Dec 10 '16 at 19:51
JaleksJaleks
1799
1799
The author's problem has nothing to do with the Windows 10 bug introduced by KB3201845.
– Ramhound
Jan 4 '17 at 22:22
And did the hint not help out?
– Jaleks
Jan 6 '17 at 7:54
Your hint is for an entirely different problem. You should edit your answer so it addrsss specifically the problem the author had
– Ramhound
Jan 6 '17 at 12:55
add a comment |
The author's problem has nothing to do with the Windows 10 bug introduced by KB3201845.
– Ramhound
Jan 4 '17 at 22:22
And did the hint not help out?
– Jaleks
Jan 6 '17 at 7:54
Your hint is for an entirely different problem. You should edit your answer so it addrsss specifically the problem the author had
– Ramhound
Jan 6 '17 at 12:55
The author's problem has nothing to do with the Windows 10 bug introduced by KB3201845.
– Ramhound
Jan 4 '17 at 22:22
The author's problem has nothing to do with the Windows 10 bug introduced by KB3201845.
– Ramhound
Jan 4 '17 at 22:22
And did the hint not help out?
– Jaleks
Jan 6 '17 at 7:54
And did the hint not help out?
– Jaleks
Jan 6 '17 at 7:54
Your hint is for an entirely different problem. You should edit your answer so it addrsss specifically the problem the author had
– Ramhound
Jan 6 '17 at 12:55
Your hint is for an entirely different problem. You should edit your answer so it addrsss specifically the problem the author had
– Ramhound
Jan 6 '17 at 12:55
add a comment |
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.
answered Jan 4 '17 at 21:53
Eagle_eyeEagle_eye
1
1
Your problem is entirely different the author's problem. You need to simply update to the current build of Windows 10. See this answer for more information. This also doesn't actually answer the author's question but instead ask's your own question within the body of an answer.
– Ramhound
Jan 4 '17 at 22:21
add a comment |
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.
answered Jan 4 '17 at 21:53
Eagle_eyeEagle_eye
1
1
Your problem is entirely different the author's problem. You need to simply update to the current build of Windows 10. See this answer for more information. This also doesn't actually answer the author's question but instead ask's your own question within the body of an answer.
– Ramhound
Jan 4 '17 at 22:21
add a comment |
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.
answered Jan 4 '17 at 21:53
Eagle_eyeEagle_eye
1
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.
answered Jan 4 '17 at 21:53
Eagle_eyeEagle_eye
1
answered Jan 4 '17 at 21:53
Eagle_eyeEagle_eye
1
answered Jan 4 '17 at 21:53
Eagle_eyeEagle_eye
1
answered Jan 4 '17 at 21:53
Eagle_eyeEagle_eye
1
1
1
Your problem is entirely different the author's problem. You need to simply update to the current build of Windows 10. See this answer for more information. This also doesn't actually answer the author's question but instead ask's your own question within the body of an answer.
– Ramhound
Jan 4 '17 at 22:21
add a comment |
1
Your problem is entirely different the author's problem. You need to simply update to the current build of Windows 10. See this answer for more information. This also doesn't actually answer the author's question but instead ask's your own question within the body of an answer.
– Ramhound
Jan 4 '17 at 22:21
1
1
Your problem is entirely different the author's problem. You need to simply update to the current build of Windows 10. See this answer for more information. This also doesn't actually answer the author's question but instead ask's your own question within the body of an answer.
– Ramhound
Jan 4 '17 at 22:21
Your problem is entirely different the author's problem. You need to simply update to the current build of Windows 10. See this answer for more information. This also doesn't actually answer the author's question but instead ask's your own question within the body of an answer.
– Ramhound
Jan 4 '17 at 22:21
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1090319%2fwindows-10-not-getting-ip-address-from-dhcp%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Once check restarting DHCP client in services.
– vembutech
Jun 17 '16 at 6:53
1
169... is the link local IP address. Your computer assigns it to itself when it cannot contact the DHCP server. See: askleo.com/why_cant_i_connect_with_a_169254xx_ip_address
– InterLinked
Jan 4 '17 at 21:58