Self Assigned IP none of usual fixes working

My college recently revamped their wireless network and my computer will no longer connect to the wi-fi meant for student use. My computer sill connects to the public wi-fi on campus and connects to my home network just fine. It is a WPA2 set-up that, in theory, you only have to sign into once and it will remember you. These are the things that I have already tried but have not fixed the problem:
Restarted my computer
Turned airport on and off
Told my firewall to accept all incoming connections
Turned off my firewall
Created a new location
Renewed the DHCP Lease
Deleted System Preferences and restarted my computer
Put a $ before my password
Installed all updates and restarted
Deleted airport in the new location and added it again
Contacting school IT who were basically worthless
I'm not sure what else I can do, it's not like I can restart the router or anything. Any suggestions?

I ended up having to change my password for my student account to connect. It was a problem with the system and not my computer like I thought it was

Similar Messages

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.

Self-assigned IP adress problem. What if none of the fixes worked?

I just developed the "self-assigned Ip adress" at my college last night. I've been up all night on forums trying to solve the problem and tried about everything.
I've:
Tried to Renew DHCP Lease. (does nothing)
Manually input ip address. (doesnt work because the college uses a dynamic ip instead of static)
Opened the firewall to allow all connections. (I think it already was open)
Created a new location. (nothing)
Run diagnostics about 10 times. (prompts to reset router or modem, which I doubt is the problem since my roommate's laptop works fine)
Created another ethernet connection. (nothing)
Repaired the permissions. (nothing)
Can't think of what else I did, but I'm thinking it could be an issue with the 10.5.5 update, so if nothing else works, I am planning to use my OS disks to reinstall OS X (I think it was 10.5.3 when I bought it.)
If there is an easier way, please advise!
Any help would be greatly appreciated.

I too am having this problem. I just updated from 10.4 to leopard, and could not connect due to the self assigned IP. Found somewhere online on another computer that you can shut down, restart and hold down the shift key to boot up in safe mode. Then restart, and everything works, normal IP. I then did software update, to get the latest leopard updates, and had the same problem, used the same fix. I was coming on the forum to ask if anyone else had this problem and to see if there were any explanations. Hope this works for you. I will keep reading to see if anyone else has an explanation. I also noticed that Internet connect is no longer part of OSX. I travel a lot and that function has helped me connect in many places, so I hope it's exclusion won't mess me up.

Self assigned IP : still no bug fix ?

I have a problem for a long time with my Time Capsule. I use an ADSL modem and router (from Free French ADSL Provider) and my TC is plugged on it and set to "Bridge" mode.
I have many devices wired and wireless on the TC. But I have a big problem, sometimes (not all the time), my MacBook is getting a "169.254.x.x" IP address, a self assigned IP.
That's weird because sometimes it works well from 6 AM to 7 PM for example, then at 7 PM it doesn't work anymore. There is no reason why, because I haven't touch anything in my network.
It's pretty annoying. Is Apple aware of this problem ? Can we hope a fix soon ? I had many problems with the WIFI on my Mac (before, it was the "wake up" WIFI problem but it seems to be fixed in the last Lion update).
I've tried everything, reset all (TC, Macbook etc.), sometimes it works a day, the other day it's not
Thanks

7pm sounds too specific to me.. get a wifi analysing software, kismet on the mac but inssider on a pc is a better utility. Locate all the wireless around you and what channels are used. I would say you are being swamped by higher intensity wireless than the TC can produce.
Go into the wireless setup and change over to manual settings.. set to N wireless.. and set to manual channels.
In 2.4ghz try 1, 6, 11.. but pick whatever is the lowest usage from your survey of wireless usage.
Also try and use 5ghz as it has less interference. When you are bridged, the IP address is derived from the modem and not the TC so the issue can be there.. try setting dhcp to fixed for the MAC address of each wireless. and set the lease to very short.. 30min or even try 10min.
There certainly are issues with Lion networking.. exactly what is hard to figure out.. but you can also try the TC with earlier firmware.. go back to 7.5.2 which was much more reliable than later ones.
You can also try it in router mode putting the modem in bridge if the ISP supports PPPoE.. or use DMZ with the modem still doing routing. The TC will kick up a double NAT error but just select to ignore it. Sometimes it will work better in router mode.

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

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.

Self-Assigned IP: How Can I Fix This?

Hi,
I've posted on this issue before, but am still having trouble. All was working well with my wireless network until recently, when I became unable to connect my iBook G4 to my wireless network via a Netgear router. I am getting the "Self-Assigned IP Address", despite the fact that I am using DHCP, have renewed the DHCP lease, and input my IP address manually. I can see my IP addresses under the DNS tab, and it is configured using DHCP with an IPv4 169. address.
I've tried all solutions. I was once able to resolve the problem by dragging the Library/Preferences/System Configuration folder onto the desktop. Now the problem has returned despite the folder being on the desktop and remains even if I move this folder back into the Preferences.
Can anyone help me? I am at the point of simply buying a new laptop, but surely there has to be a solution...
Thanks.
lsb
Ps. I am using an iMac running Snow Leopard as well. The iBook is running Panther. The desktop, so far, touch wood remains OK.

lsb wrote:
Hi,
I've posted on this issue before, but am still having trouble. All was working well with my wireless network until recently, when I became unable to connect my iBook G4 to my wireless network via a Netgear router. I am getting the "Self-Assigned IP Address", despite the fact that I am using DHCP, have renewed the DHCP lease, and input my IP address manually. I can see my IP addresses under the DNS tab, and it is configured using DHCP with an IPv4 169. address.
I've tried all solutions. I was once able to resolve the problem by dragging the Library/Preferences/System Configuration folder onto the desktop. Now the problem has returned despite the folder being on the desktop and remains even if I move this folder back into the Preferences.
Can anyone help me? I am at the point of simply buying a new laptop, but surely there has to be a solution...
see if the posts by Tesserax in this thread http://discussions.apple.com/thread.jspa?messageID=10162935&#10162935 give you any pointers
good luck !

I've spent an hour plus googling this and none of the 'fixes' works. My custom ringtones show up fine in itunes but are grayed out in iphone when I try to sync. This just happened when I synced my phone: previously worked fine.

I've spent an hour on this: massively frustrating. My custom ringtones disappeared from iphone when I just sync'd and now show up in itunes/iphone interface (on the mac) grayed out: won't sync to phone. I know the audio files work because they were fine two hours ago! (iphone 5 running 8.1.3)

I had this problem too after i upgdatd to OS X Mavericks... only the songs on my iphone 5s that i purchased from itunes would play.
i read something about it being a syncing issue. when you plug your phone into your computer with the usb cable, the person said to switch from automatic syncing of itunes to the "manual" option. mine was already set to manual so i wasn't sure anything would work. BUT, when i plugged my phone into my computer, it started to sync all of my music on my phone again (top of itunes bar where song playing/time is listed said "now syncing 123/534 songs to x's iphone"). once that was completed, i checked the music app on my iphone and everything was back to normal!
so, i would suggest setting your music syncing settings to manual if you haven't tried that yet!
hope this helps!

Firefox crashes MANY times/day. None of your fixes work so far.

Running FF 24.0 on Mac OSX 10.8.5. Crashes constantly. I get the color wheel and have to force quit. Force quit says "not responding". I have reset FF, turned off hardware acceleration, was already set at default theme, I have no extensions. It does not crash in safe mode. Help!

In Firefox Safe mode these changes are effective:
*all extensions are disabled
*default theme is used (no persona)
*userChrome.css and userContent.css are ignored
*default toolbar layout is used (localstore-safe.rdf)
*Javascript JIT compilers are disabled (javascript.options.*jit)
*hardware acceleration is disabled
*plugins are not affected
*preferences are not affected
You can try to disable the JavaScript JIT compiler and set javascript.options.*jit to false on the <b>about:config</b> page.
*javascript.options.baselinejit.chrome
*javascript.options.baselinejit.content
*http://kb.mozillazine.org/about:config
You can also do a check for corrupted and duplicate fonts and other font issues:
*http://www.thexlab.com/faqs/multipleappsquit.html - Font Book 2.0 Help: Checking for damaged fonts
*http://www.creativetechs.com/iq/garbled_fonts_troubleshooting_guide.html

Self Assigned IP - Fixed, but help still needed, please

I'll add a bit of a back story first which I hope will help people understand my issue, but also hopefully lead people with a self-assigned IP issue to a fix (link is within the post)
I’m on on an iMac 20″ Mid 2007. I recently updated to OSX Lion after having wifi connection issues in Leopard. I used to randomly get kicked off my wifi and given a self assigned IP. With Leopard, the issue was fixed by applying a manual IP, router address etc and restarting. The issue would return months later, but I got over it after a few tantrums.
Then as soon as I updated to Snow Leopard, I instantly had no internet access and I could only upgrade to Lion if I downloaded system updates. So after a few hours of searching, I toggled my internet sharing ‘on & off’ and that was enough for that fix.
But then I upgraded to Lion and again, no internet. And nothing worked for me at all, every fix on the internet I tried failed. If my airport ever managed to connect to my router I would get a self assigned IP. Or it would say it was connected but there was no internet. So I hunted for hours and eventually found this:
Now, here is a fix for anyone who is having the same issue. I hope it works for you!
http://www.davidpierron.com/index.php/archives/2009/04/13/289/
This did work for me. The fix is to flush your ipfw through terminal, and it worked for me instantly.
However, I now have another issue that I really hope people can help me with. It's not as annoying as the above, but my god it's still very annoying!
Here are some bullets to show the tedious routine I have to go through in order to connect to the internet via my airport.
• I turn on my mac and my it tries to connect to my router automatically. But after a minute of trying, it says it can’t connect.
• I select my router manually from the list and have to enter my password manually, even though it is already saved in my Keychain.
• It then connects and says, ‘Connected but no internet’, so I leave it for two minutes and throw things around the room.
• After those 2 minutes it connects to the internet. But no, I can’t browse the web as the browser says 'DNS look up failure'.
• So I open terminal, enter 'sudo ipfw flush' to flush my ipfw and BINGO, I’m online 5 minutes after logging on to my machine.
The router I am using was only issued to me 8 months ago by my new ISP here in the UK, it connects via WEP and has always been stable for every other device I have connected to it. But I am going to ring up my ISP and see if there is a new router I can get.
If anyone - ESPECIALLY APPLE who seem to be shying away from admitting there has ever been an airport wifi issue - has any information to advise me, then please let me know.
Also if you are having a Self Assigned IP address issue and that fix above works, give the man some credit on his blog, and if you know him, give him a kiss from me!
Thanks

Update:
I spoke to my ISP to see if they had any newer routers and if they did WPA now.
I have a new router on its way and they have updated my router to do WPA!
The result?
I now connect to my router automatically after a restart. No issue there.
However,
It still can't find the internet when it first connects.
I still have to wait 2 minutes for it to find the net.
I still have DNS issues once connected
I still have to flush ipfw before it works correctly.

No importing fixes work for me.... help please! My job is on the line!

Ok, the specs first...
G5 desktop w/ OSX 10.3.9
iMovie HD (5.0.2)
QT 7
Sony HDR-FX1
Problem: Same as several posts I've read- iMovie sees and communicates with the camera, but WILL NOT import anything... Lots of people with the same problem, but the difference is that NONE of the fixes worked for me.
I tried the GarageBand / Audio/MIDI Setup fix. Nothing. I tried trashing preferences. Nothing. I tried resetting the PRAM. Nothing. Unplugging the computer for a while, power cycling the computer and camera, switching Firewire cables, switching Firewire ports, examining all options on the camera.... nothing!
I even tried using the Quicktime 6 re-installer. I downloaded it, began the installation, and it ended up telling me I couldn't reinstall because I didn't have a valid version of Quicktime on my machine! I was sitting there looking at QT 7!!!
Now my job is on the line because I have video assets that are due! Can anyone help me? I know it should be working because it did momentarily the first time I tried it... imported the HDV signal like a champ... until I went to stop the import and edit my video. Then viola... iMovie crashes and all goes downhill from there.
Anyone with any help would be sainted in my book. Thanks for reading...

You say you've tried different FireWire ports on the G5 ..but that often seems to be the problem ..or the fix!
Do you have a 3rd-party FireWire card installed in the G5..? If so, try connecting the cam to one of those ports instead of the built-in ports. Or try pulling out the 3rd-party card, and then try the built-in ports.
Do you have someone else's codec installed? Toast? Flip4Mac? To avoid those, try creating a new User (..System Preferences>Accounts and press the + at the bottom of the left pane..) then log in as that User instead, and see if it works. If so, you have conflicting software in your main User account.
However, it's not usually that: it's most often (..with a G5..) a hardware (FW port) problem, by all accounts. [..Even the Apple Store in London couldn't get their FX1 to work with their G5 when I wanted a demo of import times!..]
So there has to be a solution (my FX1 works fine with PowerBooks and a Mac mini, but I don't have a G5) ..I'd suspect a bad interaction between different ports - or recently-connected FW hardware - on the G5.
P.S: "..Then viola... iMovie crashes and all goes downhill from there.." Try removing the viola; it takes up too much space. Try a violin.

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 ...

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.

Self-Assigned IP....Internet Not Working

Hi--
Let me start off by saying I have absolutely no idea how this happened. I went to start my Macbook this morning and the Internet didn't work. Usually this is not big deal, and I just unplug the router and everything works fine. However, this time (for whatever reason) was different. When I go to my network settings, it says "Self-Assigned IP" under Airport and that "AirPort has a self-assigned IP address and may not be able to connect to the Internet." I was browsing other forums, and found that sometimes renewing the DHCP lease works. I did this, and still no Internet.
How do I fix this??
Thank you.

Hi - this may help.....I sort of had the same problem with my wired connection.
Although I think my router is dying - I hooked my Macbook directly to my modem and my network said that it had a self-assigned IP address but could not hook up to the internet (although it had green lights for the Ethernet, Network settings and ISP)....
I used the 'Automatic' location and the DCHP with manual address setting (or it was the Manual setting) - I got told that what it is doing is just randomly selecting a IP address to use but the address it chooses isn't actually able to work...
(This what I was told) - I entered my IP address (I had copied it down from previous network setups) and I had to type in my router address (even though I wasn't using one I still had to have a number for it to use) - plus a subnet address.....
After that it picked up my internet and works ok......I have to get a new router so hopefully I can connect it all up as it was before.....
This may help - although my set up is slightly different....

No Internet with Lion. Stay away until self-assigned IP addresses are fixed!

I have a TimeCapsule (802.11n 3rd gen) and four Macs. Until two months ago all was well and everyone could connect.
Two months ago the Apple apps on the MacBook Pro stopped connecting to the Internet on the TimeCapsule network (Mail and Safari would not connect, Firefox was fine). The MacBook Pro connects on all other networks. I travel a fair amount and the computer has connected fine at all networks tried. I have sinced updated to Lion (10.7.2) and the problem is the same. The error in System Preferences indicates that the computer has a self-assigned IP address and will not be able to access the Internet - but Firefox works, so we know that is not entirely the case.
Last week our desktop stopped being able to access the Internet using the TimeCapsule network. Problems the same as the MacBook but the desktop Mac is using Snow Leopard.
Our older laptop is using an earlier version of OSX and all is well. Out antique Mac laptop is also working well.
We also have a Verizon MiFi and all machines can access the Internet on that.
I have tried every "fix" I can find on the boards and through Google. Nothing works. From the looks of the boards, there are thousands of users with this problem and no answer from Apple.
I was much better off before I switched to Lion. In those days, I just used Firefox and looked at my iPad when I needed mail (and waited to sync at the office). But with Lion comes iCloud and an increased reliance on the App store, making internet connectivity through Apple apps is a must. Can someone from Apple help us fix this? Does anyone have any suggestions?

That is what I told Comcast, but they said since my
computer works "fine" in Safe-Boot,
Classic, and the other PC—then they
conclude there's no problem with their hardware and
that its not their problem; that its Apple's issue.
And nope I'm not connected wirelessly, it's through a
basic ethernet cable.
I don't know who to blame for this. Five years ago, this never happened, but it is common now. It affects both Macs and PCs, but as usual, people like Comcast will make an effort to fix a PC but throw up their hands with a Mac. Go figure.
So, what speed, duplex and adapter type numbers
should I put in?
I don't know for sure. Start with duplex. If it current says "auto", change it to "full". If that doesn't work, or if it already was "full", change it to "half". If still nothing, switch it back to "auto" and fiddle with all the 10/100 speed combinations. You may have to go back and try different duplex and speed combinations! It sounds harder than it is. Try changing the duplex and adapter settings from "auto" before changing the speed. I'm am on my work Dell right now (which needed the same fix BTW), so I can't give you very good step-by-step instructions.
The thing that troubles me is why is it that the
internet works fine in Safe-Boot and Classic, but not
Normal OS X mode?
No clue about that.

Self Assigned IP none of usual fixes working

Similar Messages

Maybe you are looking for