Resolved iBook G4 can't connect to network.

Discussion in 'PowerPC Macs' started by nickn, May 28, 2012.

  1. nickn, May 28, 2012
    Last edited: May 28, 2012

    nickn macrumors 6502

    Joined:
    Jun 17, 2011
    #1
    My iBook G4 can't seem to get a valid ip address from my router. Both the stock airport extreme card and built in wired Ethernet nic only manage to get a generic 169 range self assigned ip, which doesn't work. All of the other wireless and wired clients on the network don't have any DHCP issues though, meaning the iBook is at fault. I requested a DHCP refresh in the system settings, restarted the router, and reseated/cleaned the airport card, but nothing changed. I also manually filled out the TCP/IP settings pan, but despite the system preferences changing to say that the network is fine, it is not. I still have no connectivity. I should also add the iBook has worked fine with the router, a Netgear WNDR3300, for about a year now, so I don't think there any compatibility problems. Any ideas what the issue could be here, or how I could fix this?
     
  2. eyoungren, May 28, 2012
    Last edited: Jun 2, 2012

    eyoungren macrumors P6

    eyoungren

    Joined:
    Aug 31, 2011
    Location:
    ten-zero-eleven-zero-zero by zero-two
    #2
    Are you on Leopard?

    If so, try this. Turn off Airport. Go to System Preferences>Security and click on your Firewall tab. Click on the radio button for Allow all incoming connections. Turn Airport back on and then check in Network that you have a valid IP. Then you can change the Firewall settings back if you want.

    This is a little bug in Leopard I ran into a year ago. There is another route which involves deleting Airport and Network preferences, but it doesn't stick for long and it requires a series of steps and a couple of restarts. It's easier just to turn the Firewall off.
     
  3. nickn thread starter macrumors 6502

    Joined:
    Jun 17, 2011
    #3
    Thanks for the info!!!!! You were correct. After turning off the firewall, both of the interfaces are running fine now. I guess the bug will never get fixed, as I am indeed on leopard.
     
  4. eyoungren, May 28, 2012
    Last edited: Jun 2, 2012

    eyoungren macrumors P6

    eyoungren

    Joined:
    Aug 31, 2011
    Location:
    ten-zero-eleven-zero-zero by zero-two
    #4
    Cool, glad it's working.

    My wife had this happen to her with her PB one night last year. I spent an hour or so looking for the solution. Found it on some blog somewhere (I think I have a bookmark) from a guy that had the problem too (with his girlfriend's Mac).

    Of course, once I fixed my wife's Mac by just turning the firewall off it showed up on both of MY PowerBooks! At least I knew what was going on that time though.

    Surprisingly enough, this little bug does not seem to be very well known over at the Apple forums.
     
  5. charudut macrumors newbie

    Joined:
    Jun 28, 2014
    #5
    Thanks a lot man!

    Your solution worked like butter! I tired all the replies in Apple communities, but no luck. This was exactly the solution to my problem.
     
  6. eyoungren macrumors P6

    eyoungren

    Joined:
    Aug 31, 2011
    Location:
    ten-zero-eleven-zero-zero by zero-two
    #6
    You're welcome!

    Glad this info is still useful!
     
  7. charudut macrumors newbie

    Joined:
    Jun 28, 2014
    #7
    Oh yes, it is! Got my first Mac, which happens to be an iBook G4 :) so, yeah I did run into this usual issue and your reply helped me.
     
  8. moongypsy524 macrumors newbie

    moongypsy524

    Joined:
    Oct 11, 2016
    Location:
    Wilmington,NC
    #8
    Thank you so much for this....i had the same problem witrh my other ibook and this fixed it,ive been messing with it trying to figure this out for days!!!THanks!!!
     
  9. sawpits macrumors member

    Joined:
    Feb 28, 2014
    #9

    Happened to me as well last year, after having the firewall turned on for a few years. So why? Who knows. And when I turn the firewall back on, sure enough, a few days later, it happens again.
     

Share This Page