Wireless not getting an IP (via DHCP) from router

Question

Level 1

0 points

Wireless not getting an IP (via DHCP) from router

I just purchased my new MacBook Pro two days ago and the wireless is acting really strange. In order to get an IP I have to follow the following process:

- Boot
- Computer connects to wifi, doesn't get IP
- Turn off wireless
- Turn on wireless
- Select access point
- Wait 10 seconds
- Computer gets IP and works

10.4.6, updated BIOS. Any ideas? I have a powerbook and two desktops that work everytime..

Thanks!

MacBook Pro, Mac OS X (10.4.6)

Posted on Apr 7, 2006 2:00 PM

Reply

Answer 1

nbl50

Level 1

0 points

Apr 7, 2006 2:09 PM in response to elementk

i'm having the exact same problem. any help would be great.

mac book pro Mac OS X (10.4.6)

Reply

Answer 2

Quux.nl

Level 1

5 points

Apr 7, 2006 2:14 PM in response to nbl50

Ever since I upgraded the firmware the wireless network does no longer connect to my WPA personal protected wireless network. So right now I can't even get the link to work. DHCP is even a big step further...

I guess Apple just made a BIG mess of the firmware upgrade for 2.16GHz MBP users...

Reply

Answer 3

elementk Author

Level 1

0 points

Apr 7, 2006 5:10 PM in response to Quux.nl

Yea, mine is the 2.16 as well.

Reply

Answer 4

elementk Author

Level 1

0 points

Apr 7, 2006 5:17 PM in response to elementk

Speaking of which (side-topic) I can't get Boot Camp to work w/the 2.16 either..

Reply

Answer 5

Ron A. W

Level 2

161 points

Apr 7, 2006 5:26 PM in response to elementk

i to have the same problem using 2.0 - the only way i can get a connection is to go thru the diagnostics steps - called apple support and now they have me doing a re-install - will get back in a few to let u know how that worked out...

Reply

Answer 6

Ron A. W

Level 2

161 points

Apr 7, 2006 5:57 PM in response to Ron A. W

ok - i had to do a re-install - just dont check that erase and install u will keep all of your stuff ....

Reply

Answer 7

Apr 7, 2006 6:36 PM in response to elementk

Same problem here, and this worked for me: I used the "Cleaning" section of Onyx ( http://www.titanium.free.fr/pgs/english.html). Since I checked off everything under that tab, I'm uncertain which one did the trick.

Good luck!

Reply

Answer 8

Apr 8, 2006 9:19 AM in response to NeuronNerd

same problem here, onyx did NOT work for me, and I checked everything . I have the 2.16 too. first real pblm with the machine ...

its a week 11, no discernable whine, runs quiet and quick.

i guess I'll doa reinstall?

Reply

Answer 9

elementk Author

Level 1

0 points

Apr 8, 2006 3:50 PM in response to Burton Bollinger

OnyX didn't work for me... I hate to do a reinstall.. please let me know if a reinstall works for anyone else. thx!

Reply

Answer 10

elementk Author

Level 1

0 points

Apr 8, 2006 5:12 PM in response to elementk

OK - I FIXED IT - THIS WILL WORK FOR YOU!

Ok, If you are having the original problem I posted, I know what the issue is and how to fix it.

So I reinstalled OS X.4.5 and it fixed the problem BUT I then applied the patch to X.4.6 and the problem came right back.. So, what is the deal, I'll tell you. For some reason, after installing X.4.6 OSX corrupts your saved WPA/WEP password in a cache. So when you initially connect it doesn't work, but after you turn it off, then on again, it fetches the uncorrupt password from the keychain and it works. Want proof? Ok, do this:

- Go to System Preferences
- Click Network
- Highlight AirPort and click Configure
- Choose "By default, join: Preferred networks"
- Select your access point and click edit
- Click on "show password"

At this point you should see a crazy corrupt password.. Proof that it is jacked up. Now:

- Exit that window back to the access point list
- Remove your access point with the "-" button
- Launch your keychain and delete your access point keychain entry.
- Reboot
- Go back to the "By default, join:" page and click the "+" this time to add your access point. Enter the correct password, save, reboot, BAM, FIXED!

Enjoy and visit digg.com often 🙂

Reply

Answer 11

Apr 9, 2006 9:47 PM in response to elementk

This Fixed my problem.

Thank you very much for posting.

I would like to make one change to your instructions though, after line:

"Launch your keychain and delete your access point keychain entry."

(Note: I had 2 instances of my wireless network name. I deleted both.)

New Line: Before rebooting... turn OFF airport.

The reason why I say turn off Airport is that I did not the first time and somewhere and despite me deleting all the instances of my wireless network, OS X still found it and logged into it.

Turning off airport will avoid OS X auto logging in with a cached password/network

My wireless has survied two restarts and its still working...

Reply

Answer 12

ShellyB

Level 1

0 points

Apr 10, 2006 9:05 AM in response to elementk

Just wanted to chime in and say thanks for posting this fix. My new MBP was refusing to connect to my wireless network on reboot, but after going through the steps in your fix it works fine.

Reply

Answer 13

Apr 11, 2006 7:39 AM in response to elementk

Have to say, this didn't work for me.

Worked on it for 2 hours yesterday, changing router settings and passwords and only briefly got an IP connection. I am going to try a different router (since the one at home still works fine) but after that I might need a re-install I guess.

Reply

Answer 14

Apr 11, 2006 8:06 AM in response to Dartagnan

Make sure Airport is off before restarting.

Restart a couple of times and check each time to make sure "yourwireless" does not appear in your keychain.

Reply

Answer 15

Apr 11, 2006 12:16 PM in response to Louis Rodriguez1

I'm pretty sure I did that in the many iterations of connections. I certainly deleted the wireless network keychain entry.
The thing is, my home network works fine. It's only my office network that messed up after the firmware update (but before the 10.4.6 update). It sees the router but just can't communicate with it. I can't PING it either.

I'm going to bring in a different router and see if that works. Otherwise I'm at a loss as to how this seems to be the only wireless network I can't connect to.

Reply