R
RobGarrett
I have this same problem on a Lenovo laptop, Intel N-7260 wifi adapter. Windows 10 Enterprise, 1903 -- current on updates.
It will connect for a short time (sometimes an hour or so, more often less than a minutes) and then the connection drops and the adapter goes back into "Identifying" state - trying to get an address from DHCP. Let me be clear on this. This happens AFTER the adapter has already "DHCP'ed" and gotten a valid IP address assigned. After a short time (usually minutes) the adapter somehow "loses" this address and appears to try to "re-DHCP", at which point the problem begins. This attempt eventually fails and the adapter gets assigned a default local IP in the 169... network and it's in "No Internet" state.
Once that happens, no matter how many times I turn off and turn on wifi, disable/enable the adapter, reset the entire network using the full brace of all the netsh reset .... commands, it's done and won't successfully "DHCP".
However if I run the "diagnose"/troubleshooter tool, it will reconnect and successfully DHCP - for "awhile" - then the whole thing starts over.
What I've tried so far:
* Turning wifi off and on
* Disable/reenable the adapter
* Made sure that "power management" on the adapter is turned off
* Completely uninstalled/reinstalled the adapter from device manager (both with and without deleting the driver)
* Run all the netsh reset commands I've been able to find
* reset winsock
* used "Network Reset" from the Win10 Settings->Network & Internet menu
* Installing the most recent driver for the N-7260 directly from the Intel site
* sfc /scannow (runs clean)
* dism /checkhealth, /scanhealth, /restorehealth (from a known pristine install image) --- also runs clean
* doing all of the above immediately after a fresh boot
The ONLY thing I've found so far that has any positive results has been to run the diagnose/trouble-shooter tool. As it runs it shows messages: "Reset the WiFi adapter", ending in "Problems found: WiFi doesn't have a valid IP configuration - Fixed". At which point it's up and running ---- for a few minutes - maybe - if I'm lucky. Then the connection drops, it goes back into "Identifying..." which ultimately fails and the adapter once more has an IP address in the 169.. range with "No Internet", and it will stay that way no matter what I try (see above) until I run the Diagnose tool again. Looking in the various output detail files that the troubleshooter produces, there's not much useful information beyond what I already know - that the adapter has been assigned a 'local' address - duh.
BTW, I have my own server network here including my own local DHCP server, and *every* other computer on my network is running fine without any sort of DHCP problems at all, so I know DHCP is functional.
NOTHING - has solved the problem. It's still happening.
My conclusion: Network support in Windows 10 is **** and the MS developers who work on it are a bunch of morons.
Continue reading...
It will connect for a short time (sometimes an hour or so, more often less than a minutes) and then the connection drops and the adapter goes back into "Identifying" state - trying to get an address from DHCP. Let me be clear on this. This happens AFTER the adapter has already "DHCP'ed" and gotten a valid IP address assigned. After a short time (usually minutes) the adapter somehow "loses" this address and appears to try to "re-DHCP", at which point the problem begins. This attempt eventually fails and the adapter gets assigned a default local IP in the 169... network and it's in "No Internet" state.
Once that happens, no matter how many times I turn off and turn on wifi, disable/enable the adapter, reset the entire network using the full brace of all the netsh reset .... commands, it's done and won't successfully "DHCP".
However if I run the "diagnose"/troubleshooter tool, it will reconnect and successfully DHCP - for "awhile" - then the whole thing starts over.
What I've tried so far:
* Turning wifi off and on
* Disable/reenable the adapter
* Made sure that "power management" on the adapter is turned off
* Completely uninstalled/reinstalled the adapter from device manager (both with and without deleting the driver)
* Run all the netsh reset commands I've been able to find
* reset winsock
* used "Network Reset" from the Win10 Settings->Network & Internet menu
* Installing the most recent driver for the N-7260 directly from the Intel site
* sfc /scannow (runs clean)
* dism /checkhealth, /scanhealth, /restorehealth (from a known pristine install image) --- also runs clean
* doing all of the above immediately after a fresh boot
The ONLY thing I've found so far that has any positive results has been to run the diagnose/trouble-shooter tool. As it runs it shows messages: "Reset the WiFi adapter", ending in "Problems found: WiFi doesn't have a valid IP configuration - Fixed". At which point it's up and running ---- for a few minutes - maybe - if I'm lucky. Then the connection drops, it goes back into "Identifying..." which ultimately fails and the adapter once more has an IP address in the 169.. range with "No Internet", and it will stay that way no matter what I try (see above) until I run the Diagnose tool again. Looking in the various output detail files that the troubleshooter produces, there's not much useful information beyond what I already know - that the adapter has been assigned a 'local' address - duh.
BTW, I have my own server network here including my own local DHCP server, and *every* other computer on my network is running fine without any sort of DHCP problems at all, so I know DHCP is functional.
NOTHING - has solved the problem. It's still happening.
My conclusion: Network support in Windows 10 is **** and the MS developers who work on it are a bunch of morons.
Continue reading...