[Fixed] Windows 10 Limited Connectivity and Not Getting IP from DHCP -Wi-Fi or LAN

If your Windows 10 desktop or laptop suddenly lost the network connectivity and showing limited connectivity, then this how-to guide will be useful. In this case, the Wi-Fi or Wired network can go offline and could not connect to the network. It will impact the Internet and other network activities on your computer. These below steps show how to fix Windows 10 limited connectivity issue on the wireless or wired network.

If it shows as limited connectivity, mostly the network adapter would not have got an IP from the DHCP. If only one particular PC is facing this issue on your network/home, then apparently nothing wrong with the network setup or DHCP server, it is a problem on your Windows 10 laptop or desktop. When I recently faced this similar issue randomly on a Windows 10 and another Windows 8.1 laptop, the following steps helped me to solve the problem.

This problem is not specifically for the Wireless network adapter; it can happen to your LAN wired network adapter too. It’s an issue with the IP stack (IPv4 or IPv6 – based on which protocol you are using). There are few solutions available on the internet, but let me start with the possible (which worked for me straight away) solution, then other methods.

If you get “DNS Server Not Found” error on Windows 10/8.1 while connected through the wireless adapter, you must check this guide to fix it. Updating or re-installing the WiFi adapter driver will solve it most of the time. But this limited connectivity issue in Windows 10/8.1 could be due to the IP address issue. The network adapter will not get an IP address; hence it will be getting APIPA address range, something like 169.245.x.x, that means you are in trouble.

The Solution for Windows 10 Limited Connectivity – Wi-Fi and Cable Network

As described earlier, this is due to IP address/IP stack problem which can be resolved by resetting the TCP/IP stack to its default value. TCP/IP is a protocol used in most of the computers (including Mac, Linux, and Windows) and other network devices to make communication in LAN or WAN.

Use NetShell utility (netsh.exe) command to perform the task.

1) Open the command prompt as Administrator. Search ‘cmd’ and right click on cmd then select ‘Run as administrator’ as below.

open cmd as admin

2) Type following commands –

netsh winsock reset catalog  (Reset WINSOCK entries to installation defaults)
netsh int ipv4 reset reset.log (Reset IPv4 TCP/IP stack to installation defaults)
Source

fix for limited connectivity in Windows 103) Reboot the computer.

The Problem:
One of the above reset commands removes all persistent static route entries from your Windows 10 computer. I faced this issue and had to add those static routes again by ‘route add’ command.

This will mostly solve the problem of limited connectivity issue on Windows 10 or 8.1.

4) If you are still facing the problem and your Windows 10 or 8.1 can’t connect to the internet and other local network resources, continue below steps.

The following few more netsh commands may fix the problem. Make sure you are entering below commands in command prompt which was opened as Administrator.

netsh int tcp set heuristics disabled

netsh int tcp set global autotuninglevel=disabled

netsh int tcp set global rss=enabled

I’m sure one of the above commands may fix the issue or at least make your Windows 10 network faster.

5) If your wired network is fine, but you are having trouble in the wireless network only, then you can change the power options and wake up the WiFi Adapter.

Right-click on the WiFi adapter and select Properties.

wifi propertiesClick on ‘Configure’.

configureOn the ‘Power Management’ tab, uncheck the below option.

This will prevent Windows 10 to turn off the WiFi adapter when it goes to sleep or hibernation mode. Because when the laptop resumes from sleep, the WiFi adapter may not wake up and work properly. So, avoiding this feature may help in having proper wireless network connectivity in Windows 10.

wake up wifi adapter in windows 10


6)
A discussion here mentioned that having a 3rd party antivirus and personal firewall software such as BitDefender also can disturb the network connectivity in Windows 10/8.1. So, if none of the above solutions work for you and you have a dedicated Antivirus software with firewall enabled, you can uninstall it or find a way to allow Internet connectivity and IP requests in the firewall settings. It might help.

I hope one of the above methods will solve the windows 10 limited connectivity or not getting IP address issue on Windows 10 and Windows 8.1. Also, keep updating the Windows OS and drivers (especially LAN and WiFi network adapters) from Windows update. They will fix the issue permanently.

123 thoughts on “[Fixed] Windows 10 Limited Connectivity and Not Getting IP from DHCP -Wi-Fi or LAN”

  1. Bloody brilliant! The first fix worked for me, thanks so much for sharing. In 25+ in the industry, that was a new one.

  2. Tried all steps, still can’t get an IP addr. Good tries tho, some I’ve never heard of. When I plug into my router, it keeps saying “Unidentified Network”. I plug the same wire (from same port on router) into another PC, works fine. I’ve tried all the ipconfig/netsh/net cmds, Registry hacks, etc. to refresh winsock, IPv4, DNS, etc.

  3. It wouldnt work for me but what did was setting the ipv4 ip and gateway manually. Only problem is if you carry your laptop to diffrent places you will have to reasign a new ip bassed on the new connections gateway ip

  4. The solution it is work but problem again repeating a lot of time later.
    I wanna f*ck microsof*ck

  5. Thanks so much…. I have been struggling with this for days…. The first solu worked for me.

  6. This is wonderful information. These commands worked for me:

    netsh int tcp set heuristics disabled

    netsh int tcp set global autotuninglevel=disabled

    netsh int tcp set global rss=enabled

  7. Did not work for me either. If I assigned a static IP address then is the only way it works. For some reason DHCP is not assigning IP address. Either it can not find the DHCP or process is going to La La Land while assigning IP address. I will keep researching. If someone has the solution, please post it. Thanks

    • I have the same issue. It started after windows creators update. I can’t even try to update the driver on my wifi adapter. Tried everything here, plus some, and nothing has worked.

      • I took the computer to the Geek Squad. They determined Windows was corrupt. They tried to reset it, and that didn’t work either. Finally just reinstalled Windows 10, and everything finally works.

  8. after a general power interruption, the devices connected to our lan get randomly and occasionally a wrong IP (192.168.0.xxx instead of 192.168.1.xxx); some say that there could be a ‘rogue’ DHCP server interfering with the router’s DHCP service but so far i havn’t been able to figure it out. At least, it works for us to assign a fixed IP to a disconnected device, but it’s only a temp solution.

  9. Does not work. Windows is a piece of crap. I run Linux but my neighbor keeps to invite me to “repair my Internet”. I’m just very angry as I have already spent 3 hours finding some solution.

  10. netsh winsock reset catalog (Reset WINSOCK entries to installation defaults)
    netsh int ipv4 reset reset.log (Reset IPv4 TCP/IP stack to installation defaults)

    Worked fine for me because after Win 10 installation I got no network connection before, except if I set WLAN and LAN to manual IP’s.

  11. I had been running ipconfig /release – ipconfig /renew after moving to a different AP during so long. Now this has fixed it. Thank you!!!

  12. DHCP got stuck, kept my old default GW but assigned an apipa address. Manual IP worked, ipcofig /release didn’t dolve it, removing and adding tcp/ip stack didn’t solve it, removing the adapter didn’t solve it.

    netsh winsock reset catalog
    netsh int ipv4 reset reset.log
    and now all is well. Great post ! Thanks!

  13. I had this issue too and the first 2 commands didn’t work. Before trying the other 3 I decided to try something else. I set static IPs for both of my adapters, connected to the network, then I removed the static IPs, and out of nowhere DHCP started working again.

Comments are closed.