self assigned ip address starts from

What is Self-Assigned IP and How to Fix it

The self-assigned IP error may prevent your Mac from connecting to the Internet. You may get an Internet connection error messages such as “Wi-Fi has the self-assigned IP address and will not be able to connect to the Internet.” If you investigate this issue further, you will see that the Network pane in System Preferences will also show a notification message saying “Self-Assigned IP” with a yellow dot instead of the regular “Connected” message under the network service, as you can see in the screenshot below. This problem may occur when Mac is connected to a wired, wireless (Wi-Fi), or hotspot connection.

This problem occurs when a self-assigned IP address is issued to network interfaces. When this issue happens, not all computers connected to the same network may be affected. For example, in the same home, one Mac may have this problem while other similarly configured Macs may have no problem at all, even though they all are using the same Wi-Fi connection. This may mean that the root of the problem is how the problem Mac is configured. Several factors may cause this issue, such as:

• Bad cable connections.
• Not getting an IP from the router or modem.
• Failure of the DHCP server.

Follow the steps below to address this problem. Please try the steps in this order. After trying each step, check to see if your problem is fixed. If it is not fixed and if you still see the Self-Assigned IP error, move to the next step.

Self-Assigned error troubleshooting steps

Check your router/modem : If you are connected over Wi-Fi, ensure that your Mac is not too far away from the router/modem.

Restart your router/modem and your Mac : You can do this easily. Simply disconnect the power cable to your router/modem. Wait 30 seconds. Then reconnect. Then restart your Mac. Click the Apple  menu and select Restart .

Renew DHCP Lease : On your Mac, open System Preferences and click on Network . Select the network service you want to connect to (e.g., Wi-Fi or Ethernet) and click on Advanced . This will open a new window. Select the TCP/IP tab and click the Renew DHCP Lease . Then click OK .

Check your connection settings : On your Mac, go to System Preferences > Network . Then select the network that shows this error and click Advanced . Select the TCP/IP tab and then make sure that “Configure IPv4” and “Configure IPv6” are set to Using DHCP and Automatically , respectively.

Then click on the DNS tab, and delete any DNS servers that are listed there. Select them one by one and click on the minus button to remove them. Do not forget to click OK and Apply when you are done.

Create a new network location : On your Mac, open System Preferences and Network . Open the Location drop-down menu and select Edit Locations . Click the plus (+) button and add a new location, give it a name and click Done . Now you have two locations: Automatic and your new location. Select this new location and then click Apply .

Now, we will add a new Wi-Fi or Ethernet service, whichever you are using. Click the plus (+) sign under the network services on the left, select the Interface (Wi-Fi, Ethernet, etc.) and name it, then click Create . Then click Apply .

Now select the Self-Assigned IP network and then click the minus (-) button to delete it. Then click Apply . Does this newly created service connect?

Reset the system firewall: We can do that by deleting its preference file . Open a Finder window and then click Go and Go to Folder from the top menu bar. Enter /Library/Preferences/ and click Go .

Once the Preferences folder is open, find the com.apple.alf.plist file. Delete this file (or place it on your Desktop; if you are not happy with what happens, you can put it back). Then restart your Mac.

Related articles

• How To Reset Network Settings On Mac
• How To Use Network Utility on Mac
• Mac Wi-Fi Connected But No Internet Access
• iPhone Will Not Connect To A Known Wi-Fi Network, Fix

Dr. Serhat Kurt worked as a Senior Technology Director specializing in Apple solutions for small and medium-sized educational institutions. He holds a doctoral degree (or doctorate) from the University of Illinois at Urbana / Champaign and a master’s degree from Purdue University. He is a former faculty member. Here is his LinkedIn profile and Google Scholar profile . Email Serhat Kurt .

Similar Posts

Fix bluetooth problems in macos catalina.

This article explains what you can do if Bluetooth isn’t working as expected on your Mac….

Why Some Apple Music Songs Are Greyed Out or Unavailable

Some Apple Music users have found that songs that were previously available to them are now…

iPhone Compass Not Working? Showing Wrong Directions? Fix

Several users have reported that The iPhone Compass app is not working properly. These are common…

How to Download macOS Installers Using Terminal

You can download full macOS installers from the command line. You may want to do this…

Apple Cash Setup Not Working, How to Fix

There are a lot of things you can do with Apple Cash. For example, you can…

What is ‘Follow Up’ in Mail on Mac and How to Turn It Off

If you use Mac’s built-in Mail app, you may have seen a banner with a “Follow…

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Categories:

How to fix self-assigned IP address issue on Mac

Is your MacBook struggling to access the internet, though your Wi-Fi or Ethernet works fine? This can be due to the self-assigned IP error on your Mac. Worry not! In this guide, I’ll share how to fix the internet not working due to a self-assigned IP address issue on your Mac to regain a stable network connection. 

But before we jump into the troubleshooting steps to resolve the issue, let’s understand what a self-assigned IP error is.

What does “self-assigned IP address” mean on Mac? 

The “self-assigned IP address” error on Mac refers to a situation where your device assigns an IP address and sets up an ad-hoc network instead of obtaining one from the network router or DHCP (Dynamic Host Configuration Protocol) server. This self-assigned IP address is not legitimate or acknowledged on the network.

That’s why your Mac cannot connect to the internet or other devices on the network, resulting in limited or no network connectivity. This issue occurs due to network configuration conflicts, DHCP server unavailability, or problems with Mac’s network or Firewall settings.

So, what to do when your Mac has a self-assigned IP address? Continue reading to get rid of the issue and restore standard network functionality on your Mac. 

• Check your connection
• Reboot your network devices
• Rejoin your Wi-Fi network
• Check your connection settings
• Reset your Network Preferences on Mac
• Renew DHCP Lease on macOS
• Create a new network location
• Reset the Firewall on your Mac
• Set Service Order from Mac’s network settings
• Change DNS Servers on macOS
• Check for conflicting IP address
• Disable VPN

1. Check your connection

Before diving into Mac-specific settings, ensure that your router is functioning correctly and located near your Mac to obtain a valid IP address. Besides, if you are using an Ethernet connection, plug in the cable snugly.  

I also check to validate that the cable has no fault and is in good condition. Moreover, If you are using an old Wi-Fi router, discard it and get a new one to obtain a smoother connection.

2. Reboot your network devices

Restarting both your modem and router can often resolve temporary network glitches. Power off the devices, unplug the cables and wait a few seconds. It will help them cool down, as excessive heat can cause malfunctions. After that, plug all cables, connect them to the power outlet, and turn them back on.   

In the meantime, restart your Mac once to iron out any bugs in macOS.   

• Click the Apple logo .

3. Rejoin your Wi-Fi network

Sometimes, simply forgetting and rejoining your Wi-Fi network can solve the self-assigned IP address error on your Mac.   

• Turn off Wi-Fi for a few seconds and toggle it on.

4. Check your connection settings

Verify that your Mac’s network settings are configured correctly. You must opt for the appropriate network settings to obtain IP addresses and DNS information automatically. 

• Go to your Wi-Fi Details .  I have shown the steps above.  
• Select TCP/IP from the left panel. 

You may also try turning off the IPv6, as some users reported it conflicted with the IP address assigning procedure.

• Click on the drop-down arrow beside Configure IPv6 . 

5. Reset your Network Preferences on Mac 

Resetting the network preferences can help eliminate IP address misconfiguration, causing the internet to not work. So, you must delete specific network connectivity-related files from your MacBook.

• Launch  Finder .

• Enter your Mac password to authenticate the deletion.
• Restart your Mac. It will automatically recreate the deleted files.
• Log in and connect to your Wi-Fi network.
• Go to the  TCP/IP  setting again and check the router files.

6. Renew DHCP Lease on macOS

This method is effective when the assigned IP address may have expired or encountered conflicts. When you renew the DHCP Lease, your Mac requests a new IP address from the DHCP server. It ensures a fresh and valid configuration and resolves connectivity issues.  

• Open the same TCP/IP tab window from Wi-Fi Details, as shown above. 

After renewing the lease, check if you can connect to your network. If that doesn’t help, try creating a New Network Location and renewing the lease.

7. Create a new network location

Creating a new network location lets your Mac start fresh with network settings and eliminate a self-assigned IP address.  

• Click the  Apple logo →  System Settings .

• Wait for a few seconds until your Mac connects to your Wi-Fi.

Repeat the steps of renewing the DHCP lease on your Mac, and then try connecting to your network.

When you try to perform configuration changes to the system, your Mac’s firewall experiences configuration issues. Let’s fix this problem by resetting the Firewall.

8. Reset the Firewall on your Mac

• In the menu bar, click  Go  → Go to   Folder .

• Restart your Mac.

After your system boots, it’ll ask you to allow access to numerous programs and services. You may choose to enable access depending upon your choice. Then, try connecting to your network and check if the self-assigned IP address error persists.

If you are unsure about deleting the Firewall files, you may temporarily disable it. Toggling off the Firewall on your Mac can help determine if it’s causing conflicts with network connectivity.

• Select  Network  from the left panel → Choose Firewall .

• Restart your Mac and turn it on again.

9. Set Service Order from Mac’s network settings 

Adjusting the service order can prioritize the network interface, ensuring your Mac connects to your preferred network. 

• Click the  Apple logo →  System Settings →  Network .

10. Change DNS Servers on macOS

Discarding existing DNS and switching to alternative DNS servers can resolve DNS-related issues that may contribute to the self-assigned IP address error.  

• Open System Settings → Wi-Fi → Click Details beside your Wi-Fi name.

• Add   these numbers: 8.8.8.8 8.8.4.4 1.1.1.1 9.9.9.9

11. Check for conflicting IP address 

Ensure that no other devices on your network use the same IP address as your Mac. Check your router’s DHCP client list and verify that all devices have unique IP addresses assigned.

12. Disable VPN 

If you have a VPN service enabled, disable it temporarily to see if it resolves the self-assigned IP address error. Open your Mac’s VPN settings and turn off the VPN connection. 

Bonus fixes 

You may need to attempt more complex fixes if the troubleshooting techniques outlined above do not fix the self-assigned IP address problem on your Mac:

• Update your Mac to the latest OS version.
• Verify your Mac is not infected with any malware or viruses. 
• Ensure your network devices are operating well and there are no hardware problems. 
• Reset NVRAM or PRAM on Mac to clear up the system settings memory. 

To use a static IP address, go to Apple logo → System Settings → Network → Wi-Fi → Details beside Wi-Fi name. Select TCP/IP → dropdown arrow next to Configure IPv4 . Choose Using DHCP with Manual Address and enter the static IP address. Click on OK to save.

Get back your smooth internet access!

Encountering a self-assigned IP address error on your Mac hampers your work, so you should address it ASAP. You can tackle the issue and restore a stable and reliable network connection using these troubleshooting techniques. If the problem isn’t resolved, contact Apple Support and seek assistance.

Explore more…

• MacBook connects to Wi-Fi but has no Internet? 12 Fixes  
• Wi-Fi not working on Mac? 10 Ways to fix!  
• How to Run Wi-Fi Diagnostics on Mac for Better Network Connections  

Readers like you help support iGeeksBlog. When you make a purchase using links on our site, we may earn an affiliate commission.  Read more .

Ava is an enthusiastic consumer tech writer coming from a technical background. She loves to explore and research new Apple products & accessories and help readers easily decode the tech. Along with studying, her weekend plan includes binge-watching anime.

After much internet searching – these clear, easy directions were a lifesaver. The second suggestion worked perfectly! Thank you!!

Thank you sooooo much !!! I was really struggling to get my Ethernet adapter to connect to my MacBook and I tried the first option and it works now!!!! God bless you and your family.

Thank you soooo much. Resetting the Firewall worked

THANK YOU!!!!! What a PITA this has been. Four hours of struggle, and your post solved the prop in seconds. I could climb through my phone and kiss you I’m so happy! Hero!

Thank you soo muchhh!!! Finally after 3 hours desperated, and you helped me 😭👍

Your directions and explanations were clear, easy to follow, and a perfect translation of technical for a layman.

Thank you very much for this fix tips!

I was ready to completely reboot my whole MPB to its factory settings. What worked best for me was your tip called: Create a new network location.

Thanks again. Remko

Yesss!! Resetting the firewall did it for me!

changing DNS worked!! thank you

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Save my name, email, and website in this browser for the next time I comment.

This site uses Akismet to reduce spam. Learn how your comment data is processed .

Stack Exchange Network

Stack Exchange network consists of 183 Q&A communities including Stack Overflow , the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.

Super User is a question and answer site for computer enthusiasts and power users. It only takes a minute to sign up.

Q&A for work

Connect and share knowledge within a single location that is structured and easy to search.

Determining the self-assigned IP address of a directly-connected counterpart

I have connected two computers, A and B, NIC-to-NIC using an ethernet cable. They have self-assigned their IP addresses—at least, I can see that A has done so, so I infer that B must have also done so. Computer A is a laptop running Windows 10, but I have no keyboard and mouse available for B. From A, how can I determine B's IP address?

On A, this is what I see:

What I've tried (based on https://serverfault.com/a/30742 ):

...which just says "Host is up" and doesn't report anybody else being on the network. I don't claim to understand what nmap is doing (for example, I have no idea what's special about the number 24) but I do know that the same command with 192.168.1.0/24 successfully finds devices on the wireless network to which A is also attached.

for example, I have no idea what's special about the number 24

It's a short way of writing the "255.255.255.0" netmask. (Also called "CIDR syntax" from its origins, or "prefix length" because it indicates that the network is specified by the first 24 bits. If you convert 255.255.255.0 from decimal to binary, you'll see it begins with exactly 24 'one' bits.)

However, your actual netmask is not 255.255.255.0 – it's 255.255.0.0, as shown in the ifconfig output. That's a /16. The whole "self-assigned" range is in fact 169.254.0.0/16.

Hosts will send out a few ARP probes as part of the self-assignment process (to ensure that the address isn't already in use). If you connect the computers while Wireshark or tcpdump is already running a capture on the Ethernet interface, you should see both of them revealing their addresses this way.

• Relative to everything else I had so far stumbled across, this is a stunningly intelligible explanation of the /24 - thanks. So I conclude that nmap -sn 169.254.0.0/16 would be the way to go. I actually managed the equivalent of that in the end by adapting one of the nmap --help examples to nmap -sn 169.254.0-255.0-255 and found the IP by letting it run for 45 minutes. In future I'll bear in mind the tcpdump tip. I presume there's no way of unilaterally configuring A to say "hey, let's self assign, but with a 24-bit prefix"? That would make it a lot quicker to find... –  jez Apr 1, 2021 at 15:39
• No, this autoconf mechanism (APIPA) is defined to always use this specific /16 prefix. However, the idea was that it would be accompanied by other Zeroconf services such as mDNS for dynamic discovery. (For example, Windows has mDNS and a few similar alternatives, so as long as both computers run Windows and have the network mode set to “private” you should be able to reach the other computer by its name without needing the exact address. Same goes for macOS and (to some extent) Linux.) –  u1686_grawity Apr 1, 2021 at 16:18
• But to answer the question, if you specifically wanted to change the prefix, you would have to run DHCP in order to do that instead of relying on autoconf. (And once you have DHCP you no longer need nmap nor tcpdump, as you can just look in the DHCP server’s “lease” table to find the address...) –  u1686_grawity Apr 1, 2021 at 16:22

You must log in to answer this question.

Not the answer you're looking for browse other questions tagged windows networking ..

• Featured on Meta
• What should be next for community events?
• Alpha test for short survey in banner ad slots starting on week of September...
• If more users could vote, would they engage more? Testing 1 reputation voting...

Hot Network Questions

• The Wug Test For Grownups
• Upper bound on absolute difference with squares
• Would the USSR invade Poland in WW2 if the Germans did not cross into previously-agreed Soviet sphere of influence?
• Earth enslaved by aliens. Last sentence of the short story gives added grimness to it
• Conditional selection in a GROUP BY clause
• How do you translate "out of all that" in an outraged or disbelieving way?
• By implementing/By having implemented new technologies, the company is going to generate more revenue. - differences in meaning
• Political purpose of Canada's prime minister publicly accusing India's government of being involved with killing a Canadian Sikh leader
• Do most conference papers get written last minute?
• Unwritten conditions to succeed in PHD program.
• How does Einstein's paper on Brownian motion actually prove atoms exist?
• Implement the RegPack decompressor
• Identify Duplos that were in the Red Bunny Purse
• "Exegesis" but for the unbeliever?
• How to know if the model is underfitting because the data is hard to model, or just the model is too simplistic?
• Write a set as a union of ranges
• Complement an infinite list
• Can a derivative of a public domain text be licensed under CC0?
• Left adjoint to the forgetful functor from Hilbert spaces to topological spaces
• When casting a spell that lets you distribute X +1/+1 counters among creatures you control, how do you submit less than X creatures?
• LED circuit seems to defy Ohm's law. Of course it’s something else
• Is catechin an ingredient, a composition, or a compound of green tea?
• How to to create lines from points where the point attributes are transferred to the line segments?
• Identification of shiny metallic blocks on the PCB

Your privacy

By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy .

• Have Tech, Will Travel
• iPhone 15 Price, Features & More

How to Fix a 169 IP Address Error

Having trouble reaching your DCHP servers? There are ways around that

• Shoreline Community College

• The Wireless Connection
• Routers & Firewalls
• Network Hubs
• Installing & Upgrading
• Wi-Fi & Wireless

When you can't connect to the internet , and your computer seems to have an IP address that starts with 169, there's a simple explanation. This type of error happens when a Windows computer requests an IP address and doesn't receive one. To fix this sort of 169 IP address error, your computer must be able to obtain a valid IP address from your network.

Causes of 169 IP Address Error

For a computer to access the internet through a network, it needs a valid IP address. The easiest way to make sure this happens seamlessly is through the Dynamic Host Configuration Protocol (DHCP), which is a setting that allows the router to automatically assign an IP address to each device on the network.

When a Windows computer isn't able to communicate with the DHCP server, something called Automatic Private IP Addressing (APIPA) kicks in. It assigns the computer an IP address that starts with 169.254. These IP addresses are only useful on local networks, not the internet.

Without communication between the computer and the DHCP server, and as long as the computer has a 169 IP address, it can't connect to the internet. That's why the fix for this problem involves making sure your computer and the DHCP server can communicate. When that happens, the problem basically fixes itself.

To fix an error where your computer has an invalid IP address that starts with 169, you need to make it so that the networking device in your computer is able to communicate with your network hardware .

Depending on the reason you experience this error, you may be able to accomplish this by resetting the network hardware, telling the networking device in the computer to request a new IP address, or changing some settings in the router .

Power cycle the network hardware . Turn off and unplug your modem and router, and then plug both devices back in. When the network hardware starts back up, and your computer attempts to reconnect to the network, it may be able to obtain a valid IP address.

Use the Windows networking troubleshooter . This automated process takes care of most networking problems, including ones that prevent a computer from obtaining a valid IP address.

Request a new IP address . This is a little more complicated because you need to open a command prompt and enter a series of commands. In most cases, this allows the computer to obtain a valid IP address.

Check the DHCP settings in the router . There are two ways that a router can assign IP addresses. Either the router dynamically assigns a unique IP address to each device, with no input from you, or you must assign a unique static IP address to each device manually.

DHCP is the setting that allows a router to assign IP addresses dynamically. If this setting is turned off, and you haven't set a static IP address for the computer, you won't be able to access the internet.

Disable the router . In some cases, you can fix this type of problem by disabling the networking device and then re-enabling it, or by uninstalling and reinstalling the driver. These are similar processes that both require you to access the Windows Device Manager .

An IP address , short for Internet Protocol address, is an identifying number for network hardware connected to a network. Having an IP address allows a device to communicate with other devices over an IP-based network like the internet.

DHCP using automatic IP address assignment means the same device may have different addresses over time, and there are some reasons you might not want this. To disable DHCP on a Windows computer, press the  Windows + x  keys and click  Settings > Network & Internet > Select a connection > Properties > Edit  to access DHCP settings.

A static IP address is an IP address that is manually configured for a device instead of one that is assigned by a DHCP server. It's called static since it doesn't change, unlike a a dynamic IP address that does change.

Get the Latest Tech News Delivered Every Day

• What Is an IP Address?
• Cisco Default Password List
• What Is a Dynamic IP Address?
• What Is a Private IP Address?
• “Failed to Obtain IP Address”: How to Fix an IP Configuration Failure on Android
• How to Properly Restart a Router & Modem
• NETGEAR Default Password List
• How to Fix the PS4 'Cannot Connect to the Wi-Fi Network' Error
• DNS Servers: What Are They and Why Are They Used?
• How to Change Your IP Address
• How to Use the Ping Command for Testing in Windows
• Troubleshooting Xbox One Network Failures
• How to Find Your IP Address in Windows
• What Is a Router and How Does It Work?
• How to Resolve Limited or No Connectivity Errors in Windows
• How to Change the IP Address on Your Android

By clicking “Accept All Cookies”, you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts.

• Skip to primary navigation
• Skip to main content
• Skip to primary sidebar

Technology Simplified.

Self-Assigned IP Address Error on Mac: How to Fix?

By: Waseem Patwegar

If Wi-Fi or Ethernet is not working on your MacBook due to “Self-Assigned IP Address” error, you can find below the steps to restore network connectivity on your Mac.

Self-Assigned IP Address on Mac

In a typical case of this nature, the MacBook appears to be connected to the Network (WiFi or Ethernet), but it fails to load webpages and comes up with “Self-Assigned IP” error.

As indicated by the wordings (Self-Assigned IP Address), the reason for this problem is due to your Mac Assigning itself an IP Address that is not valid or not recognized on the network.

Luckily, in most cases the problem of No Internet connectivity due to “Self-Assigned IP Address” can be fixed by rebooting the modem.

1. Power Cycle Modem/Router

Before going ahead with other methods, simply disconnect the Modem/Router from its power supply source > wait for 60 seconds and reconnect the Modem/Router back to its power supply.

After this, you should find internet working properly on your Mac, as it starts using a valid IP Address on both WiFi and Ethernet to connect to the network.

2. Renew DHCP Lease

1. Click on Apple Logo in the top menu-bar and select System Preferences… in the drop-down menu.

2. On System Preferences screen, click on the Network Icon.

3. On Network screen, select your Network ( Ethernet or WiFi ) in the side-menu and click on Advanced .

4. On the next screen, switch to TCP/IP tab and click on Renew DHCP Lease button.

5. Click on OK to save the revised settings.

After the DHCP lease is renewed, you should be able to connect to internet

3. Delete PLIST Files

The problem of No Internet on Mac due to Self-assigned IP Address can be fixed by removing certain files related to network connectivity on your computer.

1. Click on the Finder Icon in taskbar > click on the Go tab in top-menu bar and select Go to Folder option in the drop-down menu.

2. In Go-to window, Type /Library/Preferences/SystemConfiguration/ and click on the Go button.

4. In System Configuration folder, delete the following folders (right-click on the Folders and move them to trash).

• com.apple.airport.preferences.plist
• com.apple.network.identification.plist
• NetworkInterfaces.plist
• Preferences.plist

Note: Your Mac will automatically recreate above Folders when it restarts.

5. Shutdown the MacBook > Wait for 30 seconds and Restart the Mac again and see if you can now connect to the internet.

4. Set Service Order

Make sure that your MacBook is always connecting to your preferred network type (WiFi or Ethernet).

1. Click on Apple Logo > System Preferences > Network > On the Network screen, click on the Gear icon and select Set Service Order option in the drop-down menu.

2. On Service Order window, drag your preferred Network (WiFi or Ethermet) to the top position.

3. Once you are done, click on OK to save the changes.

5. Create New Network Location

If you are still unable to connect to Internet, create a New Network Location on your Mac and renew its DCHP lease.

1. Click on Apple Logo > System Preferences > Network > On the Network screen, open the Location menu and select Edit Locations option.

2. On the next screen, click on the Plus icon to Add New Location.

3. On the next screen, type a Name for the New Network Location and click on Done .

4. After creating new location, select either WiFi or Ethernet in the side menu and click on Advanced .

5. On the next screen, switch to TCP/IP tab and click on Renew DHCP Lease .

6. Click on OK to save the new settings.

This should certainly fix “Self-Assigned IP Address problem and restore network connectivity on your Mac.

6. Switch to Google DNS

If your Mac is frequently struggling from Network connectivity issues, the problem might be due to the DNS Servers of your Internet Service provider being busy and clogged up.

To fix this issue, you can consider switching the DNS servers on your Mac to Google DNS or Open DNS.

• Tips to Speed Up Slow MacBook, Mac Mini and iMac
• How to Speed Up Slow Safari Browser on Mac

Stack Exchange Network

Stack Exchange network consists of 183 Q&A communities including Stack Overflow , the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.

Server Fault is a question and answer site for system and network administrators. It only takes a minute to sign up.

Q&A for work

Connect and share knowledge within a single location that is structured and easy to search.

workstation getting self-assigned IP after static IP configured

SO I have a client whos DC went down. With it offline I went ahead and assigned static IP's to all workstations (win 8.1) so they would still have internet and recreated a file-share off of a single workstation. They are up and running with one problem. 2 of the workstations will not take a static IP. I'll configure them, bounce the system and ipconfig only to see a self-assigned ip. I've reset TCP/IP on the box as per this doc from MS. I've updated the drivers for the NIC. I'm stumped. This is working just fine for other workstation on the network. Although as a side note, all system have the networks classified as a public network.

• 1 Did you by accident configure both machines to the same IP? That was the reason I had this problem last time, duplicate IPs. –  Gerald Schneider Oct 20, 2016 at 12:58
• I want to say no because but I'm going to check again just to make sure. –  brooksly Oct 20, 2016 at 13:10
• 1 You know sometime when you are so confident in something you end up looking foolish. It was a dup from the phone system, thanks for the clear thought! –  brooksly Oct 20, 2016 at 13:31

Make sure the IP address you assign isn't already in use.

Windows uses a self assigned IP address even though a static address is assigned when duplicate IP addresses are in use on the network.

You can check this by running ipconfig on the command line, the IPv4 address line will have (duplicate) after the static IP address if this is the case.

You must log in to answer this question.

Not the answer you're looking for browse other questions tagged windows networking static-ip ..

• Featured on Meta
• What should be next for community events?
• Alpha test for short survey in banner ad slots starting on week of September...
• If more users could vote, would they engage more? Testing 1 reputation voting...

Hot Network Questions

• How can I get my engineers to accept being on call?
• Do you think evil people are conducting according to principles that are legitimate in their own system of values?
• Conjugacy classes in towers of groups
• Pronunciation of Ancient Greek sigma as voiced [z] before voiced consonants
• By implementing/By having implemented new technologies, the company is going to generate more revenue. - differences in meaning
• "Exegesis" but for the unbeliever?
• How far deep in the mantle has any rock ever been brought to the surface? Have scientists found anything they believe originated in the outer core?
• What distinguishes the people who get academic jobs from the people who don't?
• E-bike motor stopping momentarily during steep climbs
• How can I improve insulation on a lower level floor without modification?
• Independent t-test formula
• How to know if the model is underfitting because the data is hard to model, or just the model is too simplistic?
• Is every house vote taken one vote at a time?
• Girth 5 graphs with diameter 2
• When casting a spell that lets you distribute X +1/+1 counters among creatures you control, how do you submit less than X creatures?
• What do these clearances by Heathrow Director mean?
• What is an "attosecond pulse", and what can you use it for?
• Potential energy in an ideal spring compressed from both sides
• Is there a way to extend the analogy that fractions means "x out of y" to show that fractions are also dividing?
• Jury-rig second monitor on school lectern?
• Write a set as a union of ranges
• 2 lines 1 plane question in 3 dimension
• How does Einstein's paper on Brownian motion actually prove atoms exist?
• What does this Peter Sellers sentence mean?

Your privacy

By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy .

How to Solve the Self-Assigned IP Error on Macs?

Have you ever encountered the frustrating “self-assigned IP address” error on your Mac? If so, you're not alone. This common issue can cause your internet connection to fail, leaving you unable to browse the web or access online services. But fear not, as there are several steps you can take to fix this problem and get your Mac back online.

1. Reset your network preferences: Sometimes, network settings can become corrupted, leading to the self-assigned IP address error. To fix this, you can reset your network preferences by following these steps:

– Click on the Apple logo in the menu bar and select “System Preferences.” – Find and go to the “Network” settings. – Select your Wi-Fi or Ethernet connection, if it's not selected automatically. – Click on the “Advanced” button. – Go to the “TCP/IP” tab. – Click on the “Renew DHCP Lease” button. – Restart your Mac and check if the issue is resolved.

2. Create a new network location: If resetting your network preferences didn't work, you can try creating a new network location. This will create a fresh set of network settings, which may help resolve the self-assigned IP address error. Here's how to do it:

– Open the “Network” settings as mentioned above. – Click on the “Location” drop-down menu and select “Edit Locations.” – Click on the “+” icon to create a new location. – Give it a name (e.g., “New Location”) and click “Done.” – Select your new location from the drop-down menu and apply the changes. – Restart your Mac and check if the issue is resolved.

3. Reset the firewall on your Mac: In some cases, the firewall settings on your Mac can interfere with the network connection and cause the self-assigned IP address error. To reset the firewall, follow these steps:

– Open “System Preferences” and go to the “ Security & Privacy ” settings. – Click on the “Firewall” tab. – Click on the lock icon and enter your administrator password. – Click on the “Turn Off Firewall” button. – Restart your Mac and check if the issue is resolved.

4. Set Service Order from Mac's Network settings: Another potential solution is to change the service order of your network connections. Here's how to do it:

– Open the “Network” settings. – Click on the gear icon and select “Set Service Order.” – Drag your Wi-Fi or Ethernet connection to the top of the list. – Click “OK” and apply the changes. – Restart your Mac and check if the issue is resolved.

5. Change DNS servers on macOS: DNS (Domain Name System) servers translate domain names into IP addresses, allowing your Mac to connect to websites. Sometimes, changing the DNS servers can help resolve the self-assigned IP address error. Here's how:

– Open the “Network” settings. – Select your Wi-Fi or Ethernet connection. – Click on the “Advanced” button. – Go to the “DNS” tab. – Click on the “+” icon to add a new DNS server. – Enter the following DNS server addresses: 8.8.8.8 and 8.8.4.4 (these are Google 's public DNS servers). – Click “OK” and apply the changes. – Restart your Mac and check if the issue is resolved.

By following these steps, you should be able to fix the self-assigned IP address error on your Mac and regain your internet connection. However, if the problem persists, it may be worth contacting your internet service provider or seeking further assistance from a professional technician.

How Do You Stop Your Mac From Self Assigning IP Address?

To fix the self-assigned IP error on your Mac, follow these steps:

1. Reset your network preferences on Mac: – Open the “System Preferences” on your Mac. – Click on “Network.” – On the left-hand side, select the network connection you are using (e.g., Wi-Fi or Ethernet). – Click on the minus (-) button to remove the connection. – Confirm the action by clicking on “Apply” or “OK.” – Restart your Mac.

2. Renew DHCP lease on macOS: – Go to “System Preferences” and click on “Network.” – Select the network connection you are using (e.g., Wi-Fi or Ethernet). – Click on the “Advanced” button. – Go to the “TCP/IP” tab. – Click on the “Renew DHCP Lease” button. – Close the window and restart your Mac.

3. Create a new network location: – Open “System Preferences” and click on “Network.” – Select the network connection you are using (e.g., Wi-Fi or Ethernet). – Click on the “Location” drop-down menu and choose “Edit Locations.” – Click on the plus (+) button to create a new location. – Name the new location and click “Done.” – Apply the changes and restart your Mac.

4. Reset the firewall on your Mac: – Open “System Preferences” and click on “Security & Privacy.” – Go to the “Firewall” tab. – Click on the lock icon and enter your administrator password. – Click on the “Firewall Options” button. – Click on “Restore Defaults” or “Allow incoming connections.” – Apply the changes and restart your Mac.

5. Set Service Order from Mac's Network settings: – Open “System Preferences” and click on “Network.” – Click on the gear icon and select “Set Service Order.” – Drag the network connection you are using (e.g., Wi-Fi or Ethernet) to the top of the list. – Close the window and restart your Mac.

6. Change DNS servers on macOS: – Open “System Preferences” and click on “Network.” – Select the network connection you are using (e.g., Wi-Fi or Ethernet). – Click on the “Advanced” button. – Go to the “DNS” tab. – Remove any existing DNS servers by clicking on the minus (-) button. – Add new DNS servers by clicking on the plus (+) button and entering the server addresses (e.g., 8.8.8.8, 8.8.4.4 for Google DNS). – Click “OK” and apply the changes.

By following these steps, you should be able to resolve the self-assigned IP error on your Mac and establish a proper network connection.

How Do You Fix Your Self-Assigned IP Address On Your Mac Ethernet?

To fix a self-assigned IP address issue on your Mac Ethernet, you can follow these steps:

1. Click on the Apple logo in the menu bar and go to “System Preferences.” 2. In the “System Preferences” window, find and click on “Network.” 3. From the list of network connections on the left side, select your Ethernet connection. 4. Make sure that the Ethernet connection is selected and click on the “Advanced” button. 5. In the “Advanced” settings, go to the “TCP/IP” tab. 6. If the “Configure IPv4” dropdown menu is set to “Using DHCP,” change it to “Manually.” 7. Now, click on the “Renew DHCP Lease” button to release the current IP address. 8. After that, click on the “Apply” button to save the changes. 9. If you want to use specific DNS servers, go to the “DNS” tab and click on the “+” icon. 10. Add the desired DNS server addresses, such as 8.8.8.8 and 8.8.4.4, and click on “OK.” 11. click on the “Apply” button again to save the DNS server changes.

By following these steps, you should be able to fix the self-assigned IP address issue on your Mac Ethernet connection.

What Are The Self Assigned IP Address Ranges?

Self-assigned IP addresses, also known as Automatic Private IP Addressing (APIPA), are utilized by client computers when they are unable to obtain an IP address from a DHCP server. In such cases, the client computer will automatically assign itself an IP address from a specific range of addresses known as the APIPA range.

The self-assigned IP address ranges are as follows:

– 169.254.0.0 to 169.254.255.255

When a client computer activates APIPA and is unable to connect to a DHCP server, it will randomly select an IP address from this predefined range. It does this to ensure that it can still communicate on the local network, even without a valid IP address assigned by a DHCP server.

It is important to note that self-assigned IP addresses are only meant for local network communication and cannot be used for internet connectivity. These addresses are not routable on the internet, hence they are primarily used as a temporary solution until the client computer can obtain a valid IP address from a DHCP server.

The self-assigned IP address ranges are from 169.254.0.0 to 169.254.255.255, and they are automatically assigned by client computers when they are unable to obtain an IP address from a DHCP server.

A self-assigned IP address, typically in the range of 169.254.x.x, is an indication that your device, in this case, a Mac computer, was unable to obtain an IP address from the router or DHCP server. This issue can prevent your device from connecting to the internet or communicating with other devices on your network.

To fix this problem, there are several troubleshooting steps you can follow. Firstly, resetting your network preferences can help resolve any configuration issues that may be causing the self-assigned IP address problem. Renewing the DHCP lease is another option, as it forces your Mac to request a new IP address from the router.

If these initial steps don't work, creating a new network location can help by resetting all network settings to their default values. Resetting the firewall on your Mac can also be beneficial, as it may be blocking the necessary network connections.

Additionally, adjusting the service order in the network settings can ensure that your Mac prioritizes the correct network connection. Changing the DNS servers can also be helpful, as sometimes incorrect DNS settings can lead to self-assigned IP address issues.

By following these troubleshooting steps, you should be able to resolve the self-assigned IP address error on your Mac and regain normal network connectivity. Remember to consult the specific instructions for your macOS version for accurate guidance.

Related posts:

Sanjeev Singh

Stack Exchange Network

Stack Exchange network consists of 183 Q&A communities including Stack Overflow , the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.

Ask Different is a question and answer site for power users of Apple hardware and software. It only takes a minute to sign up.

Q&A for work

Connect and share knowledge within a single location that is structured and easy to search.

What does this mean: "Wi-Fi has the self-assigned IP address...& will not be able to connect to the Internet"?

I have internet access but I noticed that in System Preferences/Network, although the W-Fi status is "On" this statement is below: "Wi-Fi has the self-assigned IP address XXX.XXX.X.XX and will not be able to connect to the Internet." There is a yellow dot preceding the "Wi-Fi / Self-Assigned IP" icon on the far left of the System Preferences/ Network window. The Network Diagnostics shows all the items under Network Status as green. My modem does not have a router. It is behind a Verizon (ISP) router that I do not physically own or have access to. I can only access the settings at: "my home.modem manufacturer's name.com". Is this still a problem that needs correcting? Thank you.

UPDATE: My ISP says: "Okay that's the issue as it is a 6100 modem it does not have a feature or wireless option you need to get one wireless router from ups store...I will send you a free modem which is an advanced one.."

MacBook Pro with Retina display, OS X Mavericks (10.9.5), MacBookPro11,3; Airport Time Capsule

• 2 If (for whatever reason) no IP address is assigned to it from outside, your computer will make up an IP address for its Wi-Fi to use locally. So I'm guessing you should use Airport Utility and examine what is going on in your Airport Time Capsule. –  GEdgar Dec 26, 2015 at 2:12
• Your network hardware information is a bit vague. It is unclear which device provides the wifi for your device: is it your 'modem' connected to the Verizon router or the Verizon router itself? Have you powered cycle your 'modem'? Have you asked the owner of the Verizon router to power cycle the router? Sometimes, simple net connection glitches are fixed with a flick of the power switch. –  IconDaemon Dec 26, 2015 at 2:45
• OP mentions no Time Capsule device - the yellow dot is in System Preferences > Network, indicating that the router serving a usable IP address is not working. –  IconDaemon Dec 26, 2015 at 2:48
• Maybe it is an edit (but I don't see a history) but OP has Time Capsule listed last in hardware list. –  bjbk Dec 26, 2015 at 3:21

2 Answers 2

So there are two things happening when a wifi device wants to use "internet". First it has to join the wifi network using an AP (access point) If there is a password like WPA that needs to be supplied. Next the device needs to get an IP address. That information comes from a router. It is not always necessarily true that the router and AP are the same piece of equipment. If the IP address acquisition (typically via DHCP) fails or times out the device will assign itself an IP from 169.254.X.X. However this IP can never talk to the Internet and the device knows that so that's why the message is provided. Sometimes this is simply resolved via a reboot of the router, but it could also be a hardware failure, especially if the AP and router are two separate devices.

I would check Airport Utility to see what the problem is. If there is a yellow dot by the Time Capsule, that means that it is not properly connecting to the Internet. This means either the Ethernet cable is loose, or it is not configured properly. Try checking all cables or restarting the router, or try to reconfigure the Airport. If all fails, see this guide on Apple's website on resetting/troubleshooting the router.

If the Internet bubble is yellow and the Time Capsule is green, then your router is messed up and you need to contact the owner to reset it.

Hope that helps.

• Hmm. I was under the impression OP used the Airport Time Capsule for wifi. Then it would appear resetting the router would help. –  SentientBacon Dec 26, 2015 at 2:49
• The first comment (by GEdgar) to the OP inserted a non-existant Time Capsule into the mix. I agree that resetting the Verizon router, and whatever the 'modem' is, will be a good first step in attempting a fix. –  IconDaemon Dec 26, 2015 at 2:52
• Airport Time Capsule was there in the original post. It is at the very end. –  GEdgar Jul 23, 2016 at 14:37

You must log in to answer this question.

Not the answer you're looking for browse other questions tagged wifi ..

• Featured on Meta
• What should be next for community events?
• Alpha test for short survey in banner ad slots starting on week of September...
• If more users could vote, would they engage more? Testing 1 reputation voting...

Hot Network Questions

• PhD Advisor Slander to Postdoc PI
• How does Einstein's paper on Brownian motion actually prove atoms exist?
• ImportError: cannot import name 'url_quote' from 'werkzeug.urls'
• Potential energy in an ideal spring compressed from both sides
• How to know if the model is underfitting because the data is hard to model, or just the model is too simplistic?
• Table stability
• Why doesn't share movement match difference between open and close?
• E-bike motor stopping momentarily during steep climbs
• Conjugacy classes in towers of groups
• "Exegesis" but for the unbeliever?
• Pronunciation of Ancient Greek sigma as voiced [z] before voiced consonants
• Identify Duplos that were in the Red Bunny Purse
• Do you think evil people are conducting according to principles that are legitimate in their own system of values?
• A perforated ding dong surface
• Does Coolant Actively Circulate Through Overflow Reservoir?
• Jury-rig second monitor on school lectern?
• Do most conference papers get written last minute?
• Sodium borohydride and lithium aluminium hydride
• Write a set as a union of ranges
• Is there an increase in whale deaths due to windfarms?
• What does it mean to "publish machine code"?
• Cartoon: girl with blue skin can phase through walls
• What distinguishes the people who get academic jobs from the people who don't?
• Adapting a 4-jaw drill chuck to hex shanks?

Your privacy

By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy .

• Home Entertainment
• Services & Software
• Credit Cards
• Cryptocurrency
• Home Internet
• Home Security
• Kitchen & Household
• Energy & Utilities
• Yard & Outdoors
• Personal Care
• Mental Health
• News & Culture
• Social Media
• Misinformation
• Internet Culture
• Entertainment
• Deals & Reviews
• Best Products
• Shopping Extension
• Car Accessories
• Car Reviews
• Vistaprint Coupons
• StubHub Discount Codes
• H&M Coupons
• ExpressVPN Coupons
• Home Depot Coupons
• Office Depot Coupons
• Ashley Furniture Coupons
• Samsung Promo Codes
• NordVPN Coupons
• Surfshark Coupons
• Shutterfly Promo Codes
• Zenni Optical Promo Codes
• Hotels.com Coupons
• Walmart Promo Codes
• Booking.com Promo Codes
• Hotwire Promo Codes

Fix self-assigned IP addresses in OS X

One common issue that has affected OS X systems is when network interfaces are issued a self-assigned IP address. Here is how to address this problem.

One common issue that has affected OS X systems is when network interfaces are issued a self-assigned IP address, even though the system is connected to a network with a properly configured DHCP server. When this happens, other systems on the same network (often including similarly configured Macs) will be working just fine, indicating the problem lies with the Mac's configuration and is not a compatibility issue with the networking hardware.

Often when I encounter this issue, I find that people have recently made a relatively major configuration change to their systems, either by updating their OS version, performing an upgrade to another major release of OS X, migrating to a new system, or have just restored their systems from backup. Initial attempts to address the problem include creating new network locations to refresh the network port configurations, or manually refresh the DHCP lease to force a reconfiguration for the port. While these are good attempts, many times they do not fix the problem.

The reason OS X issues self-assigned IP addresses is to allow a network interface to create an ad-hoc network if needed, without the presence of an established network. However, this is only done if the network port detects a proper hardware connection but cannot communicate with the DHCP server to obtain an IP address. Usually the main culprit for this is configuration problems with the system's firewall.

When people perform major configuration changes to their systems, sometimes the settings may not migrate properly. One that seems particularly vulnerable to odd problems is the system firewall. Luckily the fix is a relatively easy one; all you have to do is remove the firewall's preferences and then reboot the system.

To reset the firewall, go to the /Macintosh HD/Library/Preferences/ folder and remove the file called "com.apple.alf.plist," and then restart your computer. After the system boots, you may be prompted to allow incoming connections to numerous programs and services, so accept these for now (you can always go to the Firewall settings and deny or remove entries later on) and then try connecting to the network again. While configuration changes from migrating or restoring a system can lead to this problem, at other times major system crashes or power outages can do the same.

Questions? Comments? Have a fix? Post them below or e-mail us ! Be sure to check us out on Twitter and the CNET Mac forums .

Computing Guides

• Best Laptop
• Best Chromebook
• Best Budget Laptop
• Best Cheap Gaming Laptop
• Best 2-in-1 Laptop
• Best Windows Laptop
• Best Macbook
• Best Gaming Laptop
• Best Macbook Deals

Desktops & Monitors

• Best Desktop PC
• Best Gaming PC
• Best Monitor Under 200
• Best Desktop Deals
• Best Monitors
• M2 Mac Mini Review

Computer Accessories

• Best PC Speakers
• Best Printer
• Best External Hard Drive SSD
• Best USB C Hub Docking Station
• Best Keyboard
• Best Webcams
• Best Laptop Backpack

Photography

• Best Camera to Buy
• Best Vlogging Camera
• Best Tripod
• Best Waterproof Camera
• Best Action Camera
• Best Camera Bag and Backpack

Tablets & E-Readers

• Best E-Ink Tablets
• Best iPad Deals
• Best E-Reader
• Best Tablet
• Best Android Tablet

3D Printers

• Best 3D Printer
• Best Budget 3D Printer
• Best 3D Printing Filament
• Best 3D Printer Deals

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Self Assigned IP address - How do I get rid of it?

I have an apple extreme base station. I subscribe to Optimum Online internet. I connect the two, and I am getting a self assigned IP address, which starts with a 169, and obviously does not connect to the internet. I have changed locations, reset the extreme base station, renewed the DHCP - nothing works. How can I get rid of this self assigned IP? Of course, Optimum says its not a "problem they deal with". HELP. ***** cause I got a new TV and I wanna connect it to the ethernet on the airport extreme! But the Self Assigned IP is killing me...

Posted on May 17, 2011 6:51 PM

Loading page content

Page content loaded

May 17, 2011 6:55 PM in response to Marco Meneses 11

Can you confirm that you have an Ethernet cable connecting the Optimum device to the WAN port on the AirPort Exteme.....and that the AirPort Extreme has been configured in Bridge Mode?

May 17, 2011 6:56 PM in response to Bob Timmons

Hi there. Yes, ethernet cable connecting the Optimum internet jack to the WAN port on the extreme. No - the airport is NOT on bridge mode. Should it be?!?

May 17, 2011 7:00 PM in response to Marco Meneses 11

I am assuming the Optimum device is a gateway/router, correct?

Open AirPort Utility - Click Manual Setup

Click the Internet icon

Connection Sharing = Off (Bridge Mode)

Then restart your entire network, gateway first, then AirPort Extreme, etc.

May 17, 2011 7:05 PM in response to Bob Timmons

Shouldnt it be on share a public IP address? Bridge mode will just pass along the 169 self assigned IP...won't it?

May 17, 2011 7:09 PM in response to Marco Meneses 11

It should be on "Share" if you are connecting to a simple modem ....not a gateway or router.

Can you provide some details about the Optimum device? A link, perhaps?

May 17, 2011 7:12 PM in response to Bob Timmons

First of all - thanks for your help. I do appreciate it. As I have a brand new LED TV that I want to hardwire and it won't work! Annoying...

Anyways - I live in a pre-wired community. The whole building uses optimum online, so there are no "modems" in my unit - just jacks - like phone jacks - that say DATA.

If I hardwire my mac into the wall - the jack gives me a self assigned IP address. Won't work.

Right now, I have an aiport EXPRESS connected to the jack. This for some reason works.

If I switch out to my spare airport EXTREME (so that I can use one of the ethernet ports to wire the TV) - then the self assigned IP address comes through on the extreme - and it does not work.

Does that make sense?

May 17, 2011 7:19 PM in response to Marco Meneses 11

I understand what you are saying, thanks. But the behavior of the devices does not make sense.

Your computer, AirPort Express and AirPort Extreme should all be able to connect to the Ethernet jack on the wall.

Anytime you plug a router (the AirPort Express and AirPort Extreme are routers) into a network like you have, the correct configuration is Bridge Mode. If you configure the Express or Extreme to act as a router in the "Share a public IP address" setting, then you have 2 routers in series, both trying to handle DHCP and NAT, which invariably causes a conflict....and no connection.

I cannot understand why your computer will not connect if connect it directly to the wall jack. Are you restarting the computer / device each time you make a change?

May 17, 2011 7:20 PM in response to Bob Timmons

Me neither man. And what is annoying is that for "some reason" the airport EXPRESS actually DOES work. If I could replicate that on the Extreme, I'd be set. But IT JUST WON't WORK - as the self assigned IP does not go away!

May 17, 2011 7:39 PM in response to Marco Meneses 11

This is beginning to sound like the main router at the facility "registers" or "authorizes" the device that is connected to the wall jack. And, it picked up the AirPort Express for authorization....and won't authorize another device until someone or something tells it to. A lot of college dorm networks work this way.

I think you will need to talk to the IT guy in charge of the network to get things figured out.