Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
wifi problems with lion
- Thread starter Xgamer1224
- Start date
- Sort by reaction score
Wirelessly posted (Mozilla/5.0 (iPhone; U; CPU iPhone OS 4_3_4 like Mac OS X; en-us) AppleWebKit/533.17.9 (KHTML, like Gecko) Version/5.0.2 Mobile/8K2 Safari/6533.18.5)
Anyone found a fix?
Anyone found a fix?
Try booting into safe mode and deleting your airport from the network preferences. Reboot the machine back into normal mode and add the connection back in.
I have had this problem for a long time. When Apple released 10.6.5, It completely killed my wireless and I have had to strip the driver from 10.6.4 every time there was an update and add it to the update, as the driver from 10.6.4 was the only thing that would work.
Wirelessly posted (Mozilla/5.0 (iPhone; U; CPU iPhone OS 4_3_4 like Mac OS X; en-us) AppleWebKit/533.17.9 (KHTML, like Gecko) Version/5.0.2 Mobile/8K2 Safari/6533.18.5)
Tried all that to no avail. Still nothing just 'connection timeout'
Tried all that to no avail. Still nothing just 'connection timeout'
Been having the same issues on both my 2010 iMac, 2008 Macbook Pro and 2009 Macbook -- all since installing Lion. No avast installed.
I did what another user on another thread suggested as a possible fix and it solved my wifi probems.
Before I did it, my wifi just didn't connect. Most of the time my MBA didn't see the Wifi network. When it did see it, it refused to connect. Or it worked till I put the MBA to sleep, then didn't connect to the network at all.
I deleted plist files etc and none of that worked.
What you have to do is:
Disable automatic channel scan on your wifi router. The newer routers have a setting that automatically sets the best channel (between 1-11 usually) for you, depending on where it finds the least amount of traffic.
Disable that and manually set a channel.
Reboot router.
Tada!
Wifi is now solid on my MBA with no ill effects.
Before I did it, my wifi just didn't connect. Most of the time my MBA didn't see the Wifi network. When it did see it, it refused to connect. Or it worked till I put the MBA to sleep, then didn't connect to the network at all.
I deleted plist files etc and none of that worked.
What you have to do is:
Disable automatic channel scan on your wifi router. The newer routers have a setting that automatically sets the best channel (between 1-11 usually) for you, depending on where it finds the least amount of traffic.
Disable that and manually set a channel.
Reboot router.
Tada!
Wifi is now solid on my MBA with no ill effects.
Wirelessly posted (Mozilla/5.0 (iPhone; U; CPU iPhone OS 4_3_4 like Mac OS X; en-us) AppleWebKit/533.17.9 (KHTML, like Gecko) Version/5.0.2 Mobile/8K2 Safari/6533.18.5)
You shouldn't have to do that surely!!! And what about access to public open wifi?
Fkn Lion
You shouldn't have to do that surely!!! And what about access to public open wifi?
Fkn Lion
I made these changes, and thought it had fixed my issue with awaking from sleep, but unfortunately, it is back.
Last edited:
I put this changes and still when my comp goes to sleep and i wake it up is off,then after few seconds it connects by itself,I can't connect my comp now with remote apps because of this,is very annoying and I regret my update,I should haven't jumped to this Lion crap so fast
I was surprised to see this thread, because I've gone through the exact experience yesterday and today. Since the internet was so slow, I decided to reset my modem, but afterwards I couldn't connect at all. My Airport light was green and my computer said WIFI was on. I tried all the steps mentioned in the previous messages, but finally called Comcast and after speaking with 3 different people, a knowledgeable person "provisioned" my line. He said that no matter what I did, I would not have been able to connect until they entered the data at their "end". I don't know how it got messed up, but I can't help but think that the recent Lion installation had something to do with it.
Quote:
DNS has nothing to do with how a wifi will connect to a router.
It's also funny that this thread is just a bunch of people saying the same thing with no real answer to fix the problem. But I'm guessing a 10.7.1 update will be out soon to install and fix this problem.
DNS has nothing to do with how a wifi will connect to a router.
It's also funny that this thread is just a bunch of people saying the same thing with no real answer to fix the problem. But I'm guessing a 10.7.1 update will be out soon to install and fix this problem.
I had this issue in one of the Betas. And also had the issue with the official release version.
I had tried turning the wireless router off and on again, And also cut power to both the modem and the wireless router. But it didn't work.
So I called Apple Support. After they asked me if I had tried turning the router off and on again, I said yes, I have tried that. They still said they would walk me through the process and everything worked fine for me this time.
Here is what they had me do.
Turn off my computer then the wireless router then the cable modem in this particular order.
And then asked me to turn these devices on in the reverse order, cable modem, wireless router and the computer.
this time it worked. I was baffled. But I was happy everything was working again.
I had tried turning the wireless router off and on again, And also cut power to both the modem and the wireless router. But it didn't work.
So I called Apple Support. After they asked me if I had tried turning the router off and on again, I said yes, I have tried that. They still said they would walk me through the process and everything worked fine for me this time.
Here is what they had me do.
Turn off my computer then the wireless router then the cable modem in this particular order.
And then asked me to turn these devices on in the reverse order, cable modem, wireless router and the computer.
this time it worked. I was baffled. But I was happy everything was working again.
hmm
while this may have worked, it doesn't really make sense. If that were the case, a "forget this network" in network settings should have as well.
while this may have worked, it doesn't really make sense. If that were the case, a "forget this network" in network settings should have as well.
WIFI does not connect automatically
My wifi does not connect automatically and has to search for wifi...worked fine with snow leopard and works fine with iPad and works fine with my wife's older iMac...just having issues with the newer iMac...called Apple and they could not resolve the issue
, any suggestions.
My wifi does not connect automatically and has to search for wifi...worked fine with snow leopard and works fine with iPad and works fine with my wife's older iMac...just having issues with the newer iMac...called Apple and they could not resolve the issue
, any suggestions.
mine will connect to my att u verse router fine but under the airport extreme it won't. on the internet and server light under system preferences>network>assist me>diagnostics both are yellow and turn to red after a few seconds. i tried resetting the airport, changing the settings, turning wifi on and off , rebooting the computer, and nothing works. it worked fine yesterday but just got the problem this morning when i woke up.
EDIT: back now
EDIT: back now
Last edited:
I got my iMac last week and had the same issues with Snow Leopard.
It haoppened after I updated the SL that came with the Mac to 10.6.8. Nothing worked. What I did was in the Router settings, made sure that my security was WPA2-PSK and also the Encryption to AES only. I had it on WPS-PSK and then I changed the Channel to 1.
1 or 11 are the best. The others are bound to be shared by other networks in the area.
The AES setting was suggested on an Apple.com discussion forum.
My machine is now flying.....Hasn't dropped the connection in a week. I'm on a 25MB broadband and now its really acting like it!
I'm very reluctant now to upgrade to Lion. I have the redemption key to upgrade but my Mac is working so well, is so quick and responsive I may hold off.
It haoppened after I updated the SL that came with the Mac to 10.6.8. Nothing worked. What I did was in the Router settings, made sure that my security was WPA2-PSK and also the Encryption to AES only. I had it on WPS-PSK and then I changed the Channel to 1.
1 or 11 are the best. The others are bound to be shared by other networks in the area.
The AES setting was suggested on an Apple.com discussion forum.
My machine is now flying.....Hasn't dropped the connection in a week. I'm on a 25MB broadband and now its really acting like it!
I'm very reluctant now to upgrade to Lion. I have the redemption key to upgrade but my Mac is working so well, is so quick and responsive I may hold off.
My Mac Pro isn't dropping the connection, it just can't access the internet after the computer puts itself to sleep. It works just fine after waking from a sleep that I initiated, which doesn't make any sense to me. When it won't get on the net, it still shows that it is connected to my network, though. I'm going to do a clean install when I have time this weekend and see if that solves the problem. I'm having some other issues as well, so I'm hoping the clean install gets things working again. I never had any problems with this Mac Pro with SL.
NO issues on 10.6.8 or 10.7 with my Mid 10 2.4i5 MBP.
I run an airport extreme dual band (original, not brand new one) have my 5ghz band set for channel 44 and my 2.4ghz band set for channel 1.
Using WPA2 Personal
Hope this helps someone.
I run an airport extreme dual band (original, not brand new one) have my 5ghz band set for channel 44 and my 2.4ghz band set for channel 1.
Using WPA2 Personal
Hope this helps someone.
This is how the Apple support guy explained it to me: the routers cannot make sense of the computer in their network that was in their database(already had a IP address provided by DHCP) but has just been upgraded to a completely new operating system. While the operating system thinks great, I have the IP address from before and I am good to go.
So restarting the modem, and router and then booting the computer makes the routers see it as a new device and give it a new IP address and correctly route internet traffic to it.
I accept this explanation, but if this still doesn't make sense to you, maybe you should call Apple yourself or go to a genius bar.
hmm
hmm, but the MAC address on the MAC (not to confuse the two) hasn't changed at all, it remains the same. The router, IF it had address reservation setup (which most are not setup to do from the factory at all and most people don't enable) then the router would simply see A MAC ADDRESS and not care, simply delivering any new open next DHCP address. Even IF the router had A DCHP address reserved and associated with a previous MAC via MAC address lookup, the MAC ADDRESS on the MAC is going to report as the same. It sounds more like a lease timeout issue on the MAC OS that has been changed and will need to be updated in an OS revision. If THAT were the issue, then a reboot of the router WOULD work as the lease reservation would have timed out on the router, and would now be refreshed on the router.
hmm, but the MAC address on the MAC (not to confuse the two) hasn't changed at all, it remains the same. The router, IF it had address reservation setup (which most are not setup to do from the factory at all and most people don't enable) then the router would simply see A MAC ADDRESS and not care, simply delivering any new open next DHCP address. Even IF the router had A DCHP address reserved and associated with a previous MAC via MAC address lookup, the MAC ADDRESS on the MAC is going to report as the same. It sounds more like a lease timeout issue on the MAC OS that has been changed and will need to be updated in an OS revision. If THAT were the issue, then a reboot of the router WOULD work as the lease reservation would have timed out on the router, and would now be refreshed on the router.
At some point it DOES get confusing to me a little because you are writing Mac as MAC.
But I guess the lease timeout may be the issue. I have had to call them twice again today about the iMac loosing internet connectivity after using the internet for a while, even though the wifi is still connected. And this time, apart from the usual restart the router stuff, one rep also made me clear out my keychains.
But I guess the lease timeout may be the issue. I have had to call them twice again today about the iMac loosing internet connectivity after using the internet for a while, even though the wifi is still connected. And this time, apart from the usual restart the router stuff, one rep also made me clear out my keychains.
M.a.c.
Well, when I typed MAC I was referring to the M.A.C., media access control ID that all devices which connect to the internet have as a unit identifier, every network card, ethernet, wifi, etc., has a different M.A.C. ID. Mac, I meant well, the Macintosh computer that we were talking about.
Well, when I typed MAC I was referring to the M.A.C., media access control ID that all devices which connect to the internet have as a unit identifier, every network card, ethernet, wifi, etc., has a different M.A.C. ID. Mac, I meant well, the Macintosh computer that we were talking about.
Wirelessly posted (Mozilla/5.0 (iPhone; U; CPU iPhone OS 4_3_3 like Mac OS X; en-us) AppleWebKit/533.17.9 (KHTML, like Gecko) Version/5.0.2 Mobile/8J2 Safari/6533.18.5)
The same problem occurs for me when my MBP goes to sleep during a Time Capsule backup. Sometimes I have to restart the computer to get things running again, and I've noticed that fiddling with wi-fi settings when the problem is occurring can cause Lion to freeze.
The same problem occurs for me when my MBP goes to sleep during a Time Capsule backup. Sometimes I have to restart the computer to get things running again, and I've noticed that fiddling with wi-fi settings when the problem is occurring can cause Lion to freeze.
I had this problem since installing Lion. (late 2008 Unibody)
I fixed it today by making my SSID visible. I had hidden it some time ago and found an old Apple support thread regarding the same issue from a few years back.
Making the SSID broadcast again has fixed the problem for me.
I fixed it today by making my SSID visible. I had hidden it some time ago and found an old Apple support thread regarding the same issue from a few years back.
Making the SSID broadcast again has fixed the problem for me.