Q: Mountain Lion no Wifi after wake from sleep

Removing the Transmit icon solved my issue on a 2010 Macbook pro and a 2008 Macbook

Verizon Fios Actiontec router users only!

This is something that has been working for me since early Saturday.

I've passed it onto Apple.  I know most of us has tried deleting our network setups with no luck.

Well this is what i did:

1: Deleted all networks and setting on my Mac again.

2: This time after that I did a Hard Reset of my router.

3: Rebooted my Mac

4: I then let our 2 Macs and Router set them selves up Automatically.

5: I left all settings to the default  settings including Network name

6: Later I set my energy settings to deep sleep every 5 minutes.

This morning I decided to update my Onkyo receiver.  I disconnected my router and moved it over to the receiver it needed to be hard wire connected to the receiver.  The net worked fine there and when I put it back in the other room and connected to my PC every thing was still working wirelessly on our Macs.

I intentionally waited 2 days before I posted this and 36hrs before I passed it onto Apple.

I really don't know if this is just a fluke or if it works on other routers.

If you try it let me know your results.  I'll pass it onto Apple.

An update: from what we've found so far, this is an Apple bug, possibly involving Bonjour networking.

Transmit, and Transmit Menu, both try to access Bonjour networking during setup, which would explain how they can easily trigger this bug. But any app that access Bonjour could possibly trigger this.

For now, it looks like only Apple can fix this bug, hopefully in 10.8.1...

We've filed a Radar with Apple, and we'll keep you guys posted if we/when hear anything!

Best,

Cabel

Hi Gary,
Had been having exactly the issues you detailed, scanned this thread and when I came to your post decided to give it a go (as it was a very easy thing to try!).

Lo and behold the problem has gone - have only tried a few times but it would crash every time before I removed the Transmit icon from the menu bar.

So, I say thank you very much! Just hope that this is the end of it. I see you posted this 3 days ago - has the problem returned?

Hi Phil,

Happy to help, & the problem has not returned. Mountain Lion is quite fast without that crash bug!

I did get an email from Panic a few hours ago:

"Hi Gary, this appears to be an OS-level bug. Apparently other apps that access Rendezvous networking have the same problem. We’re trying to figure out if there’s a workaround."

Haven't run into any other instances of the issue.

Unfortunately I don't believe it's Transmit Menubar item. I removed it and I just had my MBP freeze again. Transmit itself was open though.

Dear Apple, if I wanted a constantly frozen computer, I would rather have paid a third of the price of a Mac and gone with Windows.

This is getting RIDICULOUS.

Are all of you referring to the Transmit FTP app?

Yep.  Seems to be the culprit for many of us... but as you can see, it's still being investigated.

Cheetaux wrote:

 

Are all of you referring to the Transmit FTP app?

Cheetaux: yes that seems to be one of the apps that are causing issues.  Cabel from Panic (makers of Transmit) has mentioned that this is actually a Bonjour bug, which Transmit uses. But the fix then needs to come from Apple.

Apple contact me this evening to try and get some info on this. Spoke to a nice guy for a while who asked a bunch of questions. I had to get off the call early so I'll pick up with him tomorrow to get him more data. So they are aware and actively trying to resolve it.

You would never see MS do that.

I'd be happy to provide info to Apple; I was actually the one who managed to get a log trace for Cabel at Panic (so, that's why we know it's a Bonjour issue).... Wonder how they got your phone number? This acct is linked to my developer account at Apple, so, one would imagine they could dig up my phone #, but...

Same here. I guess thats how they found me. Not sure how they choose who to contact. He said he was going to email me his contact info but I never got that from him. Hopefully he follows up tomorrow.

That's good to hear!

It seems that there are other apps causing this conflict but in our case it was Transmit.

I guess the other folks out there having the same problem still should systematically go through as you did to find the problem.

It's intersting that the problem occurs and everyone slates Apple, I guess it's the obvious thiing to do, but it surprises me that the develeopers out there don't find these bugs before new OS are released - seems like quite a major one!

well, obviously it is a problem of Apple and Mountain Lion, since I have problems also in clean install of ML! and so far I tried every possible online "solution" I've found, but to no avail.

just to list something what I've tried so far :

1. Clean install of ML.

2. Reinstaling ML.

3. Kext from snow leopard, or lion (two version actually - 4.1.x and 4.2.x).

4. Open DNS, Google DNS - obviously, DNS aren't the problem, since after wifi drop I'm unable to ping the router IP either, eventhough wifi is says connected.

5. Tried looking into console logs and wifi analyser, but to no avail...

6. Removing wifi connection and creating new one.

7. Changing MTU, Changing IPv6 settings.

8. SMC and PRAM reset.

9. Removing key chain settings and renewing the WiFi connection settings.

10. Changing router settings to automatic WPA/WPA2, tried 1, 6, 12(13) WiFi channel for interference issues.

I repeat, the problems are present from the very beginning, even on the clean install of ML. So do not bother to try "fixes" listed above. They just don't work...It's been nearly two weeks, and I'm forced to use the cable!

Cheers!