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

Similar Messages

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

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

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

  • Self-assigned IP problem - still no resolution!?

    I have a Macbook which is about two and a half years old. I have never experienced any real problems with it, especially regarding connections. I have been connected to my home wireless network (BT homehub) ever since I got the laptop with no issues. It has always picked it up the second I turn it on and never drops.
    One day, I was traveling back home on the train and I tried my luck at connecting to the trains free wireless, but it didn't work. When I arrived hom, my computer would not connect to our wireless. Somehow when trying to connect to the trains wireless, my preferences must have changed or something meaning that my airport now has a "Self-assigned IP address and may not be able to connect to the internet".
    I went through all of the diagnostics and assistant things, but just kept going round incircles. I re-booted, I tried everything I found online on tis community and others but nothing works.
    I have renewed the DHCP Lease - No luck. It says "Configure IPv4: Using DHCP", so it's not that.I tried connecting via Ethernet, but I have the same issue with the Ethernet connection via Airport.
    It is not my Router or internet connection because others are using it in the household with no issue. I went a week or so not knowing what to do. Then I had to go back to Uni for a while - there I was able to connect to the internet using the Ethernet cable they provide (we don't have wireless so I couldn't test that) and that was fine, working as smoothly as it has done for the two years I have had the laptop.
    I am now home, and still cannot connect to the internet. Can somebody please give me any other options/advice? I am at a loss, and desperately need to access the Internet for work!

    I was having the same problem with the wifi not connecting to our home network on only one of our Macbooks.  It kept giving itself a self assigned ip address.  Everything else would connect fine to the home network and the computer with the problem connected fine to every other network aside from our home wifi.  After reading this thread and trying everything on it, this is what finally fixed it:  I didn't have anything under the 802.1x tab either.  So I:
    Turned the Airport off and completely deleted the Airport in network preferences.
    Then I went to keychain access and deleted EVERY wifi network password saved under both Login and System. 
    I turned the computer off and removed the battery and did the SMC reset by holding down the power button for 5 seconds. 
    When I restarted the computer, I reset the PRAM by holding down OPTION, COMMAND, P, and R at the same time RIGHT AFTER I pushed the power button to turn it on and before the grey screen appeared. 
    It reset and when the computer was back on, I added the airport again and joined my home WEP wfi network.  It worked perfectly!  Now I don't know if all of these steps are required to fix the problem but this is what worked for me.  The Macbook with the problem was a black Macbook running 10.6.8.  Good luck!

  • Airport Self-Assigned IP problem

    I have a problem where my MacBook will occasionally not connect to certain wireless networks. When this happens, the Network preferences says that the AirPort is connected with a self-assigned IP. This doesn't just happen on my computer, it happens on 2 other MacBooks and 1 MacBook Pro, and there are times when 1 computer will not connect but the other 3 will.
    I have tried power cycling the AirPort, renewing the DHCP lease, flashing the PRAM, creating a new network location and usually, none of these things work.
    The computers are white MacBook's with OS X 10.5.8 and a MacBook Pro with OS X 10.4.11. The router is very often inaccessible as it's someone else's network, but I don't think this is the problem as only 1 computer usually has a problem.
    Any advice would be greatly appreciated!

    I have also experienced this problem. Here's what I learned. After executing a "Safe" restart (holding down the shift key during restart), I restarted in normal mode and was greeted with two queries. mDNSResponder needs permission to accept incoming traffic and same thing for configd. These are functions that apparently are needed to pick up an external IP address from the DHCP service. I looked at the firewall log and saw a long list of denials corresponding to when I lost my IP address.
    The messages also note that accepting these things automatically can be set in the system preferences panel. I could not figure out how to enable these specific applications - maybe someone else can help - but if you go to System preferences pane, Security, Firewall set to allow all incoming connections. This fixed my problem, however at the cost of some security.
    Must be a better solution.

  • HT204210 self assigned ip problem after the latest update !!! help anybody

    I have this stupid problem and don't know what to do . When I try to connect to the wi-fi network at the office I got ''self assigned ip'' and can't connect. At my network at home I have no problems . Any ideas?

    Do you thing this could help ?
    http://www.cnet.com/news/fix-self-assigned-ip-addresses-in-os-x/

  • Many useless tricks to fix self assigned ip problem

    As one of the thousands Mac`s victims of this unbelievable problem "self assigned ip" I have tried many of those tricks available in the net. No one works always and many of them gives a partial or temporary solution. you may read a huge number of opinions from people who don't know what are they talking about. A few tricks are "magic" : any technical reason to work!!!
    No news from Apple after 6 years and three different OS history of this problem. A shame!!
    please come to this issue and give your contribution, if you really know about this problem.
    appreciate

    This is shocking isn't it? Just unpacked my new macbook pro today and have been battling all day with this problem. My first big gripe with Apple after many years. I refuse to even try the solutions that just sound daft but am getting desperate.

  • Self-assigned IP address problem - My solution

    I am new to this board and created an ID just to write this post. When I searched for this self-assigned IP problem, I found almost 1 million results on Google so obviously I am not alone.
    I have this problem off and on on the wireless network at home with a Netgear router. It has never happened at my office with a D-Link router. Never happened at Starbucks or McDonalds (yes, they all offer WiFi here). But it happened at one Pizza Hut and it also at Christchurch airport about a week ago.
    Deleting one of the plist files worked once at home many months ago but this week nothing worked. My Mac usually goes back to normal by itself after I "****" it out at other WiFi networks but not this time. As a last resort, I asked my brother (our family's I.T. guy) to change the router as I had not tried that fix. He didn't do it but a day later, he gave me to oddest solution that worked in a blink of an eye.
    The solution? Key in a wrong password!!!
    1) Go to Keychain Access, delete the keychain for the problematic network.
    2) Connect back to the network
    3) Enter a WRONG password that is similar to the right one. For example, if your password is Apple123, try APPLE123. You should still connect to the network and get a self-assigned IP.
    4) Repeat Step 1. To be safe, you might want to re-boot now. I did but probably didn't have to!
    5) Repeat Step 2
    6) Enter the right password
    I'm not all that techie so all I understood from what he said was:
    1) It's probably a non-Apple router bug
    2) It's a hex key problem. The password wasn't being encoded/decoded properly so the router wasn't assigning the computer an IP address. Wasn't even reading the password which is why I could connect with a wrong one.
    He deduced that from reading a post from a guy in Spain who thought he had carelessly entered the wrong password and was wasting the community's time with his posting. I had read that post a couple of days ago too! But obviously I thought the Spaniard had just entered the wrong password and there was no fix for me to try out. My brother is a genius!
    I guess it then makes sense why fixes like:
    1) Disabling the firewall
    2) Deleting preference lists
    3) Deleting keychains
    4) Changing the router
    5) Renewing DHCP lease
    6) Resetting the router
    ...have worked for many people and not others. None of them actually fix the cause of the problem. Having searched for 3 days, I could not find the REAL reason why this happened. Personally from all I have read, I think it must be a hex key problem with Netgear and Linksys routers. I see those 2 names mentioned a **** of a lot. Maybe it's another one of those gadgets built more for PCs that don't work perfectly with Macs all the time. We used to have an Apple Airport Extreme base station but that got fried by lightning. It was not cheap.... So technically, it really isn't Apple's problem. I think if we used an Apple router, we wouldn't have a self-assigned IP address. Maybe that's why they haven't "fixed" the problem after so many years.
    Anyway, let me know if my brother's fix worked for you.
    This is my good deed for the weekend! Goodnight....!

    Hello, thanks for the tip/post, & a warm welcome to the forums!

  • "self-assigned' IP address.

    Firstly to be semantic. Part of my frustration at this problem is the fact that Apple call this a "self-assigned" IP address. In no way have I assigned this IP address myself. My Macbook Pro assigned it for me.
    I have had this problem intermittently since I bought my Macbook Pro years ago. The first time I found a solution by renewing my DHCP lease and sometimes that would work, sometimes not.
    Second fix is a reboot, third fix is to make airport inactive and then re activate it again, fourth fix is to add new location from system preferences and then start from fix number one again
    I have also tried various commands suggested for terminal and tried deleting folders that have been suggested as the cause.
    But now returning from a trip overseas I get the "self [apple] - assigned IP address" message and none of the fixes that I have wasted my time applying in the past are working.
    It's almost comical because just a week ago I was saying to somone how I was thinking of moving to PC as I had had enough of trying to fix problems with my Mac.
    Hours of trawling the internet for a simple walk through of the problem suggests anything beyond what I  have already tried. I can't believe I have put up with this issue for so many years, just accepting that it's a small problem that occaisionally interupts the massive benefits of using a Mac.
    So if anyone has a final suggestion of where to go to fix the problem [on line] I would be so releived of my frustrations. If not then I am heading out to buy a PC tomorrow and I will take great pleasure in destroying my Macbook Pro.

    I have a little Macbook that connects to my wifi connection automatically without any problems and always has.
    I have a much more expensive, much more powerful 2010 Mac Pro Quad Core which is totally incapable of jumping on to the same Wifi Connection. Even if both devices are right next to one another.
    Of course, I have the usual 'Self Assigned IP' problem, and like you, I have trawled the internet endlessly following all sorts of guides, all sorts of DHCP Renewal methods and all sorts of manual methods and all sorts of Firewall settings etc etc etc.
    In the end up, none of it ever works. Except for the very rare occasionally day I'll turn the Mac Pro on and it will have randomly decided to connect to the WIFI connection and work fine.
    I gave up trying to figure it out. I can no longer connect to the internet so my Mac Pro has to live with no important updates etc. Not very future proof at all and extremely frustrating.
    I run a busy recording studio so its solely the fault of this problem that I struggle to be as competitive as my rival studios as I can not preform the simple Audio software updates everyone else can. Brilliant.
    INFURIATING.

  • Self Assigned IP Mayhem

    Hi Everyone,
    I've fallen prey to the dreaded Self Assigned IP Problem. After spending the majority of the day scouring this community and a few others, I've come to realize it's a common (if not exasperating) issue. Here are the specifics:
    - MacBook Pro running Mac OS X Version 10.6.8
    - All software is up to date
    - AirPort Extreme  (0x14E4, 0x8D)
    - Ethernet works consistently only when airport is turned off
    - First time issue with airport at this (or any) location
    Here are the troubleshooting solutions I've tried so far:
    - Rebooting the router
    - Power cycling the router
    - Having the Internet company (TWC) completely erase the network and create a new one from scratch
    - Having the Internet company reboot the modem
    - Deleting the Network from my Preferred Networks
    - Deleting the Network from my keychain
    - Deleting com.apple.alf.plist from my Library and Trash
    - Creating a new Location
    - Manually assigning the IP (this was met with the most success so far - I lose the self assigned IP problem and show that I'm connected, but I don't actual have a connection, still no internet access - but it was truly a shot in the dark, I have no idea what I'm doing)
    - Renewing the DHCP lease
    - Entering a random string of numbers in the DHCP ID
    - Turning the Firewall Off
    - Rebooting my computer after every new troubleshooting attempt
    So now...I'm at a loss. Anyone have a different solution that worked for them? Or a suggestion about a step/combination of steps that I might have done incorrectly? ANY help would be so appreciated!
    Thanks in advance!
    Beka

    Linc, THANK YOU!!! That solved the problem! For anyone else having this issue, here's what I did:
    - Deleted the original network information from my Preferred Networks
    - Deleted the password from my keychain
    - Turned AirPort off
    - Reset the Router
    - Switched from WEP to WPA with information from this article: http://www.tech-faq.com/how-to-change-wep-to-wpa.html
    - Turned AirPort on
    - Connected with the new password
    - Renewed the DHCP Lease
    - Applied the settings and waited just a minute
    - And done! I finally had my connection back!
    I'm not sure how much of that is right/wrong, but it's what worked for me!
    Thank you so much for your help, Linc!

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

  • Frustrated with apple self assigned IP (ethernet)

    Hi,
    I have ethernet self assigned IP problem. Can anyone help ?

    If the computer is connected through a switch to a cable or DSL modem, and the modem is not acting as a router, then only the first device to connect will get an address. You need to change the configuration of the modem so that it shares its Internet connection with all devices on the local network, or else connect a router.
    If there are other devices on the same network, and none of them can get an address, then the problem is on the DHCP server (most likely, the router.) If other devices are working normally, or if there are no others, see below.
    Open the Network pane in System Preferences and make a note of your settings in the Ethernet service. It may be helpful to take screenshots of the various tabs in the preference pane.
    If the preference pane is locked, unlock it by clicking the padlock icon and entering your administrator password.
    From the Location menu at the top of the window, select Edit Locations. A sheet will drop down. Click the plus-sign button to create a new location. Give it any name you want. In the new location, set up the Ethernet service with the same settings you used before. Click Apply and test.

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

  • My ipad recognizes my home network but will not connect to the internet. When I click on AirPort/preferences at the top of the imac screen it says..."AirPort has a self-assigned ip address and may not connect to the internet".How can I change ip address?

    My ipad recognizes my home network but will not connect to the internet. When I click on AirPort/preferences at the top of the imac screen it says..."AirPort has a self-assigned ip address and may not connect to the internet". If this is the root of the problem,how can I change ip address?
    Ipad will connect no problem to other networks.

    First thing you need I think is to get your iMac connected to the Internet.
    Shut down your iMac and you iPad. Then power off your router. Wait 30 seconds and power up the router.
    After the router indicates that it is connected to the Internet then start up your iMac and see if it connects. If the iMac connects to the Internet then your iPad should too.
    If this power up sequence doesn't work you'll have to dig into the router setup to make sure it is working properly.

  • Self-assigned IP address which is not able to connect to the internet.

    Okay, so my whole issue started around six or more months ago. I have a white MacBook which I have never particularly had any connectivity problems with, at least that where caused by my laptop. I constantly am on the internet at home and have never had issues with wireless connection here. I am a full time student which means I am also constantly on campus with my laptop and needing access to the internet. Even so, there I have never had any issues with connectivity.
    My issue is when I go to another university campus I am unable to connect to the internet. My airport finds the network I want and connects to it but usually within a few seconds the radial bars go a light gray and have an exclamation point through them . When looking under the Airport drop down list it simply says, "Airport has a self-assigned IP address and may not be able to connect to the internet." This particular IP that is not allowing me to access the internet starts off with 169.**.*.**. I would provide the entire IP but as I am not on that campus at the moment, I can't and don't remember it fully.
    I have tried SO many different things in order to find a solution but have come up empty handed every time. I've tried turning off my firewall and all of the steps that resolution includes and have also tried to resolve the issue through the creation of a new location, new network, and the use of network assistant on Airport.
    I know it is not an issue of the universities wireless network because I can easily connect to the internet through my Ipod Touch without a password simply by finding the network, connecting, stating I'm a guest, and then agreeing to the terms of use. Same goes for my local campus wireless network on both my Ipod Touch and MacBook.
    I am in extreme need of a resolution and would GREATLY appreciate any kind of feedback anyone can give me. If there is any other information you may need to help me out a little more accurately just let me know, I'll be happy to give you whatever I can so that I may figure this annoyance out!

    By the way, totally didn't mean to categorize this under Airport for Windows. This is my first post and OBVIOUSLY a figured out a way to mess it up. My bad. :S
    But again I'd appreciate any help! :]

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

Maybe you are looking for

  • Login to a website through java

    Hello there. I have been tinkering with an idea to make life easier for me in the long run whice should result in a java program which can sorte data from a website to make it easily accesable (then it is now) Now my problem is that i have no idea ho

  • Has Firefox stopped being able to handle hundreds of open tabs?

    For many, many years and FF versions, I have preferred having hundreds of tabs open to trying to manage bookmarks. I currently have about 650 open. For many, many years and FF versions, this worked fine. When I started using FF 25, it started crashin

  • Inquiry Number,Inquiry Date,Quotation No,Quotation Date,Sales order No

    Hi ALL, Please let me know from which SD cubes can we get data relation to these fields Inquiry Number,Inquiry Date,Quotation No,Quotation Date,Sales order No,Sales order Number,. Or do we need to enhance these field . Regards

  • Negative IR booked against GR twice

    Hello, During the MIRO process xxxx  has selected receipt lines that have already been vouched and processed another invoice against them.  We now have negative IR''s which the system booked against our GR account twice. This is creating an incorrect

  • BIP Word Template and Apache FOP

    Hello: Can I create a report format using the BIP Word template .. export it as XSL-FO file and use it with the open source Apache-FOP from APEX? Is there some technical constraints or licensing issues with doing this ? Yesh