Self assigned IP Address, wireless doesn't work

After upgrading to Leopard I keep getting "AirPort has a self-assigned IP address and may not be able to connect to the Internet." when I try to connect to the wireless network. Thus, wifi does not work at all. I've researched it best I can and it seems to be a problem with the router assigning an IP address to the mac, but why didn't this happen in Tiger? However if I play around with it for awhile it will randomly start working, but the same method doesn't fix it everytime. It also works fine in bootcamp. If I physically plug into the router, it works fine. This problem didn't exist in Tiger at all.
Message was edited by: SuperDupe453

Follow-up:
On the two laptops, I finally managed to get on line by switching to a different wireless access point, on a different modem. I surmise that the communication between the Macbook DHCP client and the modem/router's DHCP server is less than 100% effective. Looking at the modem/router, I could see that all of the Macs had active connections. But, instead of showing the names of the Macs, the page showed a star (*) for each Mac. I had to compare Mac addresses to verify the connections. The MAC address, of course, is hard-wired into the computer's network interface. It appears that either the DHCP client didn't know what question to ask when it broadcast for an IP address, or it couldn't interpret the answer. Except in the case of the iMac, which worked perfectly.
I upgraded the MacPro last, since it is my primary machine. Same story--connection with self-assigned address, which is useless. However, this time, having nothing left to lose, I restarted the modem/router, which presumably dumped any inactive connections and issued new DHCP leases.
However, I do have a few words for the Apple GENIUSES! The Leopard network preferences page puts me in mind of a maintenance free battery. A few of the older folks will remember when you bought a car battery that had to be filled with distilled water to reconstitute the electrolyte. Then, periodically, you check the level of the liquid in the battery, and added distilled water when required. Adding water was required on occasion because some of the water would boil off under certain conditions. Then, we got the maintenance free battery, which is virtually identical to the older battery design, except that you don't have to perform the maintenance of replenishing the water. It turns out, however, that maintenance free batteries do vent on occasion, and should have water added. But, you can't add water because the battery is sealed. So, the difference between conventional and maintenance free is not that the maintenance free battery doesn't need maintenance, it is that you can't perform the maintenance without voiding the warranty.
The Leopard network preference page won't let you set the parameters that could restore a connection. If the DHCP client doesn't work automatically, you're stuck.

Similar Messages

DHCP & self-assigned IP problem-Airport doesn't work

I'm not really a technical type, but I'm pretty quick to pick things up and several weeks of trying to deal with this issue has made me pretty knowledgeable about things related to it specifically.
Background:
I have a month-old Macbook Pro that runs Snow Leopard and is up to date on all its software stuff. On our home network we have another pretty new Macbook Pro running 10.5.9 and a fairly old Macbook also running 10.5.9.
We have a Linksys WRT54G wireless router. Our network uses a 40-bit Hex WEP password.
Problem(s):
When I try to connect to our wireless network, Network preferences tells me that it cannot connect because of a self-assigned IP address. Sure enough, the IP address DHCP comes up with is of the 64.XX.XX.XX variety. Google's revealed that this is a common problem for all recent versions of OSX, back to at least Tiger.
The "subnet mask" it comes up with is 255.255.0.0, which is different from the settings on our other (working) computers, which is 255.255.255.0. I'm not sure what this means, or whether it's significant. Renewing the DHCP lease either comes up with the same 64.XX.XX.XX type or, sometimes, it comes up with no IP settings at all. The most frustrating thing about this is that if I chose "DHCP with manual address" and type in any in our set that I've confirmed isn't in use and hit "apply", as soon as I go back to the panel it has reverted to the 64.XX.XX.XX type.
I've also tried manually entering the router/subnet mask/IP data, as well as the DNS numbers, and that leads to the Network Settings connectivity dot thing being green, but the internet still doesn't work. In those cases, diagnostics claims that everything is fine up to and including the ISP, but that it's unable to connect to the server and internet.
Of note: some people with a similar problem have talked about networks with this problem working intermittently, but mine seems to be consistently broken.
Initially I was able to avoid fixing the problem by using our neighbors' unsecured wireless network, which is sort of awful, I know, but at least it kept me from having to deal with this for a while. Today it started to do the same thing to that network. Both networks continue to work on our Macbook and other Macbook Pro, which is why I don't think that it's a router problem.
I've been able to connect to our other computers through computer-to-computer networks—going through our main shared network (and thus the wireless router) doesn't seem to work—which I think shows that the Airport card/hardware itself is intact (?). I did try connecting to the internet through the "internet sharing" option on our Macbook, but that had the exact same problems.
Another thing that may or may not be relevant, but is equally infuriating:
I've also noticed that my Macbook Pro has more trouble staying connected to a network than our Macbook—even when it was working, it disconnected/timed out extremely often, which is something our Macbook never does, even from the same location. When I try to connect to a network it spends a very long time displaying the "searching for network" animation in the menu bar icon, sometimes after the Network Preferences pane believes that it's connected, and sometimes even after I hit the button to turn Airport off. It's also started refusing to connect to any networks at all, on occasion, which is especially evident in the process of the diagnostics box thingy, because there it actually tells me it's unable to connect rather than just playing the searching animation for ages.
Here are some other things that I've tried:
setting up a new 'location'
restarting the computer
deleting the airport preferences file
restarting in safe mode
restarting open firmware
confirming that the firewall allows all incoming thingies
resetting the router
making sure the keychain password allows all applications to access it
connecting to the internet through a computer-to-computer network from another machine
Because the situation has deteriorated over time, I'd also like to know whether people think that it's two problems (the type of router then later the airport hardware(?)/software(?) itself, perhaps) or just one. Since I've tried basically everything besides switching out our router, I'm kind of inclined to blame it on that, especially because one of the more plausible explanations for this problem that I've heard is a time-out error due to Airport expecting a faster response than it's able to get from older routers; however, the fact that other networks haven't been working means that it's not likely to be just the router. If it's just one problem, which is the simpler explanation, then I guess there's something properly wrong with my computer's software, in which case I guess I'll take it to the Apple Store. :/
I'm in love with my computer otherwise, and I'll admit that I spent a good twenty minutes sobbing out of frustration over this. Any help would be immensely appreciated.

HI and Welcome to Apple Discussions...
Try Changing the Airport Channel
Open AirPort Utility, located in the Utilities folder in the Applications folder on a computer using Mac OS X.
Select the device you’re setting up, and then click Manual Setup. Enter the base station password if necessary
Click AirPort in the toolbar, and then click Wireless.
Choose a new channel from the Channel pop-up menu.
Carolyn

Airport Self-Assigned IP, the wireless doesn't connect to the internet

Hello Everyone,
I have a problem with my airport shows that has a self-assigned IP address and the DCHP doesn't renew, I tried a manually IP but doesn't work neither, I saw this problem about 4 days ago, and I search here in this same sub-forum, I saw that people with Macbook Alu 13'' having exact same problem as for the iMac 27'' Ethernet or Wireless with self-assigned IP have tried everything but nothing seems to work.
I'll leave this link here, maybe someone can be helped with it, I tried but doesn't work...
http://stevejamesson.com/2008/10/01/reset-mac-os-x-network-configuration-factory -default-airport-interface-disappeared/
Please if someone has same problem and can solve it please help me...

please help me...

Bizarre WiFi Connectivity Issue; Self-Assigned IPs, Static IP Doesn't work

The short and sweet of the problem: Macs/Apple Devices are pulling self-assigned IP addresses when connecting to a Linksys EA6900/AC1900 router.
Here’s the detail: I am working at an office with 1 Airport Extreme and 1 Linksys EA6900/AC1900, both are configured for Bridge Mode and both use WPA. DHCP is being handled by a Watchguard XTM5 series firewall.
When Macs (and often iPhones) connect to the Linksys (on 2.4 or 5Ghz) they get a self-assigned IP address. If you enter a manual address you still do not have any connectivity. However, if you connect to the Extreme you will instantly get an IP address, and if you switch to the Linksys your DHCP address will carry over and you will retain connectivity. This problem does not happen to the Windows machines in the office- they all connect to all base stations without any issue. Total users on the network range from 5 to 20 WiFi users at any given time plus and AppleTV (also affected).
More info: When there are between 5-10 people in the conference room for a morning meeting the Macs will all revert to self-assigned addresses (even if they were working before). The workaround has been to connect to the Extreme, but there are occasions when this occurs that the Extreme will also not seem to pass the DHCP addresses from the firewall; addresses become self-assigned and you lose all internet. To make matters more odd, this behavior seems to really only affect the network during business hours; after hours the Linksys works pretty much normally and any device can connect without issue.
Things I’ve done: Run Wireshark and located a number of rogue devices that were handing out overlapping DHCP addresses. Identified machines that were ARP storming and removed them. Expanded the DHCP pool so that we aren’t running out of addresses and confirmed that we had enough by checking the logs.
More things I’ve done: Used Netspot to check signal strength and channel overlap and isolation. I have mapped the signal strength by location and we have strong signals to the various locations (the Linksys AP is 7 feet from the conference room). I have checked that the firmware is the most recent version.
I can’t find any logical reason for the Macs (and pretty much only the Macs/Apple devices) to not be picking up DHCP info through the bridge mode devices. I would tell them to get another Extreme but they are going to be deploying a Cisco Meraki system soon and I suspect that this problem will persist since the Linksys was put in place because the last AP displayed the same behavior with the Macs picking up self-assigned IPs. Affected Macs range from 2010 era MBP and Air to 2013 MBP and Air and they are running OSX 10.8 through 10.10.
As for the history of this network, I just walked into this company and know very little about how well it worked before, but apparently it has always been flaky according to the staff.

I agree that something isn't right; I am going to cut over DHCP services from the Watchguard to the newly deployed OS X Server tonight and see if that changes anything.
On the other hand, faulty DHCP server/client settings doesn't explain why applying a static IP still leaves you with no connectivity. I think that clue is also fairly important but I can't figure out what would be blocking connectivity on a static IP setup.

Ethernet cord has a self assigned IP address, can this be changed?

I am trying to connect my laptop to my Xbox 360 so I can get on Xbox Live using my computers wireless as a gateway... but the ethernet cord has a self assigned IP address and won't work.. I've tried everything to change it and it still won't connect with my router. It is a cisco router.

Welcome to Apple Support Communities
You stand a better chance of a connection if you set the Ethernet interface to DHCP and have it be assigned an IP number by the Router ...

Lost wireless and repeated self assigned IP address

After I updated to OSX 10.5.6 my powerbook started dropping my wireless/internet connection, and adopted a self-assigned IP address. This happened whether I connected to the router via wireless or cable.
I was eventually able to change the system configuration files as suggested in previous posts, and reset my PRMU. This has worked for a wee while, but sometimes on starting up my laptop, the machine self assigns again.
I know the internet is available as I can access it from my iphone.
Then 20min ago, whilst surfing, the internet went down AGAIN, and self-assigned its favourite IP address.
I recently updated to 10.5.7, but the problem remains.
Is this a new problem or has it been going on for a while?
Also, is it a hardware or a software problem?
Any ideas?
Charlie

If you are able to connect initially and then it drops out I would look towards possible sources of interference. While most modern devices avoid this issue fairly well, it is a possibility. Devices such as cordless phones used to cause problems.
If it is dropping out while you are physically connected, I would perhaps check the settings on your router. Most models have a reset function which will allow you to reset it to factory defaults. Then you could reconfigure it and see if the problem persists.
The other possibility is that there is a software service on your macbook that is starting up and causing the network loss. If possible, I would attempt to initialize and reinstall all the software on your macbook. Note that this will wipe everything off, so make sure you make appropriate backups before reinstalling from scratch.
Once you have reinstalled the OS, you can upgrade it to the most recent version and see if the problem persists before installing any other software that may interfere with it.
You really need to go through a process of elimination to find out whether the problem lies with the macbook or the router. However considering your iphone works fine, I would look towards the macbook first.

Can't connect wireless due to "self-assigned IP address"

I recently switched from PC to Macbook. I cannot log on to many wifi networks I could previously access with my ThinkPad. The computer successfully finds the network and has a strong signal but will not connect. Under network status, I get a message that says something like "Your Macbook is connected to the wireless network but AirPort has a self-assigned IP address and may not be able to connect to the network."
Ive tried various options but still no luck. This mostly happens in public Wi-Fi networks such as internet cafes, airports and Starbucks' T-Mobile networks. Thanks!

Can you connect to any wireless location? Or does not fail only in certain places? If you can't connect anywhere, it is your problem. If you can connect in some places but not others, it is their problem.
It wouldn't surprise me if there is some new, cheap vendor of wireless access points that doesn't do the network settings correctly and only Windows machines will connect to it.
You were a ThinkPad owner, so you weren't a typical PC user anyway. Most of them use PCs only because they are cheap, cheap, cheap. Is it 3.29 cheaper than a Mac? Buy it! Those people are now making cheap wireless access turnkey solutions. I have seen people like that before. Just because there are hundreds of millions of pounds of equipment depending on the software, or people's lives, doesn't mean they know how to do networking. They may be so incompetent they don't know they are incompetent. Those types typcially would never, ever think to test their product on a Mac.

Airport and a self-assigned IP address - can't access wireless net

I have a strange issue with Airport picking up a wireless network.
I'm not in my usual location using my MacBook Pro.
There is a wireless network here.
Airport sees it, and asks for the password (provided to me).
Airport looks connected, but, I see the message: "Airport has a self-assigned IP Address and may not be able to connect to the internet".
And in fact, it cannot. I've run through the diagnostics routine twice, and no go.
How do I get Airport to accept an IP address from this wireless configuration?

I am having a nearly identical problem. The solution provided did not work for me.
We have two MacBook laptops, one is mine and the other my wife's. My laptop still works fine. The AirPort communicates well with the wireless router. My wife's laptop just started having this problem about a week ago. The latest Airport software updates helped, but did not solve.
The problem is that I now have to go into network diagnostics everytime to connect my wife's laptop to the wireless router. I have to re-enter the password to the router each time. Once I enter the password, it finds the IP address and connects everything properly. I checked the keychain password and it is there, so I don't know why it keeps losing the IP address.
One thing that I did preceded this problem. I changed my router password to WEP. If anyone knows if this could cause the problem, let me know.

Apple Mac wireless self-assigned IP address help

I just got FiOS today. Everything appears to be working fine except for one thing, my Apple Macbook Pro, running 10.5.8 is getting a self-assigned IP address when I connect it to my FiOS wireless router (ActionTec MI424-WR).
The Mac has a physical connection to the wireless router. The "My Network" tab in the wireless router configuration screen shows it as connected, with an assigned IP address of 192.168.1.6. However, the ping test fails, and the Mac's Airport settings show a self-assigned IP address.
I've tried rebooting everything, turning airport on and off, and renewing DHCP, but nothing is working.
I haven't touched any of the default settings on the ActionTec, it's still running WEP.
I did verify that my firewall is turned off on the mac.
What else can I try?
Solved!
Go to Solution.

I have a 6 month old MacBook Pro running the latest version of OS X, so it's affecting newere Macs as well. I found some on-line discussion that it's a problem with only the Macbook Pro.
FWIW, a few hours after finally getting it working it happened all over again. I had wireless connectivity but only got a self-assigned IP address. I tried shutting the airport on and off, deleting the wireless key from key chain, and clearing the wireless network. However nothing worked until I rebooted the Mac.
I then checked the firmware on the ActionTec and found it was 20.8.0 and 20.9.0 was the latest (mind you I just got this router installed today). I updated to the 20.9.0 release and everything has worked for about the last 6 hours. Fingers are crossed. :-)

HT1338 my airport is not working getting Wi-Fi has the self-assigned IP address 169.254.5.29 and will not be able to connect to the Internet

my wi fi wont work giving me this Wi-Fi has the self-assigned IP address 169.254.5.29 and will not be able to connect to the Internet whats up with the airport how do i fix it

See this discussion.
Wi-Fi has the self-assigned IP address
Troubleshooting suggestions.
Troubleshooting Wi-Fi issues in OS X
Wireless Connection Problems - Fix
Wireless Connection Problems - Fix (2)
Wireless Connection Problems - Fix (3)
Wireless Connection Problems - Fix (4)
Wireless Diagnostics - About

Wifi works for everyone but me - I get a "self-assigned IP address" and no Internet connection

I have the most confounding Wifi problem. I just got Verizon Fios, and it works perfectly on my roommate's laptop, his iPad, and on my iPhone. But it doesn't work on my Macbook Pro (running Lion). My Macbook has no problem connecting to other Wifi signals - in fact, there's another connection in my building that I can connect to just fine from my room.
When I try connecting to our own Verizon signal though, the Macbook hunts around for a few seconds, then connects - but says there's no Internet connection. I get an ominous exclamation mark over the Wifi icon. My computer gives me a "self-assigned IP address" and says it can't connect to the Internet.
I've tried everything I can think of: Restarting the computer, turning Wifi off and on, deleting and then re-accessing the signal, turning the firewall on and off, renewing the DHCP lease, restarting the router, switching channels on the router, and more. At this point, I'm out of ideas. Any suggestions?

Please try each of the steps that follow, in order, until resolved:
STEP 1 - Create a New User Account
System Preferences > Accounts
Click "+" to add a new account.
Log off, and then, log back on with the new user account.
Try connecting to a Wi-Fi network with your Mac's AirPort.
If this resolves the problem, there may be something amiss with your current profile and will require further troubleshooting.
If this does not resolve the problem, go ahead and log back into your normal account and go on to the next step.
STEP 2 - Preferred Networks
Delete Preferred Network(s)
System Preferences > Network > Select AirPort > Advanced > AirPort tab
Under Preferred Network, use the minus button to delete the network(s) you regularly use from the list.
Delete AirPort Keychain Entries (Note: This only applies if you connect to AirPort/Time Capsule routers)
Launch the Keychain Access application located in the \Applications\Utilities folder
Click on the "Kind" filter at the top, and look for any "AirPort network password" entries, and then, delete them.
Restart, or log out, then back in.
Add Preferred Network(s)
System Preferences > Network > Select AirPort > Advanced > AirPort tab
Under Preferred Network, click on the "+" button to add any preferred network(s).
Restart, or log out, then back in.
STEP 3 - Move System Configuration Files
Note: You will have to reestablish your network connection settings.
In Finder, go to the Macintosh HD/Library/Preferences folder.
Move (not copy) the SystemConfiguration folder to the OS X desktop.
Restart your Mac. (Note: OS X will automatically rebuild this folder and the associated files contained within.)
If this doesn't resolve the issue, you can move the folder (now on the Desktop) back to its original location.

My macbook air will not connect to the internet due to a self assigned IP address. I have tried trawling the support forums, but either I can't understand the suggestions, or they don't work. Please explain to me in simplest terms how to fix this. Thanks!

My macbook air will not connect to the internet due to a self assigned IP address. I have tried trawling the support forums for hours, but either I can't understand the suggestions, or they don't work. Please explain to me in simplest terms how I can fix this. Many thanks!

The warranty entitles you to complimentary phone support for the first 90 days of ownership.
If you bought the product in the U.S. directly from Apple (not from a reseller), you have 14 days from the date of delivery in which to exchange or return it for a refund. In other countries, the return policy may be different. If you bought from a reseller, its return policy applies.

Rebuilding aMacBook 1.83 GHz Intel Core Duo, hard drive failure so rebuilding system. Aircard will not stop self-assigning IP address. Any ideas how to resolve successfully?

Had hard drive failure on MacBook 1.83 GHz Intel Core Duo, so had to rebuild the OS on new drive. Was on Lion 10.7.5 prior to failure, but had to reinstall Snow Leopard 10.6.3 since that was most recent OS on media I had. After finally getting ethernet connection to router working, was able to get to internet and download / upgrade to 10.6.8. I assume I can probably buy the upgrade to Mountain Lion 10.8 from there.
Problem is this, Airport will not stop self-assigning IP address for my wireless connection, and unless I can get wireless back on this laptop, doesn't make a lot of sense to continue the rebuild and reinstall of all the software that was on it prior to HD failure. Only way to my home network and router is ethernet now. Everything else on my network (Apple MacBook Pro laptops, iPhones, desktops, and non-Apple printers and laptops) is hooking up to router wirelessly fine.
Any ideas how to resolve successfully so that the airport will stop self-assigning and allow the router to assign the IP address?

When see the beachball cursor, note the exact time: hour, minute, second.
These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.
Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad and start typing the name.
The title of the Console window should be All Messages. If it isn't, select
          SYSTEM LOG QUERIES ▹ All Messages
from the log list on the left. If you don't see that list, select
          View ▹ Show Log List
from the menu bar at the top of the screen.
Each message in the log begins with the date and time when it was entered. Scroll back to the time you noted above.
Select the messages entered from then until the end of the episode, or until they start to repeat, whichever comes first.
Copy the messages to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
The log contains a vast amount of information, almost all of it useless for solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.
Please don't indiscriminately dump thousands of lines from the log into this discussion.
Please don't post screenshots of log messages—post the text.
Some private information, such as your name, may appear in the log. Anonymize before posting.

Self Assigned IP Address redux

I am getting the "Self Assigned IP Address" in my Airport connection and I can't troubleshoot the problem.
Here's my setup and what I have been looking to accomplish..
I have an iMac G5 with a built-in Airport Extreme card running Leopard 10.5.3. I have created a network to provide my AppleTV and my work laptop with access to the internet. I've turned Internet sharing on, and have security set to a the WEP 128 key..
Recently I had to exchange my AppleTV for a new one, and during the 2 weeks I was without AppleTV - something has changed (and as I think through the issue, I'm not certain about when the last time I played youtube or purchased content - maybe the new appleTV doesn't have anything to do with it, and it was a software upgrade), as I am no longer able to access YouTube content or the iTunes Music store to authorize my purchased content or to purchase new music/movies. However, I am able to watch movie trailers, and preview songs. It connects to the network fine, shows a strong signal, but something isn't quite right.
I've performed about every known solution to the AppleTV problem, and have an open post over in the AppleTV area, but in tracking down my issue, I see that my Airport connection is showing that it has a "self-assigned IP Address" and my not be able to connect to the internet. My thoughs are that if i get the self-assigned IP address problem solved, I'll solve the ITMS/YouTube issue on the AppleTV.
My internet connection is via Verizon DSL, with a DSL modem, connected directly to my iMac with an ethernet cable. (no external router/firewall)
I find it interesting that I can watch trailers, preview music from ITMS with the 'Self-assigned IP' but not access ITMS for purchases, etc.
I do not have any expertise in networking and for the most part am just following what posts I've seen out there suggest to try - trashing the com.apple.airport.pref's - restarting in 'Safe' mode, etc. Rebuilding the network connections from scratch, etc. Repairing Keychain access, disabling the built in firewall, etc. Just can't get by this issue.
Anyone with any thoughts?

hey guys...I found the problem...it helped me very much just try to change the wireless mode from 11bgn mixed to 11bg mixed...do this from router settings . . .I guess this will help you

Self-assigned IP address problems

I'm having a problem with my wireless router connection (my Airport card shows the network, but the "fan" is greyed out, and if I choose the network it still doesn't connect - When I check network status I get "AirPort connected to network, but has self-assigned IP address and may not be able to connect...)
I can temporarily fix the problem by going into System Preferences to Network to Airport to Preferred Networks to Assist Me and THEN it will go to my network and turn on the path.
I'm running Tiger 10.4.11 on a G5 iMac with the original AirPort Extreme card, and routing through a Linksys WRT54G attached to a cable modem.
There are a lot of networks in my area, according to my wireless "fan".
If changing channels on my router might fix this, I'd like to give it a try, but I don't know how, AND I don't want to ruin the signal to the other computers in the house, which, by the way, work just fine when the iMac loses the signal.
If there's another way to tell the router to ignore the self-assigned IP address, or to get the AirPort to stop providing this ...
The problem is obviously the self-assigned IP address. The question is what is causing this?
Is it the AirPort Extreme Card?
Is it the Linksys Wireless router?
How do I test to see which it is, without losing the signal from the router to the other computers in the house?
With so many people having the same problem, there must be an answer somewhere.
Can some kind soul please point out the correct path? My tech support (teenager) will be home from college this week, and if I can prove to him that it won't ruin everything I think he'll be up to the challenge.

Hi,
Thank you Linc & dwb, I've had no issues with the router in the 14 months its been installed. But tonight I've turned off the NAS and since then no drop off for wifi/ or assigning itself an IP address.
I will switch on the NAS once again and see what happens, would it be best to assign a static IP to the NAS? One thing I have found when checking the homehub connection details, the mac air connects at the 5Gz Wireless as does the Kindle, which has also suffered from losing the wifi connection, where as my macbook pro only connects at 2.4Gz and like I said has not had any issue. Not sure if this anything to do with the problem or not?
All I do know is that since the NAS was introduced then the problems began, so again not sure if its the NAS impacting on the router or a router setting?
thanks

Self assigned IP Address, wireless doesn't work

Similar Messages

Maybe you are looking for