I had finally got a reply from Netgear and they will be providing a fix very soon. I guessed it was a good effort made by so many contributors to make it known to them on the annoyance of the problem that has caused so much inconvenience to many device owners. At least now that I do appreciate that they took my case seriously and made progress in their findings and fixes.
I will update again once I get the issue fixed by them.
I have got the fix from Netgear, deployed onto my EX7000 and it is working now! I do not see the No Internet Connection false message anymore and in addition, when i disconnect my main router from the internet, my EX7000 will also get updated with real no internet connection message.
I believe the fix will be provided by Netgear support very soon! Everyone do keep a lookout soon!
Damn, they should pass it to me. I was the one that opened the thread 😀😀 In all seriousness, thanks. Now I have to return that modem that I was going to use.
Hello,
Thanks to all!
I am not an IT technician, I just want good quality that works. That's why I bought the Netgear.
With the conversion to IPv6 / IPv4 in my router, where otherwise only standard settings are, I get with Netgear Genie this message no longer.
OK, now the bug is even officially improved.
But the question remains: why, when and how did this happen?
Was there something secretly tried on our Netgear EX7000?
Good luck
Frantisek
Ever hear of Occam's Razor? The simplest explaination is usually the correct one. If you live in the States, you know that screw ups are becoming more common as the focus shifts from quality to cost savings - assumptions are made and QA can be myopic. I can't attribute this to Netgear, of course, it's simply an generic observation. I've generally found them to be on the higher end of quality for consumer grade products. **bleep** happens.
Depends - it's cosmetic so I can't picture them doing an out of cycle build for it, but it's also a visible problem. It also is an older product and they'd probably like you to push you into that new multi-mode system. Your guess is as good as mine.
Tha makes sense. The only issue is that it does report incorrect information about the staus of one of their products. Makes it harder to step through problems users might experience.
its an interesting question because this issue occured without any change from the users, i did not change my network, i did not update firmware.
As far as i am concerned Netgear made a change to their environment that created an issue with existing devices and now they are looking to fix that by effectivly patching the devices with updated firmware. Its a good thing that this really is just a cosmetic issue and nothing more serious. Cant say i would get away with this kind of thing at my work without having to hand over my testicals in jam jar as punishement
You raise an interesting concern... but this isn't a production environment - hence no free support after 30 days. Who knows what really happens when you redirect to mywifiext? I usually attribute things like this to Ockham's Razor - the simplest explaination is usually the correct one. The only way to really know is to backed up an old copy of the firmware on your computer and tested with that. Most people set these up and never check them again unless there's a problem they can't fix by just rebooting.
By the way - I can't help it ... "Mr. Crowley, lend me your ear..." 😀
i only noticed because i had to repatch my switch and like a true IT professional decided that labelling ports was something other people did. so i did waste rather a large amount of time thinking i had stuffed something up only to realise everything still worked.
This Crowley was stolen from my favorite book, it was either that or "whythehellareallthegoodusernamesalreadytaken"
Kids! Bringing about Armageddon can be dangerous. Do not attempt it in your home.Neil Gaiman and Terry Pratchett, Good Omens
So we're the unfortunate few that stumbled on it trying to solve a different problem? I wasted time chasing it down too... and it just cost me at $18... I had to ship back the router that I was going to replace the access point with. I hope that Fry's don't hold me to their stated policy of deducting the shipping cost from my refund as well ($40 down the drain). I came close to keeping it but I just spent $450 replacing my primary router and if I buy another access point now, it'll be commercial quality w/support so I don't have to worry about this chicken**bleep** stuff.
It's a good persona 😀 Mine is from one of my favorite of the 1960's "computers are taking over the world" genre movies. I think my next one will be Arthur_Dent. Geeks get the reference immediately, everyone else probably thinks I'm an MD.
i moved to house from an apartment and i was lucky to be able to run Cat5 to every room as i have great underfloor access so the EX7000 was simply to extend the Wifi to cover all areas and is really only used by a few Mobile devices. If Wifi had been a more serious requirement i may have gone down the ubiquity or even Cisco path, at least with Cisco i am surrounded by experts at work.
OMG firstly well done to you guys for getting this far. We updated the firmware on our EX7000 last night and crash today everything is pear shaped !
Unfortunately the impacts for us don't appear cosmetic. This is actually preventing us from working. Our symptoms appear slight different though;
1. Not all our devices have continued to work. I have a Microsoft Surface tablet running windows 10 that connects via wifi and it is saying it "Unable to connect to the network." This is one of our main devices and was work absolutely fine prior to the firmware upgrade. This device is key to get up and running.
2. I also have a laptop which just goes into a spin when trying to connect to the extender via wifi however works fine connected wired via cat5 cable. This is also running windows 10.
3. My apple iphone appears to connect and work OK via wifi ??
Other info that maybe handy, we also are in Australia on the Telstra Business network (in theory the most reliable in our country).
I also extremely struggled to follow the IP6 thing if anyone has a plain english version that would be greatly appreciated.
If anyone has any further help on our symptoms especially why I can't connect my Windows 10 Surface to the extender they would be greatly appreciated.
make sure that you reboot the entire stack from the modem forward. Make sure that your caches are flushed. Restart all of your hardware and allow it to get a new DHCP address. Make sure that DNS is being passed through properly from the router to the clients (check the DNS address on the clients). Sorry I can't be of any more help - they havent released the firmware in the US yet. I could get it via VPN but to be honest with you - I'll let them get the bugs out of it first.
Thanks, much appreciated, I had success in getting the laptop going but unfortunately still no luck with the microsoft surface. Oh how I wish I hadn't selected update !
Will need to wait for another opportunity outside production time to reboot all again. Hopefully fix will be out by then.
What's the error on the tablet? Is it getting a good IP address via DHCP? Is the DNS address good? Can you see it inside the network - or probably a better question - does it see objects like printers, etc on the network? If it can't connect to the access point, make sure that you're broadcasting on both bands, I know that my windows tablet can't see the 5GHz side but is fine on the 2.4 band. At least the one I have is low powered. Also obviously check any wifi passwords or try and connect using WPS and see if that's the problem.
Pls check your driver version's date which you have downloaded. If you have got it from the Netgear support website, that should still be the Oct 2016 version which contains the error which was recently acknowledged and rectified by Netgear.
I have managed to get to test the fix from Netgear and the error was gone and after some testing on my end, i was sure if my Internet is truly down, the message will appear correctly saying that No Internet Connection message.
I guess after my test, Netgear will need to go through some QA testing before releasing the next version to the public. So do be patient or you may want to roll back to your previous driver while waiting for the update.
