Mavericks upgrade wifi problem exclamation mark

Either through the wifi icon in the bar at the top of the screen (click then "Turn Wi-fi Off), or through the System Preferences panel - Network, click on W-Fi in the left of the pane, then "Turn W-Fi Off" on the right side of the pane, at the top.

All,

My 'static ip' fix didn't seem to last long, and wasn't an ideal option anyway as i use my Mac at home and on the guest wireless at work which needed DHCP.

One thing that is crossing my mind is the switching between different networks. I get a little stability at home, go to work, come home and the stability goes down hill.

On a machine with no ethernet port this is simply unacceptable.

Andy

i have a mac mini late 2012 and after upgrade to mavericks from time to time i have the exclamation mark on my wi fi icon! i have also a pc and other devices on wifi that work perfectly..only my mini has this issue!i have to disable wifi re enable and it gives me wrong password(but it's correct)..after 3 times it works....it happens sometimes not everytime...but before with Mountain Lion mini works perfectly like other devices i have!...

This seems to have worked for me as well. Will update if problem recurs. Thanks for posting your solution!

So here's the confounding part. I got a 2004 iMac G5 (10.5.8) from a friend that did not have a WiFi card. I wanted to set it up so Grandma could Google. I took the AirPort Extreme card out of my 2003 G4 DP Tower (10.5.8) and put it in the iMac. Immediately it worked perfectly. Now the good part. The iMac is about 100' West of the wireless router that is on the East side of a brick and concrete chimney core (30' x 20') that runs up the middle of the house. So between the two there is this large wide concrete structure. The iMac is connecting at 802.11g with 5 bars, 54MBps and hasn't dropped a lick. My MBP (10.6.8-10.9) that is 0-30' away from the router in the line of sight, no obstructions, can't connect to save my life.

I find this typically Apple Humorous.

Hi guys, I'm sharing what worked for me:

1) Remove the folder /library/preferences/system configuration

2) Clean the Trash

3) Restart

I tried everything and nothing worked on the MBP retina one. I know several of you are perhaps as frustrated as me at this issue. I want to share my experience hoping it will help someone else.

I finally took a step back and looked and i saw there is no DHCP response. If you all read for many people this works by using the static IP.

So i tried something based on the older Lion hack to add new firewall rule.

To do that you will need to know how to use a editior like vi.

I did the following

1. sudo vi /usr/local/etc/ipfw.conf

2. add the following (only the bolded part) add 00050 allow udp from any to any src-port 67 dst-port 68 in

3. Save the file, and reboot the MB.

For me i tested with two access points i was having trouble with and it wokred just fine. I able to put it in sleep and resume and works too.

I will update again after testing for next week or so.

Hope this helps someone.

Thank you.

Hi all,

I was hitting a brick wall on this for days and it was very frustrating .

What resolved it for me was Linc Davis' post on this thread .....https://discussions.apple.com/thread/5506422?tstart=30

The step that actually fixed my problem was clearing out all the wifi entries in the keychain - though not all of the entries were in the Login section.

Hope this helps some of you - I know how frustrating this is.

SMC reset (Shift + Control + Option + Power) fix the problem...

MB Pro 17-inch, Late 2011

Solved...at least for me, finally....

Like so many others, I have tried every single workaround mentioned here, and in other posts. It's clearly an OS related issue. Something is preventing the DHCP response from getting back to the kernel and then bound to the adapter. I have found a new and excellent utility, however, in IPNetMonitorX...very capable. It allows you to troubleshoot DHCP from a given interface (en1 for the wireless in my case). Unlike an OS DHCP request, this tool simply creates the request and looks for the response...it doesn't actually try to bind it to the interface. What you can see with the utility, however, is that the request goes out, and the DHCP server responds as expected, including the expected IP address assignment. In my case, it's the DHCP assignment that doesn't happen, and that's ONLY on the en1 (wifi) interface. Ethernet works just fine. Also, assigning a manual IP address/gateway/netmask also works just fine, which confirms that it's not a hardware issue.

Again, I've tried absolutely everything to resolve this, with no luck. Including a clean install of Mavericks. After a CLEAN install of Mavericks, wireless/DHCP works as expected...encouraging. I then restored my user data from Time Machine (excluding the System/Network settings explicitly) and the problem shows up again. That means its specific to a particular application I have installd I expect.

As a workaround, I decided to leverage a small USB Wireless adapter I had laying around. In my case, it was a Tenda Nano USB adapter.

http://www.tenda.cn/tendacn/product/show.aspx?productid=375

It was not recognized by the Mac, so I pulled down the dirvers from their website:

http://www.tenda.cn/tendacn/DownLoads/show.aspx?downid=916

Under that installer, I went to Macintosh->WS541U W311M..

There was a version 3.0 as well as 4.1.5 driver. It's dated back to 2011_07_18 and references very old versions of Mac OS X....but it was the most recent I could find.

I ran the installer, which required admin as well as a reboot.

As soon as my Mac booted...I was very suprised to see that my INTERNAL wifi immediately connected properly and received a DHCP address.

Doesn't make much sense, as the Tenda uses a generic ralink chipset, which I believe is different than the airport's chipset, but apparently something in the installer made a difference.

It's been a couple of days....multiple reboots, sleeps, network switching and everything is working like it should!

For anyone in my situation, it certainly can't hurt!

Good luck!!

Oh...forgot to clarify. Above instructions get you to a .dmg. From there, you'll see that the dmg has a 10.4, 10.5 and 10.6 folder. I used the latest one, 10.6, which was intended for SnowLeopard.

@all_apple_all_the_time

I am glad you got it working. I agree with one important observation of yours that this is related to DHCP. I believe if you added one line to your ipfw.conf it would be working for you too.

My FW is not active, but based on that section of this thread, I did add that line to the ipfw.conf. Didn't make a difference, and that was with the FW on and off both, with resets in between.

Definitely strange behavior...I'm just glad my wireless is back to normal for 2+ days so far... It was definitey behaving like a firewall was preventing those critical packets from getting back to the kernel however.

Regards,

Andrew

gecko64

Thanks for this link. The built in firewall was blocking DHCP? Go figure!

See if this works: https://discussions.apple.com/thread/5478413?answerId=23504943022#23504943022&ac_cid=op123456#23504943

I had the same problem (wifi not connecting with bluetooth on after sleep) I created new partion HD2 downloaded Mavericks, now working as it should, HD1 still has the same issue.