Currently Being ModeratedSep 21, 2012 3:08 AM (in response to bessman)
How can I downgrade the firmware of my netgear wg102? Thanks!
Currently Being ModeratedSep 21, 2012 3:14 AM (in response to setrak)
Then update your firmware - i have the same model
Currently Being ModeratedSep 21, 2012 3:50 AM (in response to The Great White Dope)
I had this same problem with my Netgear WGT624v3. As I'm just using this as a wireless access point and I also have a Linksys WAG160n, I re-enabled the WiFi on this as well to see if I could connect to this in the interim. Alas this gave the same problem (i.e. unable to connect to the WiFi message). So I think there are a few other routers other than the Netgear routers listed above that are giving this same issue that is different to the more general iOS6 wifi issue that is widely documented elsewhere. Hopefully with a wider pool of routers impacted by this, Apple will be encouraged to do something about it.
My "fix" for this issue was to download the iOS 5.1.1 IPSW package and downgrade my iPhone 4S back to the previous operating system. I would stress that this was a painful process and not one people should take lightly. However at least it put me back to where I was previously with a setup that I had working before and I can then consider upgrading back to iOS 6 once this is fixed.
Currently Being ModeratedSep 21, 2012 6:50 AM (in response to The Great White Dope)
My setup (office LAN with 3 AP:s Netgear WAG102, firmware V2.0.16)
Access from iPhone4S/iPad2:s terminated with upgrading to iOS6, while other un-upgraded iOS-units with 5.1.1 still accessing smoothly.
My solution: Router firmware V2.0.16 downgraded to V2.0.12 (extracted from download.netgear.com).
Result: iOS6-units back in WLAN-business.
Double-checked by re-upgrading AP:s to firmware V2.0.16 resulting again in no-access from iOS6-units.
Now the older V2.0.12 will prevail in our AP:s until news is spread about iOS6-fixes or new iOS6-compatible firmware from Netgear.
Currently Being ModeratedSep 21, 2012 7:26 AM (in response to AstroAndy)
Downgrading the Firmware to 5.0.1 on my Netgear WG102 also fixed this very frustrating issue for me.
Let's hope Apple can supply a fix soon, so that my faithful router can be upgraded back to 5.0.3.
Currently Being ModeratedSep 21, 2012 7:33 AM (in response to The Great White Dope)
I can also confirm that downgrading the firmware to v21 fixed the issue for me with my Netgear WGT624v3. As an experiement, I tried to use firmware v25, but it looks like whatever is hindering the connectiong was instantiated in v25, as it results in the same error message as v26. For now, v21 works until Apple can come out with a patch.
Thanks for all the help people!
Currently Being ModeratedSep 21, 2012 9:20 AM (in response to The Great White Dope)
I am still getting an issue with my 4s saying "Password Incorrect"!! I can't figure it out. I have changed the password several times and confirmed the change on my MBP, iPad3, and other iPhones. I can't figure out why my iPhone wont let me connect, or says incorrect password.
Currently Being ModeratedSep 21, 2012 10:19 AM (in response to DJ Pezz)
I am having the same issue with the iphone 4s. Disabled the security on the router and got the message that I can't join the network, then enabled the security to private and got the message that the password is invalid. Has anyone heard when Apple is going to have a fix for this?
Currently Being ModeratedSep 21, 2012 10:28 AM (in response to The Great White Dope)
Yes, downgraded my WG102 to 5.0.1 and that has fixed the issue for me.
Also seeing the issue on a wide range of Netgear wireless products including some of their managed wireless networks
Thanks guys, great effort - saved me a lot of effort finding this thread.
Currently Being ModeratedSep 22, 2012 4:20 AM (in response to 12121211111)
Hi Everyone! I too have had the same issue with Netgear WAG102 and downgrading from 16 to 12 fixed the wifi problem using my iPhone 4s
PS. I Noted that before downgrading the Netgear WAG102 from 16 to 12, my other iPhone 4 worked with ver 16?
Message was edited by: Jambo25
Currently Being ModeratedSep 23, 2012 5:58 AM (in response to The Great White Dope)
Same is happening to me, Ive restarted my belkin router and iPhone will connect for a few mintutes and then I will get the same "unable to join network". Its annoying. I tried everything and still nothing working.
Currently Being ModeratedSep 23, 2012 6:08 AM (in response to MoFoTomO)
I have a TP Link and same issue. I changed the channel of the router to a number less than 10; I went from 13 to 8 and that solved the issue. Try it. It's easy.
Currently Being ModeratedSep 23, 2012 6:10 AM (in response to crewhughes)
Others are downloading older firmware but not knowing why it works; I only changed the channel so the issue must be related to how many channels are supported by i06.
Currently Being ModeratedSep 23, 2012 8:53 AM (in response to crewhughes)
Your issue is not the same as the issue being reported in this thread, though it may superficially appear to be the same issue. Changing (and indeed, trying ALL of) the router channels was one of the earlier fixes tried which did not solve the problem for people affected by the issue in this thread.
(Incidentally, downgrading the router firmware does not change the channel on the router. Settings are generally preserved across a downgrade, so downgraded routers broadcast on the same channel as they did on newer firmware. I am currently using my Netgear router on channel 11 with older firmware, and it works just fine. It did not work with the newer firmware on any channel at all.)
Your router issue has something to do with channels, or potentially the sensitivity of your device to potential channel interference. Our router issue is not solved by changing channels and, in fact, the router logs are showing us that it is an unsupported request being made by iOS 6 on new Apple hardware that is the problem--not an incompatibility across channels.
Currently Being ModeratedSep 23, 2012 11:54 AM (in response to NaplesDave)
I can also confirm that after downgrading netgear WGT624v3 to 2.0.21 resolves the issue.
Many thanks to Cooper and Naples Dave for elevating this issue and finding the workaround.
We appreciate you help.