How to Fix IP Address Starting With 169.254

If your system suddenly has an IP address starting with 169.254 then it is certain that you will have no connection to the internet and neither to any network resource you previously had. Having this IP address is almost as good as having no IP address. In other words, you can say your system is simply cut off from the network.

When you are on a network, using the internet or accessing any other network resource, and if you are not given an identity manually, a Dynamic Host Configuration Protocol (DHCP) server is responsible for giving you a unique identity on that network automatically when you connect to the network. That identity is called an IP address, which will be usually something starting like 192.168.X.X. In a work place, the DHCP server is usually on a separate computer called a server. Whereas in a home setup or a small office setup (SOHO), DHCP server is managed internally by your Router.

If for some reason you lose the connection to the network, then of course your system will not be able to find a DHCP server to get an IP address automatically. So, in this situation, Windows will automatically assign an IP address to itself starting with 169.254. This procedure is called Automatic Private Internet Protocol Addressing (APIPA).

Common cause for this to happen is when the DHCP server stops responding when you send a request for an IP address. So usually, the issue resides on your Router or Wireless Access Point side. In some cases, the cause of this issue has also been attributed to Windows itself. If Windows fail to fetch an appropriate IP address in time, acting on its APIPA protocol, it will assign itself the 169.254.0.0 IP.

In this guide, i will walk you through various methods to fix the issue. Follow each method in the listed order, until the issue is resolved.

Method 1: Power Cycle Your Router

A power cycle will do a soft reset, terminate and re-initiate all connections to devices connected to the Router.

Turn the Computer that has the issue off.

Unplug power from your Router/Wireless Access Point & Modem. Leave it unplugged for a minute and then plug the power back to turn them back on. Power up your computer and now check if the proper IP Address is assigned.

After following this method, if you have other devices connected to this router check them out as well to see what network are they on, if they’re also unable to connect then the issue points to a hardware fault with your router and it will need to be replaced. BUT there is no harm in following the other Methods below as well.

Check if the IP is gone. If not, move on to the next solution. You may also check this guide out which has scripted commands to reset network components.

Method 2: Request New IP through CMD

Press the Windows key, type cmd. Right click on cmd in the search results and click Run as Administrator. In the black command prompt window, type the following commands and press Enter after each.

ipconfig /release

ipconfig /renew

Test to see if the issue is now resolved.

169-254-fix

Method 3: Check your Router/Wireless Access Point Settings

Log in to your router or modem and make sure that DHCP is enabled.

ABOUT THE AUTHOR

Kevin Arrows


Kevin Arrows is a highly experienced and knowledgeable technology specialist with over a decade of industry experience. He holds a Microsoft Certified Technology Specialist (MCTS) certification and has a deep passion for staying up-to-date on the latest tech developments. Kevin has written extensively on a wide range of tech-related topics, showcasing his expertise and knowledge in areas such as software development, cybersecurity, and cloud computing. His contributions to the tech field have been widely recognized and respected by his peers, and he is highly regarded for his ability to explain complex technical concepts in a clear and concise manner.

Comments

8
    AK
    abhimanyu kumar Sep 19, 2017

    https://uploads.disquscdn.com/images/a8ae441dc63d3dbed4eae225d21302ae218a578771c5746330f8abe8d1d8f210.jpg

    I also have same problem .and after applying these command what it is writing?

      KA
      K. Arrows Author Sep 29, 2017

      Can you make sure your network adapters are enabled?

    VA
    ValyrianSteel Feb 2, 2018

    If you have a USB network dongle and it picked up a proper IP and the network works fine then the problem will most likely be a firewall block on the mac address.

    SW
    Shane Warren Author Sep 21, 2019

    Login into your router on a computer and enable DHCP it will enable it for all the devices.

    AO
    Aymincendiary One Feb 3, 2020

    Ipconfig /release ipconfig /renew doesn’t work any more… message says parameter is incorrect. Only way to attempt another address pull is to ddo a reboot. Keep getting a DNS_PROBE_NXDOMAIN error and can’t access any sites other than Yahoo home, which is probably just a cached page. When I reboot I’m fine but I have to keep doing it over and over again. Only on this computer and not others so I don’t believe the problem is with the router. It’s either the onboard NIC on the motherboard or Windows OS itself.

      SW
      Shane Warren Author Feb 8, 2020

      Try to change your DNS Servers to 8.8.8.8 and 8.8.4.4 as secondary and check if that fixes the connectivity issue for you.

        AO
        Aymincendiary One Feb 8, 2020

        I tried all that, I checked my router settings, it is consistently handing out 192.168.1.118 for this computer. What I did to have Windows stop self assigning is statically assigning that 118 address. I couldn’t release or renew the DHCP lease using the command line, the only way out to pull an address for the router was to close all my applications and do a reboot on the OS. Sometimes the self assign would happen upon first bootup, sometimes it would happen at random during operation. I went into Device Manager/Power Management and unchecked the box where it allows the onboard NIC to go to sleep however this didn’t fix the problem. Nailing up the IP address, subnet mask and default gateway seems to be working as long as my router doesn’t hand out that IP address to another computer and I get an IP address conflict. I don’t see how to make an exclusion on a SOHO router like you can on a Cisco Systems router (dhcp excluded-address xxxx in global config mode) so I may have to upgrade the firmware to OpenWRT. Seems like this is a Windows problem as it happens only on this computer with both onboard NICs and the wireless adapter as well. I don’t want to have to reimage my drive unless I am absolutely certain this will do the job. Thank you.

        AO
        Aymincendiary One Feb 9, 2020

        I tried that and still have the problem,. For some reason my NIC occasionally loses it’s lease and self assigns. Can happen any time. Changed cables on router, changed ports, turned off power management on the NIC. Happens on both onboard NICs and the Wireless adapter but only on this computer, not my HT computer in living room. I nailed up the IP address the router is handing out in network settings and so far I don’t have any problems, SOHO routers like Linksys don’t appear to have the ability to set an exclusion like Cisco managed devices used in business so hopefully my router won’t assign that IP address to another computer. I’ve seen over time it consistently hands out 192.168.1.118 in the 192.168.1.0-255 range; default gateway is 192.168.1.1 so I’ll keep an eye on a balloon message sating I have an IP address conflict. It’s a rig but the only other option would be to reimage my hard drive and reinstall everything back on the system and hope for the best. I can also try a third party NIC and see if I still have the problem of IP address dropout and self assign. If that fixes it then the motherboard manufacturer needs to be contacted about the problem. Thank you for your assistance.