Q: Wifi Constantly Dropping in Lion

Thanks for the link, Allen.  Did that just now.  Maybe we can get a fix for this driver from Apple so more people can resolve this problem.

I have Lion Mac OS X 10.7.2 (11C73) (GM Relase Build) and I can tell you that on my MacBookPro3,1 the Wifi instability and disconnects are still present aswell as a problem with the NetBios Name not appearing on the network when the computer is connected through Wifi instead of ethernet. You should test this Netbios issue on your machines to see if the problem is specific to notebooks because on my setup which is a very apple specific setup I am using an apple timecapsule latest generation the netbios problem doesn't occure on a late 2009 imac. This problem of the netbios name not appearing has develped with the upgrade and release of lion... Snow Leopard did not have this problem and I tested that by downgrading to snow leopard. This netbios name problem creates havok for SMB shares since windows cant even find the machine. I was hoping that 10.7.2 would fix this it wont... I am letting you know that you are going to be dissapointed if you think this release will fix wifi as well as SMB problems it doesn't... I am very upset with how long this is taking to fix it is clearly a bug numours posts and messages to apple I would really advice apple customers to complain in the feedback http://www.apple.com/feedback/macosx.html and bug reports http://developer.apple.com/bugreporter/.. Hope they fix this with an interm update however it most likely wont be fixed until 10.7.3 and maybe not even by then.

Stephen Antonacci wrote:
 
a problem with the NetBios Name not appearing on the network when the computer is connected through Wifi 

Thank's for your contribution about this issue!

Your findings matches with my own and also with some other reports in the forums here.

Since Apples Airdrop (zero conf networking) the OS is very sensitive about different local domain names in a network segment (aka your home network) as the use of Airdrop and the multicast based name resolution on Apples Bonjour Service is bound to the use of the domain >local<

Your findings match also to reports from UK based users with some new BT DSL/WiFi boxes with a preset local domain name "home" about sluggish Internet connection, DNS resolution problems and WiFi connection problems.

In that cases the working solution was to change the domain on the Mac's to "home" although the Airdrop function get lost with this.

It matches also to reports that bringing Windows systems from "workgroup" into "local" solved in cases with heterogeneous networks the wireless problems with Lion systems.

Certainly the rules for networks are clear about this.

See here -> http://en.wikipedia.org/wiki/Zero_configuration_networking

And in general here -> http://en.wikipedia.org/wiki/Domain_Name_System

Lupunus

I have tried everthing to get this computer to appear on the network it will not.. The only thing that made it appear back in windows was downgrading to Snow leopard.... What upsets me about this is now my laptop has to be chained down connected to Ethernet in order to perform In a Windows World.

Things I have Tried...

1. Restore Machine

2. Format and use default configuration not a restored one by setting up completley new user this method fixes the screwed up checkbox in the smb sharing user settings.

3. Change Default Netbios name make the name one word as well as deleting the system configuation folder.

4. Restoring the time capsule and resetting it up.

5. Connect to a wireless network without security.

Nothing has worked the only thing that worked is a downgrade to snow leopard this is a definite bug in lion.

Stephen Antonacci wrote:

 

I have tried everthing to get this computer to appear on the network it will not.. The only thing that made it appear back in windows was downgrading to Snow leopard.... What upsets me about this is now my laptop has to be chained down connected to Ethernet in order to perform In a Windows World.

As wrote in my answer to your last post ...

Have you set the domain equal in both Windows and Mac?

Windows has (depending on version) something like "workgroup" and Mac's have "local"

That was what I tried to tell you in the last post.

Lion is due to Airdrop function and Bonjour Service very sensitive about that.

As you may see on your own systems,

On a Mac the local host name is like "yourmac.local"

On Windows the local host name is like "yourwin.workgroup"

Change your settings to match; e.g. "yourmac.local" and "yourwin.local"

Apple:

Windows:

I have tried that but if you run an smb tool you will see that the machine does not appear so that means the mac is not sending the netbios name through the network. It does when connected through ethernet... This does not change even with changing the netbios names in windows and mac.

Stephen Antonacci wrote:

 

the mac is not sending the netbios name through the network.

Because the Apple did not use netbios. Netbios is a (outdated) Windows only technic.

http://en.wikipedia.org/wiki/NetBIOS

Apple use a Multicast (mDNS/DNS-SD) based local name resolution. Its similar to unicast Domain Name System but implemented over a multicast protocol.  Each computer on the LAN stores its own list of DNS resource records (e.g., A, MX, SRV) and joins the mDNS multicast group. Here: "local"

When an mDNS client wants to know the IP address of a PC given its name, mDNS client sends a request to a well-known multicast address; the PC with the corresponding A record replies with its IP address.

I think we have to dive a little deeper in that and think it over ...

Lupunus

So what is being said here now is Apple pulled a Microsoft move when they upgraded their operating system.  Upgrade the operating system and nothing works and has to be upgraded too.  That's the reason after 26 years of owning PC's I switched to Mac at 3 times the cost.  I've had My MacBook for a year, my wife 5 months.  Mine has been in for repairs 4 times since it was 8 months old.  Nothing major, new monitor, new hard drive, etc!

The Genius Bar at the apple store told me I better hurry up and get the extended warranty before it's to late?  LOL

Well i finally have a stable Wi-Fi connection. The issue was on the MacBook Early 2008. Downgrading to the 3.2 kext solved the issue for me.

Wow! Lupunus, you are the only person on this forum who has provided a solution that's worked for me, and I tried many, many of the solutions offered on this forum.   My wi-fi has worked perfectly for about a week since I implemented your solution.  You are a genuis, and a saint

(That said, I must say, Lupunus, that I do, at times, feel that you are needlessly harsh with people who are understandably frustrated with Apple and come here to vent their frustration.  Your solution did solve my problem, but that doesn't change the fact that the problem began precisely when I upgraded to Lion.  I would much prefer that Apple fix these problems quickly than me having to spend hours on this forum and tinker with esoteric settings, and so I commend people for voicing their frustration, in an effort to get Apple to improve their software [though it's not clear to me whether Apple employees actually read these forums].  So I appreciate your kindness in offering me a solution, and I would also appreciate you expressing a kinder attitude towards others on this forum.)

For those of you experiencing a slow re-connect to wi-fi from sleep, you might try implementing Lupunus's solution (reprinted below), especially if you own a Time Machine (or another type of Airport router) like me.

Thanks again, Lupunus, for your help!

lupunus wrote:

 

moskovit wrote:

 

The problem I was experiencing is my MacBook Pro taking awhile to connect to wi-fi upon waking from sleep.  The problem started after I upgraded to Lion.  Resetting the time capsule to factory settings (via Airport Utility->Base Station drop-down menu->Restore Default Settings) solved this problem for a couple of days, but then the problem came back.

Looks like the "2 BSSID" problem. See other posts here.

 

• On TimeCapsule set a dedicated name (SSID) for the 5GHz wireless.

• If no iPone or iPod nano is connected to the TC, eventually set: 802.11n only (5GHz) - 802.11n only (2.4GHz).
• If iPhone or older wireless system should get connected use: 802.11n only (5GHz) - 802.11b/g. You will reach that settings with holding option key (alt) while clicking on the dropdown menu.
• Force the Mac to use the 5GHz SSID
• Delete the other SSID's of your home wireless from the list of "known networks"
• Eventually delete the keys pointing to them from keychain access
• Uncheck "Ask to join new networks"
• Reboot
• Rejoin your wireless.

 

moskovit wrote:

1. Please don't post a solution unless you've tested it for at least a couple of days.  Otherwise, you may be giving false hope and inspiring people to waste time trying things that don't actually work. 

 

2. Please specify how many days you have been problem-free since implementing a solution.

Tested on own wireless with Airport Extreme (same as TC but no hard disk) on 7.5.2, 2011 MBPro on 10.6.8, 2008 MacBook 10.6.8, WindowsXPPro SP3, 4 AP-Express (7.5.2), 2010 MBook (customer) on 10.7.1.

 

Extreme up without problems now for 48D 1h 43m, MBPro uptime 23D 14h 23m, WinXP ocasionally online, Expresses uptime same as Router, Uptime customers MBook 11 days.

 

Lupunus

moskovit wrote:

 

You are a genuis, and a saint

I'm neither a genius nor a saint.

moskovit wrote:

 

Wow! Lupunus, you are the only person on this forum who has provided a solution that's worked for me, and I tried many, many of the solutions offered on this forum.

I gave that hint to you cause you provided useful information about what you've tried, your setup and the results.

Only on this base it was possible to suggest a tested solution as this solution even worked for me and also for many others with a AP-Extreme here in the community.

moskovit wrote:

 

I must say, Lupunus, that I do, at times, feel that you are needlessly harsh with people who are understandably frustrated with Apple and come here to vent their frustration.

Yes, sometimes I'm harsh on this. And I stay with it.

I did not have the time, the money or any interest to talk in a social worker's way about clean technical and engineering problems.

Nevertheless, I have a great sympathy for the fact that one is frustrated and want to tell that others.

But, I have no understanding for those staying only with their frustration and refuse to go only one single step to solve the reason for that frustration in a clear and technical way.

Poking with a stick in the fog and try this and that randomly did not solve any problem.

To everyone it is pretty clear that if a car broke down the mechanic on the shop perform a clear troubleshoot and did not randomly swap parts or try this and that hoping to get a hit.

Also everyone, if ill, expect a clear diagnosis (troubleshoot) and a matching cure from the doctor and also the doctor expect a bit more information aside from "I feel ill".

So why they refuse to the same on their networking problems?

Yes, wireless is a complicated technic and may lead sometimes to frustration regardless of Apple, Windows or Linux. The problems are anyway the same. Just take a look over the rim of your plate and you may notice that.

No, Apple are not able to do wonder or to bring real plug and play in wireless at now.

I saw such discussions at any time a new version of any operating system is released from Microsoft OR Apple during the last 18 years.

But except a hardware fault or a real firmware bug, it's a provable truth that the solution -as well as the problem- is always IN the network or a PEBCAK.

As a matter of fact it's also clear, that in 99.9% of the reported problems neither Lion nor Apple or Windows is responsible for the problem.

For that most of the wireless problems one may have are not "since Lion or since my new MacBook".

They where latent in the network before but did not show up in a remarkable amount or matter.

If one integrate a correct configured Mac in a correct designed and configured wireless network, the system will run seamlessly in that environment.

if this where not fact, the several millions of Lion users had ALL experienced a wireless disaster.

Personally I run Lion only on a virtual machine. But a few weeks ago, I had to setup a Lion for a customer on his MacBook. After installing the African animal the system integrates in my wireless immediately.

I kept that system running 24/7, performing several time triggerd benchmarks for nearly 2 weeks without one single drop out, wireless cut of or other WiFi problem.

Lupunus

Message was edited by: lupunus (typo's fixed)

Well, I'm really curious about this.  I have had this problem, i.e., WiFi connection dropping constantly, since installing Lion several months ago.  I know it's not the modem since there are two iPads, another older iMac and two iPhones using this DSL modem in addition to my iMac Quad Core i5, and the other hardware has no issue at all.  I came to the community seeking an answer and found nothing that would resolve the problem.   In frustration, I went to Apple Support since I'm still covered. After working with several techs, I was sent to the highest level tech (Jennifer) and we worked for several days on this. I've re-installed Lion (pain in the ...) and that didn't work.  Frankly, I can't remember all the stuff we've tried. As a last resort, with Jennifer's assistance, I sent several files using Apple's "capture data" programs.  These were sent at the "engineers' request".  It's been about four more weeks now, I still have the issue and the engineers have yet to respond.  While the tech is ever so nice, I'm starting to think about lawyers.  When it quits, I run Digital Assistant.  All the lights are green except for "internet" and "server". By the time I finish running through the DA steps  (or before) everything turns green again!

Hi all Im new here and must admit not read all these threads ( though a lot )

My problem was Wifi dropiing every 5 hours ( ish ) and everytime I went into standbye on my 2 week old Macbook air.

Just realised if I put my DNS IP.s into my mac instead of relying on the router Using open DNS - I havent had a drop in 11 hours.

Just thought it may help someone..

Sandpuppy wrote:

 

Well, I'm really curious about this.

What's your router (wireless access point) model?

Kwales66 wrote:

 

My problem was Wifi dropiing every 5 hours ( ish ) and everytime I went into standbye on my 2 week old Macbook air.

What's your router (wireless access point) model?

Which systems except the MBAir are in your wireless?