Self-assigned IP, no IP, no authentication server!

As most people in threads related to this problem have stated, this issue presented without provocation. The Internet stopped working during a thunderstorm, turned back on, and my computer is the only one having problems in the house. That being said, I've been browsing through countless solutions to no avail. But first, the problem.
The wi-fi status symbol in the menu bar constantly displays the "searching" icon. When I click on Network Preferences and try to join my network (if it even shows up), the wifi bar on the left toolbar displays a yellow circle, and wavers between "no IP address" and "self-assigned IP". I'll also see "802.1x:default authenticating". It always end up with "authentication server is not responding".
I've tried deleting my network from keychain access, I've tried creating a new location and renewing the dhcp lease, and I've restarted my computer multiple times during the process. Nothing seems to be working. Any ideas?

It's trying to authenticate to a RADIUS server. If you haven't set that up or don't know what it means, delete the Wi-Fi connection in the Network preference pane and recreate it with the same settings. If you have set up a RADIUS server, it isn't working or isn't reachable.

Similar Messages

Self Assigned IP from my macbook pro to xbox through ethernet...

I live in a college dorm and i have been using internet sharing through an ethernet cable to connect to xbox live and it has been working fine for months now, but has now recently decided to make everything difficult and it continuously just says self assigned IP address cannot connect to internet. Every video and forum I have tried reading generally refers back to something involving the router however in this case my wifi is working no problem its just the ethernet cable going to my xbox that has the self assigned IP problem. If anyone could help me it would be greatly appreciated, thank you!

It isn't clear what you are trying to do. Why are you connected to the Xbox? Is the Xbox suppose to share the internet through your mac?
Since there is so little information, I'm going to go through a lot of stuff you might already know.
You have two network interfaces on your Mac. en0 which is the cable and en1 which is the wireless.
IP addresses are assigned through a process called DHCP. When you have a self-assigned address there is no DHCP server.
The DHCP server -may- be on a router or it may be on several different devices such as a Unix computer (or Linux) specifically set up to provide DHCP addresses. Since you are in a dorm, is is quite likely a specifically configured host is providing DHCP.
Your wireless network will get a different DHCP address than your wired network. For example, 128.1.0.0/16 might be the network assigned to the wireless to support 253x253 different hosts (a lot of hosts and the main reason to keep DHCP off of the router). And something like 129.1.0.0/16 would be assigned to the wired network.
The DHCP server for the wireless network WILL NOT provide an address for en0.
NOTE: I have never used Apple's Internet Sharing and I -assume- that when you share that the Mac acts like a bridge.
I also assume that this is what you are attempting to do with your Xbox. This would mean that the Xbox would have to initiate a DHCP request for an address that is forwarded (bridged) through the Mac to the DHCP server. This request includes the Xbox hardware address. Now comes the part that is going to make you cry. MAC addresses are 48 bits and look like AB:CD:EF:12:34:56. The first 24-bits are assigned to a manufacturer and used for specific products. When the DHCP request gets to the DHCP server, it knows that the request is from an Xbox. Your campus may have decided that you've been playing too many games and does not respond with an IP address for the Xbox.
You can check this out by using a tool called tcpdump or you can install Wireshark. If you want to go down this rabbit hole, it is going to require quite a bit of time and you'll end up becoming quite well educated in how networking works. People go to school for years to understand this. :-)
Or, maybe you just forgot to ensure internet sharing was on.
If you have some other kind of wiring setup then perhaps you have a different problem.
BTW, when you plug the ethernet cable from the Xbox into the mac that "activates" it.
By default OSX is configured to use DHCP to provide an address.
If the Mac sends out DHCP requests over the ethernet cable and never gets a response it will then self-assign an address.
A self-assigned address cannot be used to get to the internet.
(But, I understand that it your Xbox that isn't working not the Mac, especially since you were able to post your question here.)

Airport has self-assigned IP address, authentication step fails

I am a computing consultant at a Pennsylvania university and am trying to configure the airport service on a 15" MacBook Pro (pre-unibody style ~2007) running 10.6.5.
We are trying to connect to a WPA2 Enterprise wireless network that requires username and password authentication before assigning an IP address. We configure Macs all the time here and they all work very well, in fact my own personal Macs haven't ever given me trouble. But the machine I'm working on at the moment just cannot obtain a correct IP address. We know for sure this is not a network or user account credential problem. It must be on the client computer side.
I have tried removing all old user profiles and certificates from the Keychain (our network grants a certificate automatically for new connections), I deleted preference files from the /Library/Preferences/SystemConfiguration folder, I have removed the Airport service from Network Connections, rebooted the machine and performed 3 PRAM resets just for good measure, re-added the Airport service and tried a fresh configuration. I also created and entirely different user account and tried configuring. The only thing I have not tried is reinstalling the OS which I'm really trying to avoid because I'd like to learn what is actually causing this problem. None of the above attempts have been successful.
Has anyone encountered this before in an enterprise environment? Does anyone have any ideas that I should try?
Thanks in advance!

Something like one year ago or so, i had to reinstall the OS cuz i wasn't able to make the iPhone recognized over usb for the tethering conenction...
only AFTER i found out it was related to the OS booting in 64 bits, not just 32 and using the 64 capability for those programs who required it.
I had to deal with self assigned ip too, while sharing internet conenction from airport through ethernet to another mac, but i dunno if that should help you.

Self Assigned IP even though I am Authenticated via PEAP(MSCHAPv2) to WPA2

Help!
After installing Snow Leopard 10.6.1 on my 2.16 GHz Core Duo MacBook Pro running OS 10.5, I can no longer connect to the WPA2 Enterprise network at the University of Ottawa. I can still connect to other encrypted networks, such as my home WEP encrypted network. Before the installation I was able to connect to the WPA2 enterprise network.
When attempting to connect, under network preferences I can see that my computer is Authenticated via PEAP(MSCHAPv2) and a timer showing my time connected is running. However under status, it says that I have a self assigned IP and that I cannot connect to the internet. As a result I cannot connect to the internet.
I have included a picture that describes my problem exactly:
Does anyone have this problem? Can anyone help me?
Thanks!

The thing you and many others forget is that these forums are for those with problems. Those for whom the installs works without fault do not visit here. They do not post. There are about 9,000 topics in the Installation and Using forums (the largest two) and even if every topic were an unique fault, this would mean a small fraction of the installed base.
According to AppleInsider the Q1 sales of SL would be circa 5 million copies, and other reports indicate these numbers have been surpassed in the early months. So lets go for one months sales at only 1.5 million copies. 9,000 faults in 1.5 million copies is only a 0.6% rate and that's if every topic is a different fault (which it plainly isn't).
So I'm afraid your argument is even less convincing - a few people report your fault, and even if only 1% of the installed base uses it, its still infinitesimal. IMO, the vast majority of problems arise from an initial Leopard installation that had enough variability of build to make enhancements problematical. I'd be the first to admit its not Apples finest hour, but its certainly not bad for the overwhelming majority.
Perhaps you could apply to be an Apple tester, to help solve this issue ? Its better than standing on the sidelines complaining about everyone elses work for certain.
Or log a fault request as it will get looked at I can assure you, but only if there is a tester who is actually able and willing to test that particular piece of functionality.

I can't connect to my school's free wifi. i was able to do it before but not anymore i get the self assign ip agrees message .it has no password only a pop up window before you connect to agree to school terms for wifi use. i don't get that window anymore

I can't connect to my school's free wifi. i was able to do it before but not anymore i get the self assign ip addrees message .it has no password only a pop up window before you connect to agree to school terms for wifi use. i don't get that window anymore. i tried everything I can think of. It is a 2010 macbook pro but i recentrly updated to osx lion and even with lion it was working fine so I nkow it is not the update. also Im able to connect to other internets at home it works great. starbucks too. but i became so frustated that i reset my computer to manufactuter setting and reinstall snow leopard on it. still I cant connect. I need help please i have been searching all over the web for help and i see people has been having this same problem for years now.. oh yeah and i know it is not the internet cuz there are other macs connecting to it without a single problem so i think it is an isolated problem plase help....i have follow many advises such as delete the internet from your prefered netwoks. restar your commputer etc etc.

Be sure Safari does not have the Block Pop-Up Windows preference set.
Where I work now there are several unencrypted VLANs that require authentication, and Safari promptly pops up a window for me to register every time.

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

?? New AExtremeBS- MInis self assign an IP instead of picking up DHCP addy

Hello and help! I have a new Airport Extreme Base Station that I'm deploying in our warehouse that will host 3 minis and 3 MacBooks. It's set up to serve a DHCP range out of our LAN's subnet - .126 through .150. I'm using WPA Personal with a 13 character password. It's in "automatic" mode for channel and speed.
The clients are setup with the network in the "preferred" pane of network preferences, password added to the keychain, and set to "automatic"
The Macbooks quite happily join the network, get a dhcp addy, and surf on out to the internet and internally to other LAN computers and servers.
The minis, however, APPEAR to join up (the airport signal bars go to full power) - however, when going to browse the local net or the internet, there is no connection. Looking at the network pref pane gives the message that "airport has a self assigned IP address and may not be able to connect to the internet". No duh! When I look at the TCP/IP pane, I see that they have indeed given themselves a rendezvous addy and subnet.
Now, I assumed that - perhaps - they had timed out in trying to get the DHCP addy and had fallen back on rendevous. However, I moved the base station _directly on top_ of one of the minis, same problem.
I then set one to an addy within the DHCP range (.149), gave it the correct subnet and gateway, Locked the network pane, and still got no love.
Even stranger, after rebooting (with a locked network pane) still no love, and STRANGER still, when checking the network pane, it was unlocked. ???
The minis in question are: one core solo circa April of last year, and two new Core 2 Duos just recently purchased (this March).
I've updated ALL to the latest firmware and 10.4.9 updates that are available to this date (5/2/07). I tried to apply the .n updater to the later models, but the CD doesn't show it as available for install - and I know it's on the disk, as I've applied the update to my Mac Pro, so I'm led to believe that the Core 2 duo minis shipped with the enabler live.
I'm getting ready to punt these frickin machines. Any ideas before I put my spikes on?
Thanks all!
mini core 2 duos and a core solo Mac OS X (10.4.9)

Hello,
Think I'm having the same problem. Got a iMacG5 and old PB. Both working fine till 4 days ago. I connect to a wireless network shared between 3 flats. Don't remember changing anything on settings tec.. but now the iMac looses internet connection every 10minutes or so and the PB can't connect at all. Both have full bars on the wireless signal indicator.However the PB Airport info in Network settings show's "Airport connected to 'wireless network' but has a self-assigned ISP and may not be able to connect to the internet". The iMac doesn't seem to have anything odd. The other 2 flats (with PC's) have no server problems and are working fine.
Any ideas anyone?

Self-assigned IP address, try to connect to pc

I do a lot of file transferring from my mac to another pc laptop, so I've got them hooked together with an ethernet cable. I had this issue in the past, where I'd try to connect but my network settings kept saying the "ethernet has a self-assigned IP address and will not be able to connect". The solution I found to fixing this was to open up the Advanced Settings, and change the IPv6 configuration to "Link-local only" and then everything would work perfectly.
I upgraded to Yosemite yesterday, however, and now that solution no longer works. Still getting self-assigned IP. How can I fix this??

I checked my sharing options, and everything looks to be on. I also have the yellow circle, but I can never get a connection unless it goes green. Before I upgraded, that was the issue before; it would be yellow until I changed the IPv6 connection to "link-local only" and then the ethernet connection would change to green, and I'd have no issues. Now, when I change it to "Link-local only" and hit apply, nothing happens, it's still yellow.
I tried to connect to the server just to see, and it won't connect. I get an error that says "There was a problem connecting to the server "AMANDA-PC" Check the server name or IP address, and then try again. If you continue to have problems, contact your system administrator."

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.

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 and renewing the DHCP doesn't give me a new IP no internet

When I went to connect to my wireless I wasn't able to, I ran a network diognostic and it said it couldnt fix the problem; normaly it works without a problem. I turned off my wireless box (netgear)and back on and still couldn't connect, my iPhone can and other pc's can. I started to look through the network preferences and saw it had a self-assigned IP. I took it to an I.T. technician at my college who also has the same macbook. He tryed renewing the DHCP but the same IP and subnet mask came up. I had recently updated the airport utility and thought it might be that but the technician had also and didnt seem to have the proble. Next we connected it by cable to the modem but that to had a self-assigned IP. We couldn't figure out what the problem is and he said all the settings I had were correct apart from the DHCP wouldn't renew.
Any help would be great, Thanks
Message was edited by: Spyonicle

I can also state the exact same issue with my MacBook. I am a consultant working for a large business customer, who has well-established hardwire and wireless networks. I have been using the company's WiFi guest network since Nov 2008, and starting the morning of June 5 I can no longer connect. BTW, my iPhone and every other Windows machine around here can.
Because I am able to connect to every Starbucks, library, home, and every other WiFi network that I try, the company's network support folks and I thought that my issue was related to a known DHCP server issue in the company's network configuration. Last night, this DHCP server issue was resolved, but my Macbook still cannot connect.
Do we have a known OS issue that affected everyone on June 5? I notice that there are no responses to this thread. In my past inquiries, this is usually the case when nobody responds. What is the next step toward resolution? Wait until September in hopes that OS 10.6 works better?
Message was edited by: tomfrenock

Self Assigned IP Addresses amber lights and no internet HELP!

Ok bear with me as I try to explain my prediciment!
I have an imac G5 with a Airport Extreme card properly connected and currently at full signal! The problem I'm having is that when i click safari (or IE) it doesn't load up any pages and a littke box pops up saying that it cannot find the server! so I go to network settings in system preferences and check the network status. I have an amber light and it says "airport connected to (my server) IP address self assigned your mac may not be able to connect to the internet" the problem is it is not self assigned it is done through DHCP.
I have had internet working perfectly at another house and it has worke don the odd occasion for a couple of days here so I don't think its a fault card (as i say it picks up a signal fine). I have tried putting in all info in manually but this has not helped (although on 1 occasion it did). I have baffeled the university technician with this problem. Im currently using ethernet to connect but this is no good as I need the computer in my bedroom and not the dining room (student accomodation) if you have any suggestions or have experienced this problem yourselves i would be delighted to hear of any answers and suggestions!

Hi,
Duane is right in that if ACL's (access control lists) are set on the wireless access point, (as they are in my school) you will need your mac address of your airport card to add to the router.
Here's what I would do.... Open up Network Prefs in the System Prefs app. Create a "New" location and name it whatever you want ("Wireless at Home"). In the "Show" drop down menu, select airport. You should see 5 tabs in the airport window. Airport, TCP/IP, PPoE, Appletalk and Proxies. Click the airport tab and select automatically where it asks you what default network you want to join. You'll also find your mac address for your airport card in that pane. Next, click on TCP/IP and select DHCP from the IPv4: drop down menu, make sure no information is showing in this window. In other words, no numbers in DHCP or DNS servers, etc. If it's blank and ready to go, hit apply. The router should then hand off an IP address. Close system prefs and look in the menu on the upper right hand corner of your screen (by the date and time). See the airport fan? Does it have black bars through it? Or are they grey? Or, does it just look like a blank semicircle (airport is not turned on). If you don't see this menu, go back to network prefs and open the new location you've just made and go back to the airport tab. There is a check box in there that says, show airport status in menu bar. Turn that on. Now, go back to the menu and if the bars are grey, click on the fan and see if your network is listed there. Click on that to join. You have made a new location with fresh DHCP settings and told your airport card to connect automatically to whatever network is available.
Your tech guy at school is probably a PC head and that's why he's been stumped. He shouldn't be.
Hope that helps.
Tim
Tech Asst
Bertschi School
Seattle, WA.
Power Mac G4 667 Digital Audio Mac OS X (10.3.8)

No internet - self assigned ip problem?

I have an Intel imac (OSX leopard, 10.5.8 )and an ethernet modem connected direct to it. The lights are on as usual on the modem but i cannot get the internet. When I look at the ethernet status in network in system preferences it says I have a 'self assigned ip'and may not be able to connect.
I've tried using the mac assistant which tells me I have an ethernet connection but says that both the internet and server have failed. This assistant also advises on ISP status and having run the test a few times it tells me sometimes that the ISP is ok and other times that it has failed. I have tried running the ethernet to an airport express too. Again this lights up as it should (solid green light) but still provides no internet. I've tried connecting to this wireless network with the imac and with an ipad too. Both find the network and connect to it but neither can get any internet from it. Any advice anyone can provide would be very much appreciated, thank you.

Ive been having a similar problem myself. Heres the situation:
Everything runs smoothly with Airport. No issues there. Ive had to invest in a couple home plugs in order to get better wireless signal at my other accomodation. Was fiddling around trying to set up the ethernet connection but it doesnt seem to want to connect beyoun Network settings. ISP, internet and server all fail.
Im completely stumped as to why this is happening when my mac is able to freely connect wirelessly to the same network. I took into consideration it may be a problem with the homeplugs but ive tried a direct connection into the router via ethernet with the same result. Any help would be greatly appreciated.
Regards
Router: DG834G v2

Self-Assigned IP via router - no internet access - HELP!

Hi all,
I have 10.5.7 leopard installed on my C2D Macbook.
In the past, I never had any issues connecting to wireless routers with internet connection.
As of late, I am currently getting 'Self assigned IP address' which does not allow me to connect to the internet. It is connected to the router, but just no internet access. I can see the other Shared computers (Windows PC and mate's macbook pros) but just no web access. And they do not have a problem connecting to the internet.
I have attempted the following:
1) Turned on & off Airport.
2) Deleted network connections and re-created them, rebooted in safe & PRAM modes.
3) Deleted router Key chain permissions & changed permissions to 'access all'.
4) Deleted plist files from /Library/Preferences/SystemConfiguration/
5) Off Firewall & verified against the logs to ensure it is disabled.
6) Re-installed 10.5.7 combo updates.
7) Rebooted router, changed router channel, etc. Router is on the latest Netgear firmware.
8) Assigned IP address and entered the DNS, router values manually in Leopard.
9) Clicked on renew DHCP lease several thousands to no avail..
Occasionally, DHCP will work. But once I reboot & awake the mac the internet connection drops and 'Self Assigned IP' happens.
Does anyone else have any ideas? My only conclusion is that the bug is in Leopard 10.5.7.

Make sure your router has the latest firmware. If you are out of range of the WiFI or in a marginal area, this error simply indicates that your computer is not able to access an internet router/server and simply assigns the default IP address which is of the form 169.254.xxx.xxx. Basically it's a flag that lets you know you are not connected to a DHCP server.

Self-Assigned IP fix?

As with a number of users in the community, my wired Ethernet connection has reverted to a self-assigned IP. Are there any viable solutions to this problem?

OK, so I hit this problem yesterday and I thought it was just one friend's mac. This morning I found that several macs were having the same problem on wifi. (Ethernet was OK, but not wifi.) I have SOLVED it for me - so here's the info in case it helps!
NB - I have tried most of the solutions on most of the help threads. (Once, years ago, I had the same problem, and one of the fixes I found back then did work. I think it was either deleting the wifi setting from Network Preferences or fixing the keychain or both. But this time, those fixes were achieving nothing.)
Anyway, the solution was simple! My modem-router included a setting for its DHCP server that was limited to 20 addresses. In other words, it was offering addresses from 192.168.1.1 to 192.168.1.20. At first I dismissed that possibility, since you'd think 20 would be plenty for one house! However, I was very wrong. Here's why.
1. Yes, we do own several Macs, and some of these are connected by ethernet AND wifi, so those ones use two addresses each.
2. Yes, we own several iPhones, iPods, an AppleTV etc.
3. Yes, we had visitors in the house. My daughter's friend had brought her iPad; my parents had brought their laptops and their phones!
4. I have an Airport Extreme and a Time Capsule, both connected (in Bridge Mode) to the modem-router, so that's two more addresses.
5. Remember that DHCP leases last for 24 hours (or whatever your router is set to), so even when visitors are gone or machines are turned off, those addresses might not become free.
SOLUTION? I changed the router's setting to offer all addresses up to 192.168.1.40. (I might even go back and offer even more than 40 - no reason why not).
My wifi macs had no trouble from that point. Hope this helps!
[NB - The reason my ethernet was always OK was that those connections had been running a long time. But if an Ethernet connection had gone down, and I had reconnected it at a time when its address had been stolen by another device, then I likely would have hit the same "self-assigned IP" error. In other words, in my case I don't believe the issue made any real distinction between wireless and wired connections.]

Self-assigned IP, no IP, no authentication server!

Similar Messages

Maybe you are looking for