No Internet. A Self-Assigned IP, DHCP & Comcast.

Well, weeks ago my internet has been working fine. And as of now it died.
I have Comcast high-speed cable internet running from their "Comcast Home Networking" router (LinkSys Model WC6200-CC). There is also another user who has internet, and he has a wirelessly connected laptop Dell PC.
Like I said it was working fine a while ago, for both of us, but unexpectedly the internet has been dropping for my housemate, then mine. We called Comcast, they fixed "his" problem and were troubled with mine. I kept on getting this "Self-Assigned IP" address that has the 169.x.x.x number thing going on. They didn't know what to do, they referred me to here. And I consider myself fairly good with my computer, so I invesitaged and tried all solutions available.
The odd thing is that my internet works 100% fine on SAFE-BOOT and CLASSIC. The IP and settings are fine, but when I go in normal OS X MODE, it does not work at all. A startup item? a faulty extention, bundle, file?
I resetted the cable model a billion times. Restarted the computer a trillion times. The renew "DHCP lease" button doesn't do anything to the 169.x.x.x numbers, Comcast refuses to give me the DNS servers I would need to configure manually (read on a different post here) as they said it should be "automatic and dynamic" and no need for me to do. And I also did the thing intended for 10.2 on IPConfiguration.bundle, that didn't go anywhere.
I am totally out of ideas!
P.S. I am posting from Safe-Boot.

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.

Similar Messages

Using WPA results in "self-assigned IP" / DHCP not working / Comm prob?

Hi,
New to the forum...just replaced all wintel boxes with new macs (macbook pro and mac mini; both at 10.4.6) talking to a new AEBS (updated firmware) which is connected to a Comcast cable modem.
Configuring the AEBS without security results in a very happy network...good range and DHCP behaves properly...handing IP addresses to both clients promptly and the throughput as reflected by www.speakeasy.net/speedtest is great.
Adding wireless security to the mix, be it WPA+WPA2; WPA2; WPA; WEP, creates problems. If I configure the AEBS with WPA+WPA2, for instance, put in a password, update the router, reboot the cable modem and the router, delete any existing preferred networks, add a new preferred network with WPA2 and the correct password (btw, I have cleared my keychain to avoid any password caching problems) and apply the changes the following behavior occurs like clockwork: The client connects to the AEBS, as reflected in the status in the network preferences window and the internet connect window, but it never gets an IP address from the AEBS and is stuck in the "self-assigned IP" / 169.x.x.x abyss. I wait much longer than 40 seconds and nothing ever changes. In addition, attempting to configure the AEBS while in this state (from airport admin utility) results in a very long attempt to read the configuration which never works - I need to connect with ethernet to reconfigure. If I go back and remove the security policy on both sides the network works just fine...including the ability to configure the AEBS over wireless.
For the record, the AEBS settings are: Open network; channel 11; b only; no interference robustness set; uses DHCP for IP from cable modem; distributes IP addresses - shares single IP address using DHCP + NAT using 192.168.1.1 addressing. All of that seems appropriate and correct but, hey, it ain't working and I am out of ideas.
All help is welcome! Thanks.
macbook pro Mac OS X (10.4.6) mac mini
macbook pro Mac OS X (10.4.6) mac mini
macbook pro Mac OS X (10.4.6) mac mini
macbook pro Mac OS X (10.4.6) mac mini

Hey Rich,
I eventually got mine to work but I really cannot give you a clear view of how...it was hit or miss. If you are running into the same thing, I might be able to guide you to the same resolution.
When you turn on WEP or WPA, does the network connect but not get an IP address from DHCP (self-assigned address abyss) or does it not connect at all? Asked another way, what does the system preferences / show / network status page say for the wireless network in question?
-matt
macbook pro Mac OS X (10.4.6) mac mini

Self-assigned IP (DHCP is not getting correct IP address)

I just moved and got my internet connection not long ago. When the installation people were there, they tested the internet connection by plugging the ethernet cable directly to my girlfriend's macbook (one of those new white macbooks). It worked pretty well. I set the router up then, and it worked fine.
The problem is: I can connect wirelessly to the LAN created by the router (and internet works), but if I try to plug the ethernet cable directly from the modem to my macbook, it will self-assign an IP address and I can't get a connection. This problem has never happened before, and it happens just at home (no matter how many times I try to reboot the modem). The funny thing about it is that it still works if I plug the ethernet cable directly to my girlfriend's macbook instead of mine.
Can anybody give me a suggestion? Just to make sure: my mac (as well as my girlfriend's) runs snow leopard.
Thanks in advance,
Davi

There's no common issue.
All a self-assigned IP address means is that DHCP did not assign you an IP address.
This can occur for a variety reasons, from the DHCP server only issuing one address per network (many DSL modems do this) to running out of addresses (many cable modems will issue up to five but no more, and many routers will not issue more than ten.)
The brute force fix attempt is, as mentioned above, to power off your Macs and other machines, power off the router, then power off the DSL or cable modem. Wait a minute, then power them up in reverse order (DSL/Cable modem, then a minute later the router, then a minute later your PCs/Macs.)

Unable to connect to internet as Self assigned IP address Since Aple repair

Right this is currently winding me up a treat and i am posting this via windows under bootcamp on my iMac as it is the only way i can connect to the internet.
Picked my iMac up from the Apple store in Bristol UK (i dont know if this is related or not) but the problem has only happened since the repair!
I cannot connect to the internet or any services that use internet access, and under network settings, under ethernet it says connected (light in green) but you may be unable to access internet and it is self assigning IP address. If i go into advanced and renew DHCP nothing changes, its still has an IP address beginning 16 not 192. as normal.
I have repaired permissions, reset the Pram restarted and nothing makes any difference! The router settings have not changed and are not at fault. i can access the internet from my Mac via bootcamp, or 2 other windows computers in the house and my iphone via wifi.
Note my Mac wont connect via wireless either as it also self assigns IP address.
I dont know what to try now and am getting fed up with this, as i never have problems that dont make sense with Macs i have been an avid user for 10 years, and am well clued up with them (normally).
Can anyone shed anylight? Its a 2007 2.4Ghz Intel Core2Gb Ram 320Gb HDD 265Mb Radion HD Pro. Running OS 10.5.7 (not updated to 10.5.8 as came out when it was in for repair and i havent been able to access since)
Thanks to anyone that can help!

Right i have just rebooted after reading another post and under Security>Firewall>Allow all incoming connections this seems to allow me access (well currently so anyway)
But surely this isnt right? IF i then go back to Set specific access its now ok, but i imagine it wont be if i rebooted with it like it was before.
Also i notice i now have the follwing under allow access (which werent there before it went to the Apple store for repair)
ntpd
nmblookup
krb5kdc
I dont know what they are? Could it be this?
Thanks

Can't connect to internet..self assigned ip address problem with DSL Modem

I've run into this before, without resolution, and now again on a friend's iMac. Time to ask around...
Basically, everything appears to be assigned and configured perfectly, but the network status always shows, "...you have a self assigned IP address and may not be able to connect to the internet". Sure can't connect to the net when it says that.
I've gone thru the procedure advise before that details the sequence of events needed to insure the modem resets and recognizes the Mac and it's incoming DSL (sbcglobal) signal. The order of network priority is set properly by dragging built in ethernet to the top of the list. Modem was powered down, plugged in, and then connected to the Mac, but no solution. Any ideas? thanks

This continues to be a mystery. I've had my powerbook on several networks, and connection has, most of the time, been an automatic process. Additionally, I've installed new systems for people with the same isp, and all has been well. So easy is the process, it's never been an issue. However, following explicit procedural instructions (including powering the Mac down), has proven unsuccessful on 2 different occasions.
There is little help with the isp support in India, which is where the call routes too.
The only thing I have not done is to swap out the cable at one of the locations, but the other location, which has the same issue, works fine on the iMac there. Only when I connect my Powerbook to the modem, does the "...self assigned ip address...not be able to connect to the internet" appear.
I just keep thinking there has got to be a small detail that is being overlooked.

Self Assigned IP / DHCP problem : sharing my fix.

Okay. I WAS frustrated for a long two weeks before I figure this out. It seems that this problem has affected a LOT of people out there, and since I now am (supposedly) free of this thing, I want to share my hypothesis of the problem's roots (A) and my fix (B).
Note that:
- i'm free of this problem since the last one week, so .. well, hopefully this is right.
- the problem happens almost anywhere, with any router types, and in any connection type, be it ethernet or wireless a/b/g/n.
- the problem is automagically fixed by running into safe mode.
- the problem keeps happening again and again, although you have powercycled everything of the electronic peripherals in your house, even by disconnecting your phone/ADSL line and main power fuse.
- disabling the Mac OS X Application Firewall sometimes cures it, but most of the time it happens again.
- AFAIK (correct me if i'm wrong), the ipfw, mother of all OS firewall, exists within Mac OS X, and the Mac OS X Application Firewall (i call this OSXAF) has nothing to do with ipfw.
A. My hypothesis and the reasons.
* for an unknown reason, there is a rule created for ipfw that tells it to block the ports 67 and 68, both are the common DHCP ports.
* because of that, your Mac cannot contact with any DHCP servers, anywhere. This forces your mac to assign an IP address by itself.
* disabling OSXAF incidentally removes that rule, but after (one or a few times) reconnect or reboot, the rule appears again.
* powercycling your routers or anything related does not concern ipfw, thus has no effect whatsoever to the problem.
B. My fix.
1. Get the WaterRoof free ipfw frontend (forgot the site, just google)
2. Open it.
3. Go to Static Rules part.
4. Find everything which reads "deny blah blah blah port blah,blah,67,68,blah blah"
5. Edit those rules so that there is no 67 and 68 inside.
6. Open tools -> rules configuration -> save to startup configuration -> yes.
7. Open tools -> startup script -> install startup script -> yes.
That's all.
For me, this seems to be a permanent fix. Please note that the startup script mentioned before exists in all *nix-based machines, so don't worry about startup time, there'll be no slowdowns (again, please correct me if i'm wrong, i had only little experience with *nixes). Besides, i suspect that if you don't save and reinstall that script, the previous script is the one which has 67 and 68 inside.
Hopefully this helps. Any corrections, comments, suggestions, and/or knowledge are welcome.
Cheers,
-bam, the noob.

OK, so a little background -
I have an MBP with 10.5.5 (which I downloaded yesterday, so that's not the issue). This year at school they upgraded the wireless system and network control to Foundry routers and Bradford Securities Network Control. Problem is, my computer is intermittently and randomly having a hard time sticking with one IP and staying away from a self-assigned 169 IP. The System Prefs are fine, and even when I change to manual settings for the IP, it doesn't stick. I checked the terminal (tcpdump) and it seemed to be having a tough time accepting one of the two IPs the servers offered (there are two servers for redundancy). It asked for an IP, gets two offers, and then asks again. I was stumped, and so were the IT guys on campus. And it's not just me, many other 10.5 users are having the issue. And it's not the network, because nobody else is having the issue but 10.5 users. Certificate problems are similarly eliminated from possibility.
The IT guy showed my this thread, and I was excited, so I first tried to just shut off the Firewall all together, and that worked, briefly, but now it doesn't matter if the Firewall is on or off, the problem persists. I tried your WaterRoof method, and the similar program NoobProof, but there were no rules relating to ports 67 or 68 at all, let alone denying them. (As a side note, when my FW is off, there's only the rule allowing all IPs in and out, and when it's on (but only allowing specific programs) it gives a second rule that denies "icmp from any to me in imcptypes 8." No idea what that means.) I've been watching tcpdump and the FW logs closely (as well as the console itself), but nothing has changed. The only interesting thing is that when the IP changes from the (good) 137 IP I'm supposed to have to the (bad) 169 IP, often times (in fact, most times) there is no firewall activity. The console says that the en1 link (wireless) is now down, and the tcpdump picks up the computer asking for an IP again, but the firewall logs pick up nothing, neither through the console or through WaterRoof. Which is weird, because I thought it was a FW problem (as did the IT guys), but the logs show that only occasionally when the servers offer me an IP does the FW block the request, but not all the time.
As another point to note, this is not only an issue with the wireless. The wired connection (Ethernet right into the wall, and attempted from many different plug-in sites) also has this issue.
My only conclusion is that the FW is buggy, or that the logs are missing denials, neither of which makes much sense, IMHO.
Any thoughts?
EDIT: Shutting off the FW often solves the problem, but not always. Sometimes I can get a correct IP even with the FW in full swing without anything popping up in the logs. And sometimes I can't.
Message was edited by: kangasaurus

Ethernet card issue...can't get rid of self-assigned IP

Hi folks,
I am using an circa 2005 iMac G5 PPC desktop with 10.5.8. I am trying to connect the iMac to my Time Capsule via ethernet cable, but seem to be having problems with my ethernet card. When I plug into the TC ethernet port, the TC drive, does not mount and I cannot access the worldwide web.
When I go to System Preferences --> Networking, the tab on the left for ethernet connection shows a green dot, says "self-assigned IP" and the status says "connected" PRIOR TO CONNECTING THE ETHERNET CABLE TO THE TIME CAPSULE. It shows a "self-assigned" IP (DHCP selected) of 169.254.69.249, even though I know my TC is 10.0.1.1. Turning the ethernet off then back on, renewing the DHCP lease, nothing seems to be able to make this 169 IP address go away. The wireless connection to the TC is just fine... everything does what it should, I just can't get the ethernet cable connection to work.
Out of curriosity, I went to the System Profiler, and on the network tab it shows ethernet IPv4 169.254.69.249 (name en0).
I know it's not the Time Capsule, as I connected my laptop to it just fine via ethernet. The TC was IP 10.0.1.1 and it assigned 10.0.1.5 to my laptop (I have a variety of devices on my network), and I was able to transfer data and access the internet with no issues whatsoever.
I live in an 32 story apartment with a built-in ethernet network and ISP included in my rent. It's pretty nice, high speed. I connect from the wall to the Time Capsule via ethernet (circle dot connection port, so I know I have the right port), and then wirelessly out to a couple of laptops, a couple of Airport Express, and of course my desktop.
Bottom line, I think the ethernet card on iMac G5 desktop has gone bad: A few questions:
(1) Any ideas what may be wrong? Has anyone seen this self-assigned IP thing that won't go away?
(2) Any ideas how to fix it?
(3) How much will it cost? It may be time to replace my 6-year old desk top computer.
Thanks, Andy

I've swapped out several cables still with no luck, and the current cable definitely has 8 pins and worked with my laptop, so I'm confident it's not the cable. Also, the Time Capsule seems to be OK, because it too worked with my laptop using the same port. The only variable that doesn't seem to be cooperating is my desktop computer.
Also, I have tried to manually assign an IP consistent with the network & appropriate subnet mask. It seems to take the IP address manually, but still I can't get internet access, and can't ping the Time Capsule in network utility either.
Finally, when I connect the desktop directly to my wall outlet, taking the router out of the equation entirely, network diagnostics shows ethernet failure...
Does that sound like a bad ethernet card?
What does it take to replace an ethernet card in an iMac G5?
Cheers, Thanks, Andy

Can't delete a self-assigned IP address...

Hi folks,
I am using an circa 2005 iMac G5 PPC desktop with 10.5.8. I am trying to connect the iMac to my Time Capsule via ethernet cable, but seem to be having problems with my ethernet card. When I plug into the TC ethernet port, the TC drive, does not mount and I cannot access the worldwide web.
When I go to System Preferences --> Networking, the tab on the left for ethernet connection shows a green dot, says "self-assigned IP" and the status says "connected" PRIOR TO CONNECTING THE ETHERNET CABLE TO THE TIME CAPSULE. It shows a "self-assigned" IP (DHCP selected) of 169.254.69.249, even though I know my TC is 10.0.1.1. Turning the ethernet off then back on, renewing the DHCP lease, nothing seems to be able to make this 169 IP address go away. The wireless connection to the TC is just fine... everything does what it should, I just can't get the ethernet cable connection to work.
Out of curriosity, I went to the System Profiler, and on the network tab it shows ethernet IPv4 169.254.69.249 (name en0).
I know it's not the Time Capsule, as I connected my laptop to it just fine via ethernet. The TC was IP 10.0.1.1 and it assigned 10.0.1.5 to my laptop (I have a variety of devices on my network), and I was able to transfer data and access the internet with no issues whatsoever.
I live in an 32 story apartment with a built-in ethernet network and ISP included in my rent. It's pretty nice, high speed. I connect from the wall to the Time Capsule via ethernet (circle dot connection port, so I know I have the right port), and then wirelessly out to a couple of laptops, a couple of Airport Express, and of course my desktop.
Bottom line, I think the ethernet card on iMac G5 desktop has gone bad: A few questions:
(1) Any ideas what may be wrong? Has anyone seen this self-assigned IP thing that won't go away?
(2) Any ideas how to fix it?
(3) How much will it cost? It may be time to replace my 6-year old desk top computer.
Thanks, Andy

same problem here. My biggest gripe . . . why isnt there a response from apple to this weeks old problem!!!! Do a google search for this problem . . . . thousnads of hits!!! *** apple!!?? Fix this dang problem!
brand new imac!!!

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

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" won't connect to Internet

I have two Macs connected to my DSL modem: a MacBook Pro (10.5.2) and a PowerBook G3 'Pismo' (10.3.9). Yesterday both were working fine, but just now when I started up the PowerBook it told me "Built-in Ethernet has a self-assigned IP address and may not be able to connect to the Internet." Indeed, though the cable is connected just like yesterday, there's no Internet (though the MBP is connected just fine).
Anyone have any idea why this happens, and what to do about it? I've tried disconnecting/reconnecting the cable, and restarting the PowerBook, to no avail.

Your router uses a system called DHCP to allocate an IP number to any computer connected to it. So when a computer is booted, the router recognizes its presence and allocates it a number. If the computer is running 24/7 the number's 'lease' is usually renewed every few days.
Sometimes the process falls over and the computer fails to get an IP number from the router: when this happens it allocates itself an emergency number with the results you describe. As you found, rebooting the router usually clears the problem.
It may be possible to reprogram the router and the computer to use a fixed IP number, it depends on the router. Very possibly this would prevent the problem occurring since both ends would 'know' what the number should be from the off.

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

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)

Self-Assigned IP error and no Internet thru cable, but fine via Airport crd

I am having a vert weird problem. Airport base station hooked to a LAN router, new Mac Pro (10.5.1) hooked via cable to Airport base station. I get the self-assigned IP address and no internet. This happens also if I hook Mac Pro directly to router via cable. Oddly enough, during all of this, my iBook connects fine to the Internet, thru the base station using its Airport card. What gives, I may throw in the towel and go out and by an Airport card for my Mac Pro to get Internet connectivity, even though it sits only 6 inches from the base station. Also not, my Power Mac G4 was hooked via cable to the Airport and worked just fine...
If someone discovers a fix, please feel free to email.
Thanks,
Bob A.

Funny you should mention that. This weekend I noticed that I can get an IP address and internet connection, either via the Ethernet cable from my AEBS or wirelessly from the AEBS on my laptop, but only one at a time and it depends which computer (iBook or Mac Pro) is on when the AEBS is toggled on/off. The only exception is my iPod touch, which can get an internet connection no matter which is the Internet connected machine(how's that for bizzare ?).
So, it appears the Linksys router that is hooked to our building's LAN is not distributing IP addresses (disconnecting the router and connecting the AEBS directly to the LAN produces the identical single IP address situation). Since using my Mac Pro with Leopard, I can only set up the AEBS in bridge mode, putting it in the DHCP mode causes the AEBS to be undetecable by the Mac Pro (haven't checked if the iBook sees it).
So I guess the questions are now:
- Shouldn't my router be assigning IP addresses from the LAN, isn't that it's job? Should I try buying a new one since I can't get AEBS to DHCP?
- Why would my iPod touch me immune from the single IP address situation?
- Any idea how to get Leopard to allow my AEBS to use DHCP?
Now I say I can't use DHCP, I mean that if I reset the AEBS, start from scratch and use assisted setup with Airport Admin Utility, and select DHCP at the place where you select Bridge or DHCP mode (or whatever the DHCP mode is called, I forget)the AEBS disappears. If I set bridge mode and then dicker around with DHCP manually, it doesn't disappear, but then it just won't give an IP address to any computer til re-rest and put back in old plain Bridge mode.
I would prefer to run the LAN right into AEBS and have it act as router and all that. I would also be fine with having a router and letting AEBS just bridge, just as long as I can connect to the Internet on more than one computer at a time.
I think I have a basic knowledge of what's going on, although my use of proper terminology is lacking, so feel free to follow up with any questions, I'd be happy to clarify.
This Leopard Mac Pro replaced a PowerMac G4 with Tiger and this all worked fine with it. When I traded computers and didn't get Internet I reset and re-setup the base station, so this might all be a Leopard problem
Of course, it brings me back to shouldn't the router hooked to my building's LAN be distributing IP addresses?
Thank you in advance for your help on this isssue.
Bob A.

No Internet. A Self-Assigned IP, DHCP & Comcast.

Similar Messages

Maybe you are looking for