Resolve Getting 169.254.X.X (APIPA) Windows Automatic Private IP Address

When a Windows computer failed to get valid IP address from DHCP server, OS will automatically assign a Windows generated Automatic Private IP address called APIPA to it. This automatic Private IP address is in the range 169.254.0.1 to 169.254.255.254. In a nutshell we can say any IP address in the range (169.254.X.X) is APIPA and it shows your computer is not connected to any network. Since APIPA (169.254.X.X) is a private IP address, your computer will not communicate to any other computers connected in the network(connected to a DHCP server). If you want your computer communicate to other computers in the network, you must change 169.254.X.X IP address by fixing the issues which prevent your computer from getting a valid IP address from DHCP server. This tutorial explains major reasons to get APIPA and how to resolve it.

APIPA = Automatic Private IP Addressing

All Windows versions like Windows 8, Windows 7, Vista, XP etc support APIPA except Windows NT. Follow the instructions below to fix 169.254.x.x addressing issues.

How to Resolve 169.254.X.X IP Address

  1. Release & Renew IP address

    When you notice APIPA on your computer, fist try to release and renew the ip address from command prompt. It will prompt your computer to contact DHCP server and renew current IP address. Commands to release and renew IP address on Windows versions from XP are:

    • ipconfig/release

    • ipconfig/renew

  2. Restart your computer

  3. Assign Static IP Address

    If your laptop does not change 169.254.x.x addressing, assign static IP to it according to the network address of DHCP server. For example if the address of DHCP server is 192.168.1.1, you can assign a static IP address in between 192.168.1.2 to 192.168.1.254. You must make sure don't assign a number which is used by other devices connected to the DHCP server.

  4. Ping the default gateway. If you are getting replies, try to go online and if you don't, follow the instructions

    • Check firewall settings & turn off all firewalls including windows firewall

    • Check the configuration of all Internet security software products.

  5. Power cycle the network

    To power cycle your network, follow the instructions provided in the link below.
    How to Power Cycle a Network

  6. If still having APIPA, use Following DOS prompt Commands

    • ipconfig /flushdns

    • netsh int ip reset c:\tcp.txt

    • netsh winsock reset


Fix Automatic Private IP Addressing Issues On Wireless Laptops

If you get APIPA On wireless PC or laptop, first step is to check whether the WiFi adapter or the Access Point is the source of the issue. If other devices on the WiFi network are working fine, you can ignore the steps on Router/AP. In my experience, most of the time getting APIPA is because of the faulty wireless adapter or corrupted WiFi utility installed. In thaa case, the below steps will fix the issue.

  1. Unplug and replug Wireless adapter (USB Adapters only)

  2. Update Wireless adapter driver

  3. Uninstall and reinstall wireless adapter driver

  4. Use Windows Wireless utility to manage wireless connection

  5. Delete the preferred networks and connect again to the current wireless network. If you are not sure how to do it, visit the link below. This link explains steps to do it on Windows 8, Windows 7 and XP computers.
    How to Delete Preferred Networks

  6. Faulty WiFi Monitoring Utility

    If your wireless computer is getting APIPA due to corrupted third party WiFi monitoring utility installed comes with adapter  on your computer, you may follow the instructions provided on the link below.

    • APIPA On Windows 8 and 7

      To fix APIPA on Windows 8, Vista and Windows 7 computers, follow the instructions provided in the link below. Here you will learn how to start WLAN AutoConfig instead of third party utilities like Linksys Wireless Monitor or Dell WiFi utility.
      Start WLAN AutoConfig Service

    • APIPA on Windows XP

      If you are running Windows XP, you should follow the instructions below to override corrupted Belkin Wireless Network Monitor Utility or D-Link wireless utility.
      How to Start WZC



Some Facts about APIPA

  1. It can be useful when you do not have a DHCP server.

  2. Even though your computer is assigned an APIPA, it will try to discover DHCP server in every five minutes.

  3. Subnet mask of APIPA is 255.255.0.0 (Class B network).

  4. Computer having APIPA cannot communicate with devices in other subnets.

  5. Two computers having APIPA can communicate each other.
    How to Communicate Two Computers Having APIPA

Recommended Readings
  1. DOS Command to Start DORA

  2. What is DHCP Server & Its Working

  3. How to Fix IP Address Conflict In a Network

  4. Network Didn't Assign Valid IP Address in a Given Time. You May Not have Connectivity to Network

Technology Portal

6 comments:

Anonymous said...

It is not true that you have no connection with the 169.254.x.x address. It IS a ip address and you can reach the computers which are in the same address range (e.g. when multiple pc can not get a dhcp address assigned)

Siju George said...

This IP address is APIPA and assigned by your Windows automatically. Please read my post below.

http://www.corenetworkz.com/2009/10/communication-between-two-apipa.html

jade craft said...

how to change this in windows 7, i have reformatted hp pavillion dv9700 with new Os WIn7, my other computers are working they have the ip 192.168.x.x but this hp laptop has 169.254.x.x, the laptop can communicate trough the another computer but cannot access internet..whats wrong any one plz help :)

Admin said...

Have you tried the steps mentioned above?

khalid khan said...

@Admin.

we have 30 branches in every branch a read only DC with DHCP server service. all pc's are working fine but some times randomly one one pc taking ip from apipa when i login to server delete problematic pc record form DHCP and restart dhcp server then it is taking ip from DHCP.
please help.

Alex George said...

@Khalid,

From your message I feel that your DHCP range is not high and whenever you access the DHCP server one PC takes APIPA, am I correct ?

Try to increase the DHCP range and check if the issue persists.