|
|
Post by bromptonaut on Dec 11, 2016 11:42:50 GMT
We have what I think is a fairly standard domestic network.
ADSL 2 connection, Netgear D6200 dual band modem/router (2.4 and 5ghz). WPS2 security. DHCP enabled.
Connected to it are a variety of Android devices and four Win 10 laptops. Until Friday all the laptops were functioning fine. Since then Mrs B's 'desktop' laptop, a Toshiba Satellite L50 has refused to connect to either 2.4 or 5ghz WiFi.
Probing around I've ascertained that going to the wireless adapter details (Intel Dual Band Wireless AC3160) IPv4 address shows as Autoconfigure 169.254.252.41. Other machines do not mention autoconfigure and show (correctly) the 192.168.1.xx series number allocated by the Router's DHCP.
Going to Network Connection Status>Properties>Internet Protocol Version 4 (TCP/IP v4)>Properties and resetting the DHCP advanced settings to use the Router's IP address as primary DHCP I can get it to connect.
However, as soon as the laptop is shut down/restarted, the problem re-occurs.
I've googled the issue and it's clearly 'known' but am struggling to find solutions that make any sense.
Any suggestions?
NB Question is also on C4P.
|
|
|
|
Post by tyrednexited on Dec 11, 2016 12:04:47 GMT
I had a Win 10 update hang up over the last couple of days. I ended up manually downloading and installing. In doing so, I noted reference to the fact that it was implicated (since Friday) in DHCP problems. I'm not sure whether there is a definitive solution yet, the general feeling is that Microsoft have "broken" the DHCP client. I have, however, hit the advice given in here: mspoweruser.com/heres-how-to-fix-the-no-internet-connection-issue-on-windows-10-build-14393-479/ in other posts. Given that you have experienced the issue since Friday, if it weren't Win 10 I'd suggest undoing the latest update, but Win 10 will automatically try to re-install in rather short order. There are ways of taking more control over the Win 10 update process to inhibit re-installation (here for example: www.pcadvisor.co.uk/how-to/windows/how-stop-windows-10-update-3632159/ ) ...but though it is a Microsoft patch, I can't vouch for it. (It is partially for such reasons that my main machine remains on Win7 - I have a laptop with Win 10) |
|
|
|
Post by Hofmeister on Dec 11, 2016 12:34:42 GMT
I had a Win 10 update hang up over the last couple of days. I ended up manually downloading and installing. In doing so, I noted reference to the fact that it was implicated (since Friday) in DHCP problems. I'm not sure whether there is a definitive solution yet, the general feeling is that Microsoft have "broken" the DHCP client. I have, however, hit the advice given in here: mspoweruser.com/heres-how-to-fix-the-no-internet-connection-issue-on-windows-10-build-14393-479/ in other posts. Given that you have experienced the issue since Friday, if it weren't Win 10 I'd suggest undoing the latest update, but Win 10 will automatically try to re-install in rather short order. There are ways of taking more control over the Win 10 update process to inhibit re-installation (here for example: www.pcadvisor.co.uk/how-to/windows/how-stop-windows-10-update-3632159/ ) ...but though it is a Microsoft patch, I can't vouch for it. (It is partially for such reasons that my main machine remains on Win7 - I have a laptop with Win 10) Yes it well known, and indeed MS have broken the DHCP client. The stable way around it till its fixed in another patch, is to move to fixed IP for the network, which means reconfiguring your router, and all the other clients on your network. Win 10 is a bloody nightmare when it comes to patching and updating (MS are trying to take control of what you see, do and who you do it with) so many corporates are refusing to move to it for that very reason. |
|
Rob
Full Member
Posts: 2,778 
|
Post by Rob on Dec 11, 2016 12:41:11 GMT
To use a fixed IP on this one machine doesn't need you to change other devices as long as (a) the router's DHCP server does not allocate addresses over the whole subnet and you have that many machines (b) so allocate an IP address the router won't allocate.
e.g. the router might allocate 192.168.1.100 - 192.168.1.200 say. So give this Win10 machine a static IP of 192.168.1.10.
The issue is if you rely on DHCP elsewhere.... if this is broke at home presumably it does not work elsewhere either.
|
|
|
|
Post by bromptonaut on Dec 11, 2016 13:11:52 GMT
Thanks guys. Spent best part of three hours yesterday and today faffing with it and now need to shop, check caravan after cold weather and do othee domestic stuff. Will be tonight before I can try any solutions. At least it's connected atm so the constant whining noise that was Mrs B unable to move her PhD forward has stopped.
Fixed IP will be problematic as she needs to use it at Uni and when on sites doing research.
|
|
Rob
Full Member
Posts: 2,778
|
Post by Rob on Dec 11, 2016 15:16:00 GMT
Which is what I thought but if this is a Windows 10 DHCP client problem, then it will be broken on all networks until Microsoft issue a fix.
So if you can roll-back the last updates and then disable them you might have a fix.
|
|
|
|
Post by tyrednexited on Dec 13, 2016 9:23:24 GMT
..I note this is still being discussed in the other place. If the use of the laptop is important I would advise: 1. Testing the Netsh commands referenced in the first link of my post above. (they are mentioned as a possible resolution in a number of places, but it isn't obvious whether these will need to be issued at each reboot/reconnection). I suspect I'm teaching my Grandmother, but if you don't know how to do these from a command prompt, I, or others here, will be able to advise. 2. If this doesn't work, and given that KB3201845 (the latest rolled-up MS update) seems to be firmly implicated, I would take the further steps from my post above, echoed by Rob. Install the Microsoft "inhibitor" for version 1607 highlighted here: support.microsoft.com/en-us/kb/3073930#bookmark-1607 (this will give you the opportunity to manage further windows updates, avoiding automatic re-installation of the bad patch). Uninstall KB3201845 using Settings/Windows Update/Update History/Uninstall updates and selecting it. Then, hope this has removed the issue, and don't uninhibit further updates unless/until the fix for the specific problem is announced. It should remove the issue, but you're on your own if it doesn't........  |
|
|
|
Post by bromptonaut on Dec 13, 2016 17:37:45 GMT
This morning it was still temperamental in wifi, ie would connect when 'persuaded' but not holding connection and fubar on ethernet.
Mid afternoon it had again lot wifi after hibernating. Did some ipconfig stuff at command prompt as suggested elsewhere and got wifi connection back. Tried a restart at which point it ran updates. These are KB3201845 but dated today and presumably fix the bug aswe now seem to have normal service on both wifi and ethernet.
Thanks all.
|
|
|
|
Post by Hofmeister on Dec 14, 2016 19:31:06 GMT
This morning it was still temperamental in wifi, ie would connect when 'persuaded' but not holding connection and fubar on ethernet. Mid afternoon it had again lot wifi after hibernating. Did some ipconfig stuff at command prompt as suggested elsewhere and got wifi connection back. Tried a restart at which point it ran updates. These are KB3201845 but dated today and presumably fix the bug aswe now seem to have normal service on both wifi and ethernet. Thanks all. KB3206632, released on Tuesday this week as part of December's Patch Tuesday, contained the following bug fix: Addressed a service crash in CDPSVC (CDPSvc is the Connected Devices Platform Service) that in some situations could lead to the machine not being able to acquire an IP address. |
|
