Windows 10: Consistent DHCP failures on WIndows 10 (1903) Wifi adapter after successfully connecting.

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.

:)

 

Windows 10 - WiFi DHCP not assigning address

Just upgraded to Windows 10 on a HP2000 Notebook. The upgrade worked flawlessly with one exception. I performed the upgrade while wired to the network. When I switched to WiFi, the adapter showed "Limited Connectivity". Using Regedit, I looked at HKLM/SYSTEM/CurrentControlSet/Services/Tcpip/Parameters/Interfaces
and found that my WiFi adapter was receiving a DHCP assigned address.

In my home, I use DHCP statically assigned addresses and typically I assign the same IP to both wired and WiFi adapters on a given machine. What I didn't realize is that because the wired adapter had already been assigned the same DHCP address, the WiFi
adapter somehow couldn't re-use the address it was given by the DHCP.

After giving the Wifi adapter a different DHCP-assigned address than the wired adapter, it worked perfectly.

 

No WiFi in Win10 Pro (1903) Windows Sandbox


I (seemingly) successfully updated my Surface Pro 6 to v.1903 today, and after some initial fumbles enabling it, now have Windows Sandbox enabled and it seems to open just fine. However, there is no WiFi access within Sandbox.

Accessing Settings for Network & Internet, the list on the left is:
Status
Ethernet
Dial-up
VPN
Airplane mode
Date usage
Proxy
WiFi appears no place in that window. Network status shows No Internet Access.

What step am I missing to be able to access the internet from within the Sandbox using my computer's WiFi connection?

 

USB Wireless adapter not connecting to Wifi

Hello

I am having trouble making my new USB Wifi Adapter to work. The drivers are working fine but the issue is it is not connecting to wifi.

1. I am using Windows 10
2. The adapter which I am trying to work is Alfa AWUS036NHA 150Mbps
3. I have also one USB mini wifi adapter attached to my other USB through which I am currently using internet

From the above screenshot, the Wi-Fi 2 is which I am trying to connect. When I right-click on Wi-Fi 2 and click on Connect/Disconnect, It shows the already connected Wifi through USB mini adapter.

When I Disable WiFi and try to connect through WiFi 2 then it shows an error "Change settings, such as making a connection metered"

The device utility does not show any Wifi available connections though there are 2-3 wifi connection is there.








any idea how can I make connect to internet using my new Alfa AWUS036NHA 150Mbps Wireless USB Adaptor - Wi Fi 2 on Windows 10 ?