Currently Being ModeratedMar 3, 2011 7:39 PM (in response to Linda Custer)Ok, well today I updated to 4.3 of iOS. Same thing, but not as bad. Still not good though. I am not guessing they are going to update something on the AEBS soon, but how soon? That's the million dollar question. I would say at least 6 months. AEBS isn't known for frequent updates. Before the latest update in December. Before that, it was March. Before that? The previous year.17" MacBook Pro 2.4 GHz Santa Rosa, Mac OS X (10.6.6)
Currently Being ModeratedMar 3, 2011 7:48 PM (in response to sapphir8)Bummer.MBP (late 2008); MBA (11"/4/128); Mac mini (late 2009) running Win 7 w/BootCamp, Mac OS X (10.6.6), Displays: Dell 30", Apple 24" LED Cinema; iPhone 4/32; TV; TimeCapsule 2 TB
Currently Being ModeratedMar 7, 2011 12:01 AM (in response to bikiru)Hi All
Apple newbie wading in here, so watch out
Anyway I found something that may be of help narrowing things down further for everyone. Me and my wife have iphone 4's, since 2 days ago we have an airport extreme running 7.5.2 (upgraded from a linksys 160n horror). Other systems are Win7 (wired), Dell workstation laptop (with n), ps3 (g) and an old and half broken dell (g).
My PS3 has been having better connections than ever on g, so great but I found my work station and phones were experiencing poor performance, although all could connect (at close range). I thought that this was a channel interference thing. So I installed net stumbler on my workstation lappy and went for a wander through the house to see who was up to what in the neighborhood.
I found a boat load of networks on 1, 6 and 11 (so all g and no n). But the thing I only noticed after a few minutes was that the n from the AE had dropped away to nothing and the g was still going strong. This could be replicated with both iphones. So perhaps the problem is with n networking on the AE's..... I notice that there is no way to force g on the phones (that I could find anyway). My linksys had much greater range on n than g, as should be expected I thought.
Any comments, or have I just completely stuffed up the settings on this thing? PS I am running g on 3 and n on 44, radio mode automatic, running WPA2.
Currently Being ModeratedMar 7, 2011 1:23 AM (in response to Petja)"My linksys had much greater range on n than g, as should be expected I thought."
"n" inherently has a much lower range than "g" which has a lower range than "b" etc.... As the data rate increases, the range decreases. This is why RF devices usually derate their connection speed as it becomes more flaky to maintain signal quality.
Thanks for the dissertation, I don't think in my case range has anything to do with it. None of my 3 iPhones (2 iPhone 4, 1 iPhone 3) connect whether you stand next to the AEx, or wander off to the garage. Bluntly they're just useless. The pick up a DHCP address, then lose it within 10 milliseconds, and continue in this vein.
Anything else I own connects superbly, particularly when it's not made by Apple. PS3, Wii, Dell laptop..... you name it, it connects.... iPads a bit more reluctant, but OK and old AppleTV fine.
So in summary, if a device is a "connector" it doesn't matter how far it is away within reason, and if it's an iPhone, it doesn't matter either, it's always useless.
PauliMac 24", Mac OS X (10.6.6), The usual list
Currently Being ModeratedMar 7, 2011 1:25 AM (in response to Stag V8)I even site surveyed my home, using what we use at work..."AirMagnet"...
Everything is fine. I have maps, plans, charts, even a what happens if the AEx fails chart... it's all fine. All fine but the iPhones
PauliMac 24", Mac OS X (10.6.6), Anything
Currently Being ModeratedMar 9, 2011 9:00 PM (in response to Stag V8)I'm happy to say that I've updated my iPhone 4 to 4.3 and the problem has been solved.
For now.MBP (late 2008); MBA (11"/4/128); Mac mini (late 2009) running Win 7 w/BootCamp, Mac OS X (10.6.6), Displays: Dell 30", Apple 24" LED Cinema; iPhone 4/32; TV; TimeCapsule 2 TB
Currently Being ModeratedMar 10, 2011 2:02 AM (in response to Linda Custer)And I just did the same and mine's fixed too. It's a revelation for it to just work.
Thanks for the moral support and camaraderie during this difficult time
PauliMac 24, Mac OS X (10.6.6), Blah Blah
Currently Being ModeratedMar 30, 2011 9:12 PM (in response to Linda Custer)I haven't had much of a chance to post, but my further tests have proven 4.3 and 4.3.1 to work fine as well. I can even setup timed access and it doesn't drop a beat. I'm happy. Linda, things still good?17" MacBook Pro 2.4 GHz Santa Rosa, Mac OS X (10.6.6)
Currently Being ModeratedApr 2, 2011 7:07 AM (in response to sapphir8)Yes, things are still good. Whew.MBP (late 2008); MBA (11"/4/128); Mac mini (late 2009) running Win 7 w/BootCamp, Mac OS X (10.6.6), Displays: Dell 30", Apple 24" LED Cinema; iPhone 4/32; TV; TimeCapsule 2 TB
Currently Being ModeratedApr 8, 2011 4:40 PM (in response to mcpezza)three days ago I started losing DHCP to comcast - I had updated (against my better judgment) to 7.5.2 and it seemed okay for a few weeks, but something must have broken, possibly with some subsequent system update. I kept losing ipod touch connection, not realizing that the airport (or the cable modem) had gone into zombie mode. Then realized I was losing wireless for everything. Spent almost a day on this troubleshooting, assuming at first it was the cable's fault, but in desperation I reverted to 7.5.1 and (fingers crossed) that seems to have fixed it. At least I haven't been kicked offline in the last few hours. Time will tell.
PS I couldn't FIND 7.5.1 at first (didnt know to hold down the option key when accessing the upload menu) and had trouble looking it up, since I was constantly getting disconnected, so I'll mention it here, in case any one else is wondering how to revert to earlier version.
Is there a way to keep airport software update from nagging you to update to 7.5.2. I dont want to go back there! (at least til the fix it).macbookpro, Mac OS X (10.6.7)
Currently Being ModeratedJun 14, 2011 3:59 PM (in response to artwire)
Since upgrading Time Capsule and Airport Express (Extending the signal) to 7.5.2. iPhone 4 (always kept to the latest version, currently 4.3.3) will not connect to WiFi. Threads here say to downgrade Airport to firmware v7.5.1 but all I am offered is 7.4.2. The only solution I could find was to downgrade my Airports to 7.4.2 and hope Apple releases another update SOON. It's not ideal but at least I have a signal again.
Currently Being ModeratedJun 26, 2011 1:16 AM (in response to shutyourpiehole was taken)
I have just been offered 7.5.2 firmware upgrade and internet connectivity stopped straight away. I did not have the option of rolling back to 7.4.2 as it was a new unit (one week). I found the solution in this thread http://www.infrageeks.com/groups/infrageeks/weblog/0635b/ (linh Mar 7) - I am now back to 7.4.2 and it works fine. Not sure what to do in future though
Currently Being ModeratedJul 20, 2011 10:59 PM (in response to Linda Custer)
Happy for those who have things fixed. Unfortunately, updating again to 7.5.2 (from 7.4.2) on TC and AP Exps still breaks my newest iPhone 4g running iOS 4.3.1. My other iPhone 3g and iPad 1 running same iOS have little to no issues with the update.
After updating to 7.5.2 again, I did notice upon resetting from Airplane mode on my iPhone 3g and iPad 1 the wireless connection (2Ghz) on the iPad and iPhone 3g did cycle a couple of times but eventually settled down and ran good.
The iPhone 4 (a Verizon iPhone) never stopped cycling between connect and disconnected even when statically assigning an IP.
Things I know:
1. The issue is not DHCP related. Statically assigning an IP would solve that.
2. The issue only seems to occur when using WPA/WPA2 settings on the TC/APs.
3. The issue is not Proxy related.
4. The iPad 1 and iPhone 3g which worked this time in trying the 7.5.2 firmware (had issues on the last couple of attempts over the year this issue has been known) had their WiFi on and connected during the upgrade from 7.4.2. to 7.5.2 firmware.
5. The iPhone 4g which didn't work on this attempt to upgrade TC/APs to 7.5.2 did not have it's WiFi on (and subsequently not connected) during the upgrade.
While I have ensured Access Controls are disabled time and time again, I suspect the issue is related somehow to Access Controls as when I enable them with 7.4.2 firmware and add an iPhone MAC address set to NO ACCESS, I get very similar results. Maybe, and I'm guessing here, the 7.5.2 firmware inadvertently enables or utilizes some access control settings? Just a guess....
I'm tired and I've rolled everything (TC and APs) again back to 7.4.2 so all of my iOS devices can use WEP secured WiFi again.
All of this in conjunction with the Lion upgrade issues today has left me irritated at Apple. But that's another post for another thread. <sigh>
Currently Being ModeratedJul 29, 2011 8:41 AM (in response to bikiru)
Had the same trouble with my iPhones 3G and 4 on 7.5.2
Rolled back to 7.5.1 and my troubles where over.
Did have to create a 5Ghz and a normal netwerk with seperate names though.
I use the 5Ghz netwerk for my notebooks and the normal one (2Ghz) for the iPhones.
Hope this will help you all.
Currently Being ModeratedAug 10, 2011 1:05 PM (in response to bikiru)
after having read through most of this thred, i decided to roll back to 7.5.1 and - drumroll - it's working again.
I was unable to connect my iphone 4 to my network and i had no idea why. Now it's working again!
Thanx a bunch